Troubles with networkmanager and openvpn
by heujhe from LinuxQuestions.org on (#4ZKBK)
Hello everybody.
I'm not much of a network expert, so i need some help. I'm used to use openvpn and when i switched to Slackware-current a couple of months ago i found that network manager with networkmanager-openvpn from Ponce repo works in a strange way:
Routes when connected with NM w/o NM-openvpn
Code:default via 192.168.77.1 dev eth0 proto dhcp src 192.168.77.10 metric 202
127.0.0.0/8 dev lo scope link
192.168.77.0/24 dev eth0 proto dhcp scope link src 192.168.77.10 metric 202Routes when connected with NM w/ NM-openvpn
Code:default via 10.18.0.1 dev tun0 proto static metric 50
default via 192.168.77.1 dev eth0 proto dhcp src 192.168.77.10 metric 202
10.18.0.0/24 dev tun0 proto kernel scope link src 10.18.0.2 metric 50
127.0.0.0/8 dev lo scope link
192.168.77.0/24 dev eth0 proto dhcp scope link src 192.168.77.10 metric 202Routes when connected with openvpn directly
Code:0.0.0.0/1 via 10.18.0.1 dev tun0
default via 192.168.77.1 dev eth0 proto dhcp src 192.168.77.10 metric 202
5.5.5.5 via 192.168.77.1 dev eth0
10.18.0.0/24 dev tun0 proto kernel scope link src 10.18.0.2
127.0.0.0/8 dev lo scope link
128.0.0.0/1 via 10.18.0.1 dev tun0
192.168.77.0/24 dev eth0 proto dhcp scope link src 192.168.77.10 metric 202As you can see list of routes when i connect to my openvpn server w/ and w/o NM-openvpn differs. I have no idea why, but i found this behavior only in Slackware. I have debian 10 and arch linux in dual (triple?:)) boot. NM in debian and arch has no such problems. Routes are the same if i connect directly with openvpn and with NM-openvpn.
Of course, i realise that i can manually push routes i need to make NM-openvpn works properly, but i'd like to find out what is the reason of all that. Can you help me?
I'm not much of a network expert, so i need some help. I'm used to use openvpn and when i switched to Slackware-current a couple of months ago i found that network manager with networkmanager-openvpn from Ponce repo works in a strange way:
Routes when connected with NM w/o NM-openvpn
Code:default via 192.168.77.1 dev eth0 proto dhcp src 192.168.77.10 metric 202
127.0.0.0/8 dev lo scope link
192.168.77.0/24 dev eth0 proto dhcp scope link src 192.168.77.10 metric 202Routes when connected with NM w/ NM-openvpn
Code:default via 10.18.0.1 dev tun0 proto static metric 50
default via 192.168.77.1 dev eth0 proto dhcp src 192.168.77.10 metric 202
10.18.0.0/24 dev tun0 proto kernel scope link src 10.18.0.2 metric 50
127.0.0.0/8 dev lo scope link
192.168.77.0/24 dev eth0 proto dhcp scope link src 192.168.77.10 metric 202Routes when connected with openvpn directly
Code:0.0.0.0/1 via 10.18.0.1 dev tun0
default via 192.168.77.1 dev eth0 proto dhcp src 192.168.77.10 metric 202
5.5.5.5 via 192.168.77.1 dev eth0
10.18.0.0/24 dev tun0 proto kernel scope link src 10.18.0.2
127.0.0.0/8 dev lo scope link
128.0.0.0/1 via 10.18.0.1 dev tun0
192.168.77.0/24 dev eth0 proto dhcp scope link src 192.168.77.10 metric 202As you can see list of routes when i connect to my openvpn server w/ and w/o NM-openvpn differs. I have no idea why, but i found this behavior only in Slackware. I have debian 10 and arch linux in dual (triple?:)) boot. NM in debian and arch has no such problems. Routes are the same if i connect directly with openvpn and with NM-openvpn.
Of course, i realise that i can manually push routes i need to make NM-openvpn works properly, but i'd like to find out what is the reason of all that. Can you help me?