Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MTU and ICMP issue #2

Open
GoogleCodeExporter opened this issue Jul 7, 2015 · 0 comments
Open

MTU and ICMP issue #2

GoogleCodeExporter opened this issue Jul 7, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.

ICMP package on IPv4 should be reflected to the IPv6 according to RFC2893.
But TB-TUN has nothing to do with ICMP.

2.

According to RFC3506, "If the IPv6 MTU size proves to be too large for some
intermediate IPv4 subnet, IPv4 fragmentation will ensue....The IPv4 'do not
fragment' bit *SHOULD NOT* be set in the encapsulating IPv4 header." But
TB-TUN disobey these 2 rules. It causes IPv6 packages missing data and did
not report any error by ICMP when IPv6 MTU is to large.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.


Original issue reported on code.google.com by [email protected] on 25 Apr 2010 at 5:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant