You are not logged in.
I am using the Dell SonicWall VPN client to access my university network. This worked for a long time without any problem from my archlinux installation. Unfortunately it stopped working some time ago. Unfortunately, I am not able to tell, when it stopped working exactly. In order to exclude, that it is a problem with my router, the ISP or my university network, I tried the same client on the same computer with an Ubuntu System (ubuntu 16.04.1) an it works without any problems.
I start the VPN client with the command 'startctui'. Then I enter my username and password and the client connects to the university network without any error messages. However, after the connection has been established, I cannot reach any server at all neither on my universitys network nor on the internet. For instance, if I try to ping www.archlinux.org, I get:
> ping -c3 www.archlinux.org
PING gudrun.archlinux.org (66.211.214.131) 56(84) bytes of data.
--- gudrun.archlinux.org ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999msThe output of ifconfig is as follows:
> ifconfig
enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 28:d2:44:4c:b6:8e txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf3600000-f3620000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 441 bytes 93724 (91.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 441 bytes 93724 (91.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1404
inet 141.75.251.19 netmask 255.255.255.255 destination 141.75.251.19
inet6 fe80::902b:37bf:a143:3142 prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1 bytes 48 (48.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.115 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::7226:2b68:1d4a:445d prefixlen 64 scopeid 0x20<link>
inet6 2a02:810d:8ac0:9a98:e3cd:708:b70:324 prefixlen 64 scopeid 0x0<global>
inet6 2a02:810d:8ac0:9a98:7226:2b68:1d4a:445d prefixlen 128 scopeid 0x0<global>
ether 5c:51:4f:8b:7f:8b txqueuelen 1000 (Ethernet)
RX packets 6466 bytes 4250522 (4.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5420 bytes 874519 (854.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0The interface tun0 is installed by the VPN client. 141.75.251.19 is an address on my university network. The output of 'ifconfig' is very similar to what is shown on the ubuntu-installation, where the VPN works without problems.
The output of 'ip route' looks also pretty similar to the corresponding outpunt with the ubuntu installation (see below).
> ip route
default via 192.168.0.1 dev wlp4s0
1.0.0.0/8 via 141.75.251.19 dev tun0 scope link
2.0.0.0/7 via 141.75.251.19 dev tun0 scope link
4.0.0.0/6 via 141.75.251.19 dev tun0 scope link
8.0.0.0/5 via 141.75.251.19 dev tun0 scope link
16.0.0.0/4 via 141.75.251.19 dev tun0 scope link
32.0.0.0/3 via 141.75.251.19 dev tun0 scope link
64.0.0.0/2 via 141.75.251.19 dev tun0 scope link
128.0.0.0/5 via 141.75.251.19 dev tun0 scope link
136.0.0.0/6 via 141.75.251.19 dev tun0 scope link
140.0.0.0/8 via 141.75.251.19 dev tun0 scope link
141.0.0.0/10 via 141.75.251.19 dev tun0 scope link
141.64.0.0/13 via 141.75.251.19 dev tun0 scope link
141.72.0.0/15 via 141.75.251.19 dev tun0 scope link
141.74.0.0/16 via 141.75.251.19 dev tun0 scope link
141.75.0.0/21 via 141.75.251.19 dev tun0 scope link
141.75.8.0/22 via 141.75.251.19 dev tun0 scope link
141.75.12.0/23 via 141.75.251.19 dev tun0 scope link
141.75.14.0/29 via 141.75.251.19 dev tun0 scope link
141.75.14.8/30 via 141.75.251.19 dev tun0 scope link
141.75.14.12/31 via 141.75.251.19 dev tun0 scope link
141.75.14.14 via 141.75.251.19 dev tun0 scope link
141.75.14.16/28 via 141.75.251.19 dev tun0 scope link
141.75.14.32/27 via 141.75.251.19 dev tun0 scope link
141.75.14.64/26 via 141.75.251.19 dev tun0 scope link
141.75.14.128/25 via 141.75.251.19 dev tun0 scope link
141.75.15.0/24 via 141.75.251.19 dev tun0 scope link
141.75.16.0/20 via 141.75.251.19 dev tun0 scope link
141.75.32.0/19 via 141.75.251.19 dev tun0 scope link
141.75.40.45 via 141.75.251.19 dev tun0 scope link
141.75.40.46 via 141.75.251.19 dev tun0 scope link
141.75.40.250 via 141.75.251.19 dev tun0 scope link
141.75.40.251 via 141.75.251.19 dev tun0 scope link
141.75.64.0/18 via 141.75.251.19 dev tun0 scope link
141.75.128.0/18 via 141.75.251.19 dev tun0 scope link
141.75.192.0/19 via 141.75.251.19 dev tun0 scope link
141.75.224.0/20 via 141.75.251.19 dev tun0 scope link
141.75.240.0/21 via 141.75.251.19 dev tun0 scope link
141.75.248.0/23 via 141.75.251.19 dev tun0 scope link
141.75.250.0/24 via 141.75.251.19 dev tun0 scope link
141.75.251.0/28 via 141.75.251.19 dev tun0 scope link
141.75.251.16/31 via 141.75.251.19 dev tun0 scope link
141.75.251.18 via 141.75.251.19 dev tun0 scope link
141.75.251.20/30 via 141.75.251.19 dev tun0 scope link
141.75.251.24/29 via 141.75.251.19 dev tun0 scope link
141.75.251.32/27 via 141.75.251.19 dev tun0 scope link
141.75.251.64/26 via 141.75.251.19 dev tun0 scope link
141.75.251.128/25 via 141.75.251.19 dev tun0 scope link
141.75.252.0/22 via 141.75.251.19 dev tun0 scope link
141.76.0.0/14 via 141.75.251.19 dev tun0 scope link
141.80.0.0/12 via 141.75.251.19 dev tun0 scope link
141.96.0.0/11 via 141.75.251.19 dev tun0 scope link
141.128.0.0/9 via 141.75.251.19 dev tun0 scope link
142.0.0.0/7 via 141.75.251.19 dev tun0 scope link
144.0.0.0/4 via 141.75.251.19 dev tun0 scope link
160.0.0.0/3 via 141.75.251.19 dev tun0 scope link
192.0.0.0/9 via 141.75.251.19 dev tun0 scope link
192.128.0.0/11 via 141.75.251.19 dev tun0 scope link
192.160.0.0/13 via 141.75.251.19 dev tun0 scope link
192.168.0.0 via 141.75.251.19 dev tun0 scope link
192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.115 metric 600
192.168.0.2/31 via 141.75.251.19 dev tun0 scope link
192.168.0.4/30 via 141.75.251.19 dev tun0 scope link
192.168.0.8/29 via 141.75.251.19 dev tun0 scope link
192.168.0.16/28 via 141.75.251.19 dev tun0 scope link
192.168.0.32/27 via 141.75.251.19 dev tun0 scope link
192.168.0.64/27 via 141.75.251.19 dev tun0 scope link
192.168.0.96/28 via 141.75.251.19 dev tun0 scope link
192.168.0.112/31 via 141.75.251.19 dev tun0 scope link
192.168.0.114 via 141.75.251.19 dev tun0 scope link
192.168.0.116/30 via 192.168.0.1 dev wlp4s0
192.168.0.120/29 via 192.168.0.1 dev wlp4s0
192.168.0.128/25 via 192.168.0.1 dev wlp4s0
192.168.1.0/24 via 141.75.251.19 dev tun0 scope link
192.168.2.0/23 via 141.75.251.19 dev tun0 scope link
192.168.4.0/22 via 141.75.251.19 dev tun0 scope link
192.168.8.0/21 via 141.75.251.19 dev tun0 scope link
192.168.16.0/20 via 141.75.251.19 dev tun0 scope link
192.168.32.0/19 via 141.75.251.19 dev tun0 scope link
192.168.64.0/18 via 141.75.251.19 dev tun0 scope link
192.168.128.0/17 via 141.75.251.19 dev tun0 scope link
192.169.0.0/16 via 141.75.251.19 dev tun0 scope link
192.170.0.0/15 via 141.75.251.19 dev tun0 scope link
192.172.0.0/14 via 141.75.251.19 dev tun0 scope link
192.176.0.0/12 via 141.75.251.19 dev tun0 scope link
192.192.0.0/10 via 141.75.251.19 dev tun0 scope link
193.0.0.0/8 via 141.75.251.19 dev tun0 scope link
194.0.0.0/7 via 141.75.251.19 dev tun0 scope link
196.0.0.0/6 via 141.75.251.19 dev tun0 scope link
200.0.0.0/5 via 141.75.251.19 dev tun0 scope link
208.0.0.0/4 via 141.75.251.19 dev tun0 scope link
224.0.0.0/3 via 141.75.251.19 dev tun0 scope linkI dont't have a firewall running (at least I am not aware of one). I would appreciate any advice, since I don't have more ideas how to find the reason for this strange problem.
Best regards
Oliver
Last edited by onatt (2016-08-25 16:43:49)
Offline
Hey Onatt I am running into the same issue as I am trying arch linux to make sure all my program work correctly before switching. I have found the only way for this to work correctly is running it with "sudo" command as a regular user it connects but does not pass any traffic along. Does is it work when you run it as root?
Edit: Update after hours of researching and testing and comparing to my ubuntu test machine I found that rolling my kernel back to the 4.4 LTS version for Arch that my vpn started working again and my ip table route has entries again. When I was running the latest 4.7.1 kernel I would connect but my route was returning no entries. Maybe somebody can explain how to fix the missing route table within the latest 4.7.1 kernel.
Last edited by sc954rr (2016-08-23 04:00:29)
Offline
Hi sc954rr,
thanks for you hint. On my machine it does not even work, when I rund 'startctui' with 'sudo'. Some time ago, I also tried to rollback to the LTS kernel. But it did not work either. What I did not try is to run startctui with sudo on the LTS kernel. I will try this latter today
Best regards,
Oliver
Offline
Hi sc954rr,
I just installed the LTS kernel (4.4.19-1-lts #1 SMP Sat Aug 20 21:58:36 CEST 2016 x86_64) and now my VPN is working again. It would be really interesting what has been changed between 4.4.19 and the current kernel.
Best regards
Oliver
Last edited by onatt (2016-08-24 14:09:08)
Offline
The following trick solves the problem also with the latest kernel:
As root:
echo 0 > /proc/sys/net/ipv6/conf/default/router_solicitations
afterwards the Dell SonicWall VPN can be started as a regular user.
Offline