Added IPv6 support #20
Conversation
|
Thank you, But I got some questions.
|
|
Ok to 1. I had some issues that the host didn't know where to send the data, and there were unanswered NDP queries. But I am still looking into not announcing them. about 2.: Nope openssl is not installed by default |
| # end ref | ||
| leftfirewall=yes | ||
| right=%any | ||
| rightsourceip=10.8.0.0/16 | ||
| rightsourceip=10.8.0.0/16,2a00:1450:400c:c05::/64 |
There was a problem hiding this comment.
The IP range 2a00:1450:400c:c05::/64 seems not in the range of reserved IP addresses, please update it to use private IP range, I thinks the IPv4 mapped addresses section is quite applicable.
There was a problem hiding this comment.
Oops. Yes you are right it should. However I don't think it should come out of the IPv6 mapped addresses, because it should probably be a full /64 to enable people to do SLAAC at some point. I think it should come out of be a /64 out of the fc00::/7subnet. I'll update this later today.
There was a problem hiding this comment.
Oh, you are right, the IPv4 mapped addresses maps to the entire IPv4 internet. fc00::/7 is the way to go.
This reverts commit 3b91dff.
I've added IPv6 support. I creates a private IPv6 subnet (
2a00:1450:400c:c05::/64) for the VPN, and uses ndppd to announce the prefix.