Opened 7 years ago

Last modified 18 months ago

#668 new Bug / Defect

route_vpn_gateway environment variable not set when no routes pushed

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


The route_vpn_gateway environment variable is not set for the up script unless a route is also pushed. There are a variety of use cases where you need route_vpn_gateway but don't have pushed routes, like where you're policy routing over OpenVPN, or otherwise want or need your up script to handle routing. route_vpn_gateway should never be excluded where it's known/exists.

Attachments (1)

0001-Fix-route_vpn_gateway-not-always-set.patch (2.1 KB) - added by jjacky 5 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 6 years ago by eshieldx

Could team review this bug? I'm awaiting for a fix almost a half of year!

comment:2 Changed 6 years ago by debbie10t

comment:3 Changed 6 years ago by eshieldx

Well, I'm using dummy route push for a long time as a workaround, but this is not good, imho. Will it be fixed?

comment:4 Changed 5 years ago by jjacky

I've been hit by that bug recently, so here's a patch that should fix it, ensuring $route_vpn_gateway is set even when no routes are pushed.

comment:5 Changed 18 months ago by OpenNya

Hi All!

I can confirm that the described defect returns back in the version OpenVPN 2.4.7 I am currently using.
Unfortunately I have no ability to upgrade OVPN because 2.4.7 is the latest version on my LTS OS package repository.

Note: See TracTickets for help on using tickets.