[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Weird ping behaviour
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Weird ping behaviour
- From: Seb <desreux_(_at_)_clipper_(_dot_)_ens_(_dot_)_fr>
- Date: Thu, 29 Mar 2001 05:48:21 +0200 (MET DST)
- Cc: Seb <Sebastien_(_dot_)_Desreux_(_at_)_ens_(_dot_)_fr>
I hope someone can help me out there... I've been banging my head on the walls
for weeks now, reading volumes of documentation and even failing to find
consolation in beer :-)
I am trying to set up a two-PCs home network with an ADSL connection. I
thought it might be smart to install Open instead of linux on my gateway. This
machine's got two NICs: 10.0.0.1 is connected to the linux-machine (aka
10.0.0.2), 10.0.0.3 is connected to the ADSL modem. I am using an out of the
box 2.8; the network has been partially setup during install; I have not
meddled in any way with any configuration file. I join the files I thought
might be useful, including `ifconfig -a`.
To be more precise, I do have tried meddling in all sorts of ways, in all
kinds of files, have reinstalled a couple of times with slightly different
options; to no avail. So I am back to the rock bare distrib (didn't even
install zsh !).
My aim is quite simple: being able to ping both 10.0.0.2 (the other machine)
and 10.0.0.138 (the modem -- the IP was attributed at factory time). Alas, it
seems that only dc0 (which is 10.0.0.1) is able to ping anybody. If it is
connected (by an ethernet cable) to 10.0.0.2 (which is the desired
configuration), I can ping 10.0.0.2 but not 10.0.0.138. If it is connected to
10.0.0.138, I can ping 10.0.0.138 but not 10.0.0.2. (Ping indicates that the
host is down.)
To get more specific, here is an account of the most basic experimentation
I could imagine:
* Reinstall Open, configuring the network during install, meaning
attributing IP adresses to dc0 (10.0.0.1) and dc1 (10.0.0.3), christening
the machine "Tintagel" and nothing more. Check with 'ifconfig -a' that
everything is okay.
* reboot; ping 10.0.0.1 and 10.0.0.3 (this works).
* ping 10.0.0.2, which is connected to 10.0.0.1 (this works -- and yet no
route has been setup for this address; maybe dc0 is the default route).
* ping 10.0.0.138, which is connected to 10.0.0.3 (this should fail, and does,
since no route has been defined).
* "route add -host 10.0.0.138 10.0.0.3"; this fails:
writing to routing socket: File exists
add host 10.0.0.138: gateway 10.0.0.3 : File exists
(I wonder what file defines a route for 10.0.0.138...)
* "route delete 10.0.0.138; route add -host 10.0.0.138 10.0.0.3"; "route show"
says it is OK; but "route get 10.0.0.138" says the interface for this route is
dc0 (10.0.0.1). Strange.
* Let's give it a try: "ping 10.0.0.138"; and then Open simply answers:
"/bsd: arpresolve: can't allocate llinfo".
Beats me. Now what does that mean ? There seems to be nothing about either
'arpresolve' of 'llinfo' using 'apropos'.
* OK, now is the worst part: after a "route flush", I can no longer ping
10.0.0.3. "route get 10.0.0.3" says that the interface for this host is dc0
(10.0.0.1)! Trying "sh -x /etc/netstart" does not ressucitate 10.0.0.3.
This is too much for me. I cannot comprehend how this kind of thing could
happen. Just to make sure I hadn't switched to yet another parallel
universe I removed Open, installed an out of the box RedHat 7.0 (ahem) and
everything worked fine from the start. I could ping both 10.0.0.2 and
10.0.0.138 by just adding the routes. I also tried moving the cards (both
Netgear FA310TX) to other PCI slots, switching them, changing the ethernet
cables and reciting the coder's prayer; to no avail.
Please! *Any* help would be *greatly* appreciated!
I absolutely need this adsl connection for last week; I am on the verge of
installing a good ol' Slack...
10.0.0.3 Tintagel.none Tintagel
inet 10.0.0.1 255.255.255.0 NONE
inet 10.0.0.3 255.255.255.0 NONE
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32972
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
lo1: flags=8008<LOOPBACK,MULTICAST> mtu 32972
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
media: Ethernet autoselect (100baseTX full-duplex)
inet6 fe80::2a0:ccff:feda:584c%dc0 prefixlen 64 scopeid 0x1
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
media: Ethernet autoselect (10baseT)
inet6 fe80::2a0:ccff:fed3:7400%dc1 prefixlen 64 scopeid 0x2
inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
ppp1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
tun0: flags=10<POINTOPOINT> mtu 3000
tun1: flags=10<POINTOPOINT> mtu 3000
enc0: flags=0<> mtu 1536
enc1: flags=0<> mtu 1536
enc2: flags=0<> mtu 1536
enc3: flags=0<> mtu 1536
bridge0: flags=0<> mtu 1500
bridge1: flags=0<> mtu 1500
gre0: flags=8010<POINTOPOINT,MULTICAST> mtu 1450
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280