Date: Mon, 1 Mar 2010 13:42:19 +0100 From: Bernd Walter <ticso@cicely7.cicely.de> To: net@freebsd.org Cc: Bernd Walter <ticso@cicely7.cicely.de> Subject: IPFW2: IPV6 - Invalid Fragment Header Message-ID: <20100301124219.GK58319@cicely7.cicely.de>
next in thread | raw e-mail | index | archive | help
The droppped packets are simple ping requests send by an amd64
8.0-RC1 (r198183) system.
The dropping systems are both ARM - one is 7.0-current and the other is
a r204418 current.
With net.inet6.ip6.fw.enable=0 those packets are properly answered.
Is this a bug in client code or ipfw being oversensible.
Those dropped packets work fine if passed.
I just do:
ping6 2002:559f:e31:1::27
This is what the other side gets:
13:38:25.903467 00:1c:c0:30:16:a1 > 00:0e:42:02:00:42, ethertype IPv6 (0x86dd), length 78: (hlim 64, next-header Fragment (44) payload length: 24) 2002:559f:e31:1::30 > 2002:559f:e31:1::27: frag (0x21fec56e:0|16) ICMP6, echo request, length 16, seq 40
13:38:25.915918 00:1c:c0:94:2c:d7 > 00:0e:42:02:00:42, ethertype IPv4 (0x0800), length 66: (tos 0x10, ttl 64, id 29018, offset 0, flags [DF], proto TCP (6), length 52)
10.1.1.9.49545 > 10.1.1.38.22: Flags [.], cksum 0x8b05 (correct), ack 2112, win 8326, options [nop,nop,TS val 1501749236 ecr 3396017690], length 0
--
B.Walter <bernd@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100301124219.GK58319>