Bug #6016
closed
ovpn-linkup not populating IPv6 gateways
100%
Description
I'm not sure if this is the intended behavior.
When configured as an OpenVPN (dual stack) client, the /tmp/ovpn1_routerv6 is not generated by the ovpn-linkup shell script. The IPv6 OpenVPN gateway will be shown as dynamic, making it unusable for routing/rules.
Updated by Chris Buechler almost 10 years ago
- Subject changed from ovpn-linkup not setting the /tmp/ovpn1_routerv6 file to ovpn-linkup not populating IPv6 gateways
- Status changed from New to Confirmed
- Assignee set to Chris Buechler
- Target version changed from 2.3 to 2.3.1
- Affected Version changed from 2.3 to All
it never has populated the v6 gateway. Judging by my perusal of the OpenVPN bug tracker as part of #5835, there are issues there in OpenVPN with env variables and IPv6. A couple related.
https://community.openvpn.net/openvpn/ticket/230
https://community.openvpn.net/openvpn/ticket/369
I'll look at it later for 2.3.1.
Updated by Jose Luis Duran almost 10 years ago
Thanks!
It used to "work" (as in the same way IPv4 does) in 2.2.x
Updated by Chris Buechler almost 10 years ago
Jose Luis Duran wrote:
It used to "work" (as in the same way IPv4 does) in 2.2.x
No, ovpn-linkup has never populated routerv6. 2.2.x's file is identical in that regard to 2.3's.
Updated by Chris Buechler over 9 years ago
- Target version changed from 2.3.1 to 2.3.2
Updated by Chris Buechler over 9 years ago
- Assignee deleted (
Chris Buechler) - Target version changed from 2.3.2 to 2.4.0
Updated by Jim Pingle about 9 years ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset f829a8d3258e377b778ac84a1f2f345b8a79b766.