-
Notifications
You must be signed in to change notification settings - Fork 136
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
IPv6 support #4
Comments
It's not planned, it's wanted, the problem is you need to go through a netlink socket to set up IPv6 addresses and I really do not want to implement that. Also keep in mind this is only for TUN interfaces, the plan was to also make a TAP crate. |
So, if I understand you correctly, if someone wrote a crate that could manipulate arbitrary interface's addresses (and maybe other things), you could then use that as dependency of both this and the yet unwritten TAP crate to provide that functionality? I guess setting the addresses on TUN would be exactly the same as setting it on other interfaces. |
Yeah, that was the initial plan, then I saw how much stuff you needed to set IPv6 addresses on Linux, and I don't even want to know how much churn there would be to support more than that. It may actually be more feasible to wrap the various |
eliminate redundant copy
Hello
I just needed a TAP device crate and only after writing one myself, I discovered this, which seems to be richer in features than mine (mine is just raw pipe for packets, without any configuration of the interface). However, reading the documentation, it seems this completely lacks any IPv6 consideration.
Is it planned or is that on purpose?
The text was updated successfully, but these errors were encountered: