[SOLVED] Host can't access internet but VMs can?

[burg]

I've had proxmox running for quite a few months now on a Lenovo Tiny but only just realised that the host can't reach the internet today when I went to try and install some Google Coral drivers and was met with internet access issues with apt-get. I never spotted this before as the VMs I have running on the machine all have external internet access and no problems.... The machine is connected to an Eero hub via Ethernet. I haven't really touched the host since initial setup so don't think I've changed anything to cause this.

Some things off the top of my head that might be useful?

Host (192.168.4.45)
- Pinging google.com times out
- Traceroute to 8.8.8.8 ends on 1 hop to lenovo.local

VM1 (192.168.5.73)
- Pinging google.com works fine
- Traceroute to 8.8.8.8 ends on 10 hops and reaches dns.google

Both have this in the resolv.conf:

root@lenovo:~# cat /etc/resolv.conf
nameserver 8.8.8.8

Networking is my weakest area by a long shot so please bear with me and please let me know what I need to provide to start diagnosing this...Thanks for any help, hopefully it's a pretty basic question!

 

[Dunuin]

cat /etc/network/interfaces of your host would be useful. I guess you setup a wrong gateway for your host but a correct one for your guests.

 

[burg]

cat /etc/network/interfaces of your host would be useful. I guess you setup a wrong gateway for your host but a correct one for your guests.

I'm not that familiar with network setup so setting up a wrong gateway would have been an accident if so, if it was optional during setup I'd have taken that route I'd have thought! This is on the host :

# comment lines....

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.4.45/24
        gateway 192.168.100.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

ip r shows default via 192.168.4.1 on the VMs that DO have internet access. Is it likely the host needs changing to the same (looks like it can ping it successfully)? I don't want to risk losing access so a bit reluctant without the knowledge.

 

[Dunuin]

If "192.168.100.1" isn't your router you shouldn't use it as a gateway. If you access your PVE host using "192.168.4.45/24" I would guess your gateway should be "192.168.4.1". So edit that line (or edit the vmbr0'S gateway using thr WebUI) to your routers IP in the 192.168.4.X subnet and run systemctl restart networking.

 

[burg]

If "192.168.100.1" isn't your router you shouldn't use it as a gateway. If you access your PVE host using "192.168.4.45/24" I would guess your gateway should be "192.168.4.1". So edit that line (or edit the vmbr0'S gateway using thr WebUI) to your routers IP in the 192.168.4.X subnet and run systemctl restart networking.

That easy eh! All working now, glad it was an easy solution but feel foolish for posting now! Thanks!