SixXS::Sunset 2017-06-06

Please document the size (change) of ICMPv6 echo packets used by PoPs
[de] Shadow Hawkins on Friday, 23 March 2012 09:21:42
Hello, please document the data size of ICMPv6 echo packets sent by PoPs in order to check whether the tunnel peer is alive, or alternatively document that the size is unspecified and is subject to change. I'm afraid I haven't found any information about it so far. The size apparently changed to 1028 bytes when the migration to SixXSd v4 was made, such that it did not pass my firewall rules which generally limits incoming ICMPv6 echo packets to 150 bytes. I solved it by accepting any ICPv6 echo packets coming from the PoP, but did not realize the problem until recently. A documentation entry about the change somewhere (e.g. in the News) would have been very helpful. Thanks, Christoph Schulz
Please document the size (change) of ICMPv6 echo packets used by PoPs
[ch] Jeroen Massar SixXS Staff on Friday, 23 March 2012 15:04:12
which generally limits incoming ICMPv6 echo packets to 150 bytes
That you put up arbitrary rules is your problem. The Firewall FAQ states, you should accept any kind of ICMPv6 Echo Request from the PoP for the latency checks. I really do not see a reason why those packet sizes should be fixed in anyway. They will be somewhere between 60 and the size of the MTU of the tunnel. Due to MTU differences it might at one point even vary in burst to be able to check what the optimal MTU size for a connection really is.
A documentation entry about the change somewhere (e.g. in the News) would have been very helpful.
There is a pointer from the news post that we deployed v4 to he entry discussing all the special things that it does.
Please document the size (change) of ICMPv6 echo packets used by PoPs
[de] Shadow Hawkins on Friday, 23 March 2012 21:06:32
Hello!
The Firewall FAQ states, you should accept any kind of ICMPv6 Echo Request from
the PoP for the latency checks.
Well, the FAQ entry does not talk about ICMPv6 packet size at all. Of course, I admit I *should* have interpreted this to allow packets ICMPv6 echo packets of any size.
There is a pointer from the news post that we deployed v4 to he entry
discussing all the special things that it does.
I'm afraid I haven't found anything there about bigger ICPv6 packets. In fact, the limit of 150 bytes worked flawlessly before the upgrade. Regards, Christoph Schulz
Please document the size (change) of ICMPv6 echo packets used by PoPs
[ch] Jeroen Massar SixXS Staff on Friday, 23 March 2012 21:20:20
I'm afraid I haven't found anything there about bigger ICPv6 packets.
Because one should be able to accept any size of packet (well, the technical minimum is 40 bytes due to the IPv6 header, then add a bit of ICMPv6, upto a max of the MTU of the tunnel).

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker