On Mon, Apr 03, 2006 at 01:11:46AM +0200, Patrick McHardy wrote: > Thomas Zeitlhofer wrote: > > On Sun, Apr 02, 2006 at 09:19:30PM +0200, Patrick McHardy wrote: > > > >>>Doing the same on 2.6.15.x shows: > >>> > >>> 1) on tap1: fragmented packets > >>> 2) on br0: the defragmented packet (connection tracking) > >>> 3) on eth1: fragmented packets > >> > >>Are you sure this is correct? I think in 2.6.15 you should see > >>the fragments on br0 already. > > > > > > Just verified it, at least in 2.6.15.6 tcpdump shows the defragmented > > packet on br0. > > I'm probably missing something, but that still seems stange. > Are you also seeing the defragmented packet on br0 with my > patch?
Yes, here is the tcpdump output on all interfaces: 1) on tap1 23:22:51.830046 IP (tos 0x0, ttl 64, id 21174, offset 0, flags [+], proto: UDP (17), length: 1500) 192.168.10.1.500 > 192.168.20.1.500: isakmp 1.0 msgid : phase 1 I ident[E]: [encrypted id] (len mismatch: isakmp 2572/ip 1472) 23:22:51.830084 IP (tos 0x0, ttl 64, id 21174, offset 1480, flags [none], proto: UDP (17), length: 1120) 192.168.10.1 > 192.168.20.1: udp 2) on br0 23:22:51.830084 IP (tos 0x0, ttl 64, id 21174, offset 0, flags [none], proto: UDP (17), length: 2600) 192.168.10.1.500 > 192.168.20.1.500: isakmp 1.0 msgid : phase 1 I ident[E]: [encrypted id] 3) on eth1 23:22:51.830120 IP (tos 0x0, ttl 64, id 21174, offset 0, flags [+], proto: UDP (17), length: 1500) 192.168.10.1.500 > 192.168.20.1.500: isakmp 1.0 msgid : phase 1 I ident[E]: [encrypted id] (len mismatch: isakmp 2572/ip 1472) 23:22:51.830133 IP (tos 0x0, ttl 64, id 21174, offset 1480, flags [none], proto: UDP (17), length: 1120) 192.168.10.1 > 192.168.20.1: udp -- Thomas - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
