Client VPN connection ok but don't ping
Posted: Mon Apr 27, 2020 8:33 am
Hi,
since few days I cant' access to my machine.
The connection is ok, with AccountStatusGet I see the vpn is connected; but I cant' access at any pc and also ping doesn't work
The virtual interface don't have ip address and there isn't rules on routing table
I use Linux client and for serveral week I use it without any problem.
Why what can I do?
EDIT
This is the resoult of route
And ifconfig
EDIT
The workaround I've found is:
1. run dhclient
2. add manually the correct roules of routing
since few days I cant' access to my machine.
The connection is ok, with AccountStatusGet I see the vpn is connected; but I cant' access at any pc and also ping doesn't work
The virtual interface don't have ip address and there isn't rules on routing table
I use Linux client and for serveral week I use it without any problem.
Why what can I do?
EDIT
This is the resoult of route
Code: Select all
[I] ➜ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 304 0 0 wlp3s0
192.168.1.0 0.0.0.0 255.255.255.0 U 304 0 0 wlp3s0
Code: Select all
[I] ➜ ifconfig
enp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:22:68:0a:1e:b7 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 17
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 1000 (Local Loopback)
RX packets 149 bytes 206583 (201.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 149 bytes 206583 (201.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vpn_vpn2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5c00:eff:fef9:a735 prefixlen 64 scopeid 0x20<link>
ether 5e:00:0e:f9:a7:35 txqueuelen 1000 (Ethernet)
RX packets 7871 bytes 1732596 (1.6 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 484 bytes 40041 (39.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vpn_vpn2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5c00:eff:fef9:a735 prefixlen 64 scopeid 0x20<link>
ether 5e:00:0e:f9:a7:35 txqueuelen 1000 (Ethernet)
RX packets 7871 bytes 1732596 (1.6 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 484 bytes 40041 (39.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::7dc2:719b:48d2:4f23 prefixlen 64 scopeid 0x20<link>
ether 00:22:fa:98:ba:72 txqueuelen 1000 (Ethernet)
RX packets 27622 bytes 20341305 (19.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12330 bytes 1961848 (1.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::7dc2:719b:48d2:4f23 prefixlen 64 scopeid 0x20<link>
ether 00:22:fa:98:ba:72 txqueuelen 1000 (Ethernet)
RX packets 27622 bytes 20341305 (19.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12330 bytes 1961848 (1.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The workaround I've found is:
1. run dhclient
2. add manually the correct roules of routing