-
Notifications
You must be signed in to change notification settings - Fork 64
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 doesn't works by default #9
Comments
I don't have ipv6 connection to test, so this needs others to investigate and fix. |
You don't need to have ipv6, you'll get it from CF warp. |
It works (ugly hack, scroll below). Modify
Tests:
credits @oskar456 |
Using that will only work on linux though. |
Yeah, routing will be different for Windows & MacOS, so platform-specific configs needed. |
I think the config should be platform-independent. Maybe Wireguard have some config to let you do that easily? |
As much I checked - no. I can write a patch to generate Linux config, or you can add the note to Readme. |
You may also want to consider nftables support for ipv6 on linux. Nftables rules (disable if iptables is used)PostUp = nft add table ip6 nat |
Doesn't iptables use nftables on backend now? |
I believe iptables is currently deprecated and being replaced by nftables in the 5.x kernel. |
This is actually an ugly hack - IPv6 NAT in order to get globally routable IPv6 address instead of ULA address. This indeed only works with Linux and iptables. So it's certainly unsafe to put in into default config file (maybe only as a commented-out default) Instead I hope Cloudflare will eventually change IPv6 prefix to some globally unique address.
It depends on linux distribution. Classical iptables still work but it is not recommended to combine nftables and iptables rules, although it is technically possible. |
Got it working without NAT&iptables. |
|
@abbyck when tunnel connects to endpoint the network interface gets ip from
|
Interface is up and get address 2a09:bac0::/32, but Linux ignore it and prefer ipv4.
More info
The text was updated successfully, but these errors were encountered: