Wolfgang Bornath wrote:
> 
> On Fri, Apr 06, 2001 at 01:31 -0400, Pierre Fortin wrote:
> 
> > [Going back to your ealier posting, you had a UH entry overlapping the subnet;
> > have you tried deleting it?  I'm not sure why a host route would even be there
> > when a net route exists...]
> 
> Err... How do I delete that? Sorry, concerning net I'm a newbie.

route del 192.168.100.X   (X matches what is in route table)

> > I forgot the default output of tcpdump was terse...  Can you give the output of
> > "tcpdump -ex"?
> 
> 1. lapmolch is pinging molch:
> [root@molch wobo]# tcpdump -ex
> tcpdump: listening on eth0

lapmolch(.2) ARPing for molch(.3):
> 10:32:06.173354 0:a0:c:14:8b:6b Broadcast arp 60: arp who-has
> molch.wolf-b.de tell lapmolch.wolf-b.de
>                          0001 0800 0604 0001 00a0 0c14 8b6b c0a8
>                          6402 0000 0000 0000 c0a8 6403 ffff 0000
>                          ffff ffff 0000 ffff 0000 ffff 0000
Since tcpdump is seeing this packet, molch does see lapmolch's ARP,
and replies here:
> 10:32:06.173432 0:50:ba:31:f:b2 0:a0:c:14:8b:6b arp 42: arp reply
> molch.wolf-b.de is-at 0:50:ba:31:f:b2
>                          0001 0800 0604 0002 0050 ba31 0fb2 c0a8
>                          6403 00a0 0c14 8b6b c0a8 6402
which lapmolch sees allowing it to ping, which molch sees (it's running
tcpdump):
> 10:32:06.173906 0:a0:c:14:8b:6b 0:50:ba:31:f:b2 ip 98:
> lapmolch.wolf-b.de > molch.wolf-b.de: icmp: echo request
>                          4500 0054 0000 0000 4001 3153 c0a8 6402
>                          c0a8 6403 0800 291a 6c00 0000 827f cd3a
>                          2828 0000 0809 0a0b 0c0d 0e0f 1011 1213
>                          1415 1617 1819
then, for some reason molch tries to ARP itself rather than send a ping reply:
> 10:32:06.173996 0:50:ba:31:f:b2 Broadcast arp 42: arp who-has
> molch.wolf-b.de tell molch.wolf-b.de
>                          0001 0800 0604 0001 0050 ba31 0fb2 c0a8
>                          6403 0000 0000 0000 c0a8 6401

So molch appears to have a problem above.  

Let's look at the other now...
> [.....]
> 
> 2. molch is pinging lapmolch:
> [root@molch wobo]# tcpdump -ex
> tcpdump: listening on eth0

molch is ARPing for itself
> 10:37:02.071155 0:50:ba:31:f:b2 Broadcast arp 42: arp who-has
> molch.wolf-b.de tell molch.wolf-b.de
>                          0001 0800 0604 0001 0050 ba31 0fb2 c0a8
>                          6403 0000 0000 0000 c0a8 6401
gets no reply, tries again:
> 10:37:03.065233 0:50:ba:31:f:b2 Broadcast arp 42: arp who-has
> molch.wolf-b.de tell molch.wolf-b.de
>                          0001 0800 0604 0001 0050 ba31 0fb2 c0a8
>                          6403 0000 0000 0000 c0a8 6401
and again:
> 10:37:04.065234 0:50:ba:31:f:b2 Broadcast arp 42: arp who-has
> molch.wolf-b.de tell molch.wolf-b.de
>                          0001 0800 0604 0001 0050 ba31 0fb2 c0a8
>                          6403 0000 0000 0000 c0a8 6401
> [....]
> 
> Looks like molch doesn't know who molch is?

Looks like lapmolch is probably OK; but molch is confused...

Did you make any changes to molch recently?  

Pierre

> wobo
> --
> GPG-Fingerprint: FE5A 0891 7027 8D1B 4E3F  73C1 AD9B D732 A698 82EE
> For Public Key mailto [EMAIL PROTECTED] with Subject: GPG-Request
> -------------------------------------------------------------------
> ISDN4LINUX-FAQ -- Deutsch: http://www.wolf-b.de/i4l/i4lfaq-de.html

-- 
Linux (Up 16 days) -- Reboots are for system upgrades... not Windows X^P
Last reboot reason:  01/03/27: winter storm 6hr power outage

Reply via email to