More details

[Aniruddha Bohra]

Hello
    There has to be some difference between how the userlevel and the kernel
module handles stuff --

    The same configuration works with the user level click as well as 
with a
linux router (non click but the default linux kernel).

    I could not see anything different in the two --- I can use the 
user-level
click for now - but if any debugging help is needed, I am willing to try.

Thanks

Aniruddha


Aniruddha Bohra wrote:

> Hello
>    Using the same configuration as my previous message to the list
> but adding several print statements, I have the following info :
> Host 0 is on eth1 subnet - sends a SYN - which never reaches the Host1 
> on eth2
> which however reaches at least the ARPQuerier (Out on eth2 printf).
>
> One thing to note is that the incoming packet is 60 bytes while the 
> outgoing packet is 58.
>
>
> /var/log/messages says
> Jun 18 20:51:31 hora-7 kernel: chatter: eth1 IP:   60 | 000476df 
> ce580010 4200827c 08004510 002c0042 40004006
> Jun 18 20:51:31 hora-7 kernel: chatter: Forward to eth2:   44 | 
> 4510002c 00424000 400601b8 0a0a0a0e c0a86402 04140017
> Jun 18 20:51:31 hora-7 kernel: chatter: Out on eth2:   58 | 00104200 
> 827d0004 76dd2978 08004510 002c0042 40003f06
> Jun 18 20:51:31 hora-7 kernel: chatter: Out on eth2:   42 | ffffffff 
> ffff0004 76dd2978 08060001 08000604 00010004
> Jun 18 20:51:31 hora-7 kernel: chatter: Local delivery:   60 | 
> 000476dd 29780010 4200827d 08060001 08000604 00020010
> Jun 18 20:51:34 hora-7 kernel: chatter: eth1 IP:   60 | 000476df 
> ce580010 4200827c 08004510 002c0043 40004006
> Jun 18 20:51:34 hora-7 kernel: chatter: Forward to eth2:   44 | 
> 4510002c 00434000 400601b7 0a0a0a0e c0a86402 04140017
> Jun 18 20:51:34 hora-7 kernel: chatter: Out on eth2:   58 | 00104200 
> 827d0004 76dd2978 08004510 002c0043 40003f06
> Jun 18 20:51:40 hora-7 kernel: chatter: eth1 IP:   60 | 000476df 
> ce580010 4200827c 08004510 002c0044 40004006
> Jun 18 20:51:40 hora-7 kernel: chatter: Forward to eth2:   44 | 
> 4510002c 00444000 400601b6 0a0a0a0e c0a86402 04140017
> Jun 18 20:51:40 hora-7 kernel: chatter: Out on eth2:   58 | 00104200 
> 827d0004 76dd2978 08004510 002c0044 40003f06
>
> tcpdump on host 0 says :
> [root at ghoomar0 root]# tcpdump -i eth1
> tcpdump: listening on eth1
> 19:52:16.467224 10.10.10.14.1044 > 192.168.100.2.telnet: S 
> 3629135766:3629135766(0) win 5632 <mss 1460> (DF) [tos 0x10]
> 19:52:19.458799 10.10.10.14.1044 > 192.168.100.2.telnet: S 
> 3629135766:3629135766(0) win 5632 <mss 1460> (DF) [tos 0x10]
> 19:52:25.458798 10.10.10.14.1044 > 192.168.100.2.telnet: S 
> 3629135766:3629135766(0) win 5632 <mss 1460> (DF) [tos 0x10]
>
> tcpdump on host 1 says :
> [root at ghoomar1 root]# tcpdump -i eth1
> tcpdump: listening on eth1
> 20:55:32.978911 arp who-has 192.168.100.2 tell 192.168.100.1
> 20:55:32.978923 arp reply 192.168.100.2 is-at 0:10:42:0:82:7d
>
> Is there any more information I can provide to identify the problem ?
>
> Thanks
> Aniruddha
>
>