Tunnels are not creating automatic routes.

[fear_angel]

Good morning,

I installed a fresh 16.4.1 version. I restored a configuration from a version 16.4.1. I updated to the latest version.

My two tunnels were configured and connected but the routes are not being made. I had to go through the console manually for it to work.

ip router add 10.68.80.0/24 via 173.32.0.6 dev tun201
ip router add 10.68.81.0/24 via 172.31.0.6 dev tun200

When I disconnect the routes are deleted and I have to create them again.
will this be a BUG? how can I solve?

Thanks.

[gravenscroft]

Is this OpenVPN? If so, are you including the local networks in your Exported Networks attribute when creating the client(s)?

[fear_angel]

No. I don't use openvpn. I am creating tunnels in the "Tunnel VPN" module. I create the tunnels. I save and it connects. But it does not create the routes.
I have to create tunnels manually.

" = IPv4 Table main = "

10.68.80.0/24 via 173.32.0.6 dev tun201
10.68.81.0/24 via 172.31.0.6 dev tun200

this should create automatically. When I disconnect and reconnect it disappears I have to go through ssh and do it manually.

[jcoffin]

Did you create rules for the tunnels (next tab over). Otherwise, no routes will be created.

[fear_angel]

I didn't create rules. In the old version it wasn't necessary... but if it is now I'll have to create it.

[optix]

Same problem starting in version 16.6.2

= IPv4 Table main =
172.16.4.137 dev tun200 scope link
172.16.5.0/24 dev eth1 proto kernel scope link src 172.16.5.1
192.0.2.0/30 dev br.lxc proto kernel scope link src 192.0.2.1 linkdown
192.0.2.200/30 dev utun proto kernel scope link src 192.0.2.200
192.168.103.0/24 dev eth0 proto kernel scope link src 192.168.103.3
192.168.103.1 dev eth0 scope link

on other Untangle connected to the same openvpn, the routes look like this:

= IPv4 Table main =
135.181.17.128/26 dev eth0 proto kernel scope link src 135.181.17.183
135.181.17.129 dev eth0 scope link
172.16.0.0/24 via 172.16.4.5 dev tun200
172.16.1.0/24 via 172.16.4.5 dev tun200
172.16.2.0/24 via 172.16.4.5 dev tun200
172.16.3.0/24 dev eth1 proto kernel scope link src 172.16.3.1
172.16.4.0/24 via 172.16.4.5 dev tun200
172.16.4.5 dev tun200 scope link
172.16.5.0/24 via 172.16.4.5 dev tun200
172.16.8.0/24 via 172.16.8.2 dev tun0
172.16.8.2 dev tun0 proto kernel scope link src 172.16.8.1
192.0.2.0/30 dev br.lxc proto kernel scope link src 192.0.2.1
192.0.2.200/30 dev utun proto kernel scope link src 192.0.2.200

[jcoffin]

Same problem starting in version 16.6.2

Try 17.0 https://launchpad.edge.arista.com/do...irewall/17.0.0

[optix]

Try 17.0 https://launchpad.edge.arista.com/do...irewall/17.0.0

Thank you very much, after installing version 17.0 the problem was solved, after setting up the tunnel in the routes appeared:

= Tunnel VPN Rules =
tunnel.200:
172.16.0.0/24 via 172.16.4.137 dev tun200
172.16.1.0/24 via 172.16.4.137 dev tun200
172.16.2.0/24 via 172.16.4.137 dev tun200
172.16.3.0/24 via 172.16.4.137 dev tun200
172.16.4.0/24 via 172.16.4.137 dev tun200

[donhwyo]

Try 17.0 https://launchpad.edge.arista.com/do...irewall/17.0.0

Is that the release candidate or final. No rc in the file name is confusing.

Thanks for the checksum.

[jcoffin]

Is that the release candidate or final. No rc in the file name is confusing.

Thanks for the checksum.

It is a release candidate. I have been running it live for almost a month now.