Opened 7 months ago

Last modified 6 months ago

#1247 new Bug / Defect

"remote_host" route moniker not working when v6 connection was established

Reported by: madduck Owned by:
Priority: major Milestone:
Component: Generic / unclassified Version: OpenVPN 2.4.7 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:


Given a line

route remote_host default net_gateway

results in a route to being added to the kernel routing table, which is bad. This only happens, if the connection to the OpenVPN server was made using IPv6, and can thus be avoided by using udp4.

Ideally, the line should yield a v6 route to be added in much the same way it would add a v4 route, depending on the address family used.

Change History (2)

comment:1 Changed 7 months ago by madduck

I forgot to include that I get a log message

RESOLVE: Cannot parse IP address: net_gateway: (Name or service not known)

which is a bit weird. There is a v4 net_gateway, but there is no v4 remote_host.

comment:2 Changed 7 months ago by tincantech

Just in case this goes somewhere .. CC

There is also a chance this is related to

Last edited 6 months ago by tincantech (previous) (diff)
Note: See TracTickets for help on using tickets.