-
Notifications
You must be signed in to change notification settings - Fork 7
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
Giving IPv6 a shot? #1
Comments
Sounds interesting. I'll do it & mention you after it is done! |
Yes IPv6 is a lot cleaner implementation, for instance AWS uses NAT and various other kludges to conserve address space with legacy IP, but v6 they just route you a block. The NAT might work here because it's 1:1 so it just forwards anything unknown to a single address, with a 1:many arrangement it simply wouldnt know where to send unknown traffic. Legacy IP basically stifles development of new protocols, for instance SCTP has been around many years and offers a lot of benefits but won't make it through most NAT gateways. |
Excellent suggestion. I tried it out and updated the readme You can see the exact changes here #3 |
AWS worked, how about digital ocean? Or is that explicitly blocking unknown protocols? They do have v6 support. |
Yep, it is mentioned in their docs that they block non-standard protocols, and even some standardized protocols that are unusued
That's interesting. Not sure what would be gained by NAT'ing IPv6. Will be interesting to try out sometime |
Since there isn't NAT in IPv6
The text was updated successfully, but these errors were encountered: