Proxmox No internet But VM does

[Phiggles]

Hi All, I used a usb key installer iso to install proxmox 8 on bare metal and went through the onscreen setup - no modifying of the interfaces file and such.
I can access proxmox via the browser on IP 192.168.0.192.
A windows VM is installed and can browse the internet and get updates. When i try to update proxmox i get errors of unable to fetch, then when i try ping 8.8.8.8 it fails - but i can ping my gateway 192.168.0.1.

I have seen several people with similar issues and some are DNS, I am totally new to this so its a bit of a learning curve. from other posts i have seen users request certain commands to be run, so i have tried them to be able to provide as much info as I can.

Thanks for reading and hopefully point me in the right direction.

Phil

My network connection;


ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 00:f1:f5:2f:81:08 brd ff:ff:ff:ff:ff:ff
3: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:f1:f5:2f:81:07 brd ff:ff:ff:ff:ff:ff
4: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:8a:d8:c9:01:df brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:f1:f5:2f:81:08 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.192/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::2f1:f5ff:fe2f:8108/64 scope link
       valid_lft forever preferred_lft forever
7: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000
    link/ether 86:38:31:25:fc:92 brd ff:ff:ff:ff:ff:ff
8: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 8a:42:6c:f2:3b:95 brd ff:ff:ff:ff:ff:ff
9: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether c6:1c:c9:79:d2:ec brd ff:ff:ff:ff:ff:ff
10: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
    link/ether 8a:42:6c:f2:3b:95 brd ff:ff:ff:ff:ff:ff

ip route

default via 192.168.0.1 dev vmbr0 proto kernel onlink
192.168.0.0/24 dev vmbr0 proto kernel scope link src 192.168.0.192

ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.03 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.54 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.43 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.44 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1.42 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.866 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1.37 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1.40 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.45 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=1.41 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.52 ms
^C
--- 192.168.0.1 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10062ms
rtt min/avg/max/mdev = 0.866/1.443/2.026/0.251 ms

ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5105ms

cat /etc/network/interfaces

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp1s0 inet manual

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.192/24
        gateway 192.168.0.1
        bridge-ports enp1s0
        bridge-stp off
        bridge-fd 0

iface wlp2s0 inet manual

source /etc/network/interfaces.d/*

cat /etc/resolv.conf

search cable.virginm.net
nameserver 192.168.0.1

cat /etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.0.192 pve.cable.virginm.net pve

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

traceroute 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  4.488 ms  4.470 ms  4.494 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

 

[KevinS]

Are you sure 192.168.0.1 is your Gateway/Router? Everything is looking fine, otherwise your router doesn't route packages from 192.168.0.192 for some reason.
Which IP and gateway does your guest use?

 

[Phiggles]

Hi Kevin,

Yes - Im sure the gateway is correct, my laptop, also logging into the router shows the same 192.168.0.1 as well as the windows VM on the host that cannot access the internet.
Attached are the Windows VM ipconfig - the only thing i can see is the dns addresses are not what is in proxmox DNS menu.......

May have to shut everything down and give the router a reboot......?

Thanks Phil





Mac os gateway

 

[Phiggles]

Hi Kevin, Im so sorry , after looking in my router settings again - i had assign IPs before to 'Known" equipment including the hardware that is running proxmox - at somepoint I applied a mac filter temporarily to it - I had left this on. At least your sanity check of my config proved it should work an your comment 'otherwise your router doesn't route packages from 192.168.0.192 for some reason.' prompted me to look deeper.

Thank you