Opened 3 years ago

Last modified 3 years ago

#18701 new defect

openvpn-polarssl can't restore a broken connection due to routing issues

Reported by: anonymous Owned by: developers
Priority: response-needed Milestone: Barrier Breaker 14.07
Component: packages Version: Barrier Breaker 14.07
Keywords: openvpn-polarssl routing Cc:


When openvpn-polarssl establishes a VPN tunnel, it adds several new routes to the routing table. If this tunnel fails (e.g. with an error from logread "

daemon.err openvpn(vpnifname): write UDPv4: Operation not permitted (code=1)

"), openvpn-polarssl can't re-establish the connection because it doesn't previously delete the routes that were set for the failed tunnel, and thus openvpn can't connect to the VPN server (and can't even resolve the VPN server's IP address).

The new (for BB) 2.3.6-2 version of openvpn-polarssl has the same issue.

Attachments (0)

Change History (2)

comment:1 Changed 3 years ago by jow

  • Priority changed from normal to response-needed

Any logs? Also are you sure that this belongs here? OpenVPN-PolarSSL is not developed by OpenWrt - maybe you should report that issue upstream at

comment:2 Changed 3 years ago by anonymous

In most Linux distributions, the "route" command is deprecated and any of "route"-specific troubles probably won't be solved. So I guess asking openwrt to provide support for this issue is the right thing.

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.