PiVPN, PiHole and Gateway woes

JCB · May 27, 2018, 4:13pm

Hello Folks,

OK, this is a goofy one, and I am really stuck. Hang on for the ride being that I have listed the back story, some steps taken, and the issues is reproducible.

I had recently built a new PC, MoBo, CPU, the works and replaced it with the same old HDD where everything was working as expected before with the previous PC. Obviously i needed to update things for the new video card and Network devices.

Upon testing, after a reboot, I was not able to access the Internet, and noticed that I would loose my gateway, and I found that if I open Debian 9 network manager gui, bounce the wired interface, I would then get the GW and could then access the Internet. Trust me, I will get to the PIHole and PiVPN here soon

I discovered that if I also had wired as well as WiFi, I would get the GW for both the wired and WiFi, but if I connect to the PiVPN I would not be able to connect to the VPN, but if I open the network manager and off / on the wired interface, I would then be able to connect to the VPN, and it would work as expected.

Here are the route -n and ifconfig before and after:

Before

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    202    0        0 enp37s0
0.0.0.0         192.168.50.1    0.0.0.0         UG    303    0        0 wlp36s0
10.8.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
192.168.50.0    0.0.0.0         255.255.255.0   U     202    0        0 enp37s0
192.168.50.0    0.0.0.0         255.255.255.0   U     303    0        0 wlp36s0

ifconfig

enp37s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.70  netmask 255.255.255.0  broadcast 192.168.50.255
        inet6 fe80::7285:c2ff:fe5e:1e20  prefixlen 64  scopeid 0x20<link>
        ether 70:85:c2:5e:1e:20  txqueuelen 1000  (Ethernet)
        RX packets 427791  bytes 558676075 (532.7 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 328483  bytes 25907559 (24.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xf7500000-f751ffff  

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 76257  bytes 914413164 (872.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 76257  bytes 914413164 (872.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.8.0.1  netmask 255.255.255.0  destination 10.8.0.1
        inet6 fe80::eca2:3d08:4e55:5a0e  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 595  bytes 33940 (33.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp36s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.139  netmask 255.255.255.0  broadcast 192.168.50.255
        inet6 fe80::99e1:c5d0:715f:6303  prefixlen 64  scopeid 0x20<link>
        ether 28:c6:3f:16:3b:13  txqueuelen 1000  (Ethernet)
        RX packets 19884  bytes 4803946 (4.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1218  bytes 250339 (244.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

AFTER Wired interface bounce

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    100    0        0 enp37s0
0.0.0.0         192.168.50.1    0.0.0.0         UG    303    0        0 wlp36s0
10.8.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
192.168.50.0    0.0.0.0         255.255.255.0   U     100    0        0 enp37s0
192.168.50.0    0.0.0.0         255.255.255.0   U     303    0        0 wlp36s0

root@Familyroom:/home/jc# ifconfig
enp37s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.70  netmask 255.255.255.0  broadcast 192.168.50.255
        inet6 fe80::7285:c2ff:fe5e:1e20  prefixlen 64  scopeid 0x20<link>
        ether 70:85:c2:5e:1e:20  txqueuelen 1000  (Ethernet)
        RX packets 429247  bytes 560396391 (534.4 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 329658  bytes 26035465 (24.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xf7500000-f751ffff  

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 77427  bytes 931854863 (888.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 77427  bytes 931854863 (888.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.8.0.1  netmask 255.255.255.0  destination 10.8.0.1
        inet6 fe80::eca2:3d08:4e55:5a0e  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 603  bytes 35236 (34.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp36s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.139  netmask 255.255.255.0  broadcast 192.168.50.255
        inet6 fe80::99e1:c5d0:715f:6303  prefixlen 64  scopeid 0x20<link>
        ether 28:c6:3f:16:3b:13  txqueuelen 1000  (Ethernet)
        RX packets 20055  bytes 4848635 (4.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1317  bytes 278803 (272.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Maybe I have been working on this too long, but the only difference that I see is the metric change after the interface bounce.

I do have the Pihole as the DHCP server so I wondered if this was part of the issue, it was not before the build, however I did move DHCP back to the router, and there was no change....

Debug Token:

Your debug token is: osh1zzjrc8

JCB · May 28, 2018, 2:51am

######################

Fixed the issue

######################

Follow up:

I did manage to get this to work, but I am still a bit perplexed why the network configurations needed to be manually configured versus using the network manager. I edited /etc/network/interface and had to add in the routes are well for it to work as expected

#Ethernet
auto enp37s0
iface enp37s0 inet static
address 192.168.50.70
netmask 255.255.255.0
gateway 192.168.50.1
dns-nameservers 192.168.50.70
up route add -net 192.168.50.0 netmask 255.255.255.0 gw 192.168.50.1 
up route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.50.1

Not sure if this was the best way to correct it or not, but wanted to add in these note in the event that there is a way to get this to work with network manager to if someone else is having this issue

JC

system · June 18, 2018, 2:51am

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.