Traffic ipv6 translation support #7981
Conversation
|
I don't mind taking a look at de69071, but the other commit looks to convoluted to me. can you open a PR for the reverse dns part only? |
Ashus
force-pushed
the
traffic_ipv6_support
branch
from
585ed7d
to
de69071
Compare
|
Here you go. Although I hope you give the second commit a second look later. |
| @@ -0,0 +1,21 @@ | |||
| #!/usr/local/bin/php | |||
There was a problem hiding this comment.
we would rather fold this special case return into an existing script. duplicating functionality for a single IP family is not ideal and we can easily build a plugin-based wrapper that can be called with pluginctl.
There was a problem hiding this comment.
Please point me in the right direction, where you want it, I'm not familiar with this.
I was trying to fetch the info on gateways directly from system, but gateway names are not there. So they are extracted from possibly non-applied config instead.
This adds a support for resolving IPv6 reverse addresses.
Second commit is a bit more controversial, but handy as well. Imagine you have static IPv6 prefixes delegated in your network. For that you need static IPv6 routes to properly configured home routers. This feature allows to translate a dynamically created IP via SLAAC into last part of IPv6 address@GatewayName. eg. fc00:106:4:0:fc82:c2ff:ffff:a0cb would be translated to a0cb@ClientsName.