problem with arp-request

[Brecht Vermeulen]

Hi,

*I've installed click-1.2.0 and I've got exactly the same problem :

10.0.1.101 -> 10.0.1.100-10.0.2.100 -> 10.0.2.102

ping from 10.0.1.101 through .100

tcpdump on 10.0.2.102:
helios102:~# tcpdump -i eth1
tcpdump: listening on eth1
14:39:34.003757 arp who-has 220.61.214.194 tell 10.0.2.100
14:39:35.000839 arp who-has 220.61.214.194 tell 10.0.2.100
14:39:36.000791 arp who-has 220.61.214.194 tell 10.0.2.100
14:39:37.000811 arp who-has 220.61.214.194 tell 10.0.2.100
14:39:38.000801 arp who-has 220.61.214.194 tell
10.0.2.100                      

very strange !!

* another thing I've noticed is that the etherencap(0x800, 1:1:1:1:1:1,
2:2:2:2:2:2)
trick for handling packets to linux doesn't work anymore. a ping from
10.0.1.101 to 
10.0.1.100 doesn't work (the echo reply doesn't come back), but if I
change 2:2:2:2:2:2 to the real MAc address of the card, then it works.
However same 2.2.18 kernel as I've used with click 1.1 where everything
worked.

regards,
Brecht

Torsten Kaden wrote:
> 
> hello
> 
> we are using the click-router in a very simple oonfiguration. one router with
> two ethernet-interfaces (10.4.0.254/16, 10.5.0.254/16) and one single host
> connected to each (10.4.0.1/16, 10.5.0.1/16). sending a ping from host
> 10.4.0.1 to host 10.5.0.1 we encounterd the following problem.
> 
> the arp-request sent by the click-router into the destination subnet contains
> the wrong ip address to be resolved.
> 
> for a better understanding of our problem we attached a tcpdump-file.
> 
> have you experienced this problem so far?
> 
> thank you and have a nice day
> 
> 
>   ------------------------------------------------------------------------
>                   Name: arp.tcpdump
>    arp.tcpdump    Type: unspecified type (APPLICATION/octet-stream)
>               Encoding: BASE64