[SOLVED] PVE host cannot reach internet despite VMs having access

[jacekp]

Hi,

My proxmox installation cannot access internet. But my guest VMs can.
I have suspected a DNS issue but I set DNS to 8.8.8.8 and it's still not working.

Probably worth noting that local network is working, and I can access the gui from my other machine.

Do you have any suggestions on where I should look for the cause of this issue?

In trying to update it's giving error:

starting apt-get update
Err:1 http://ftp.pl.debian.org/debian bullseye InRelease
  Temporary failure resolving 'ftp.pl.debian.org'
Err:2 http://security.debian.org bullseye-security InRelease
  Temporary failure resolving 'security.debian.org'
Err:3 https://enterprise.proxmox.com/debian/pve bullseye InRelease
  Temporary failure resolving 'enterprise.proxmox.com'
Err:4 http://ftp.pl.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'ftp.pl.debian.org'
Reading package lists...
W: Failed to fetch http://ftp.pl.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'ftp.pl.debian.org'
W: Failed to fetch http://ftp.pl.debian.org/debian/dists/bullseye-updates/InRelease   Temporary failure resolving 'ftp.pl.debian.org'
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease  Temporary failure resolving 'security.debian.org'
W: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease   Temporary failure resolving 'enterprise.proxmox.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
TASK OK

Ping attempt to 8.8.8.8

root@pve:~# 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 ---
7 packets transmitted, 0 received, 100% packet loss, time 6124ms

I have set it to use 1.1.1.1 / 8.8.8.8 DNS, but it can't be reached.
resolv.conf:

root@pve:~# cat /etc/resolv.conf
search NAT.warszawa.vectranet.pl
nameserver 1.1.1.1
nameserver 8.8.8.8
nameserver 127.0.0.53

network interfaces:

root@pve:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp4s0f1 inet manual

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

iface wlp3s0 inet manual

ip route:

root@pve:~# ip route
default via 192.168.0.1 dev vmbr0 proto kernel onlink
192.168.100.0/24 dev vmbr0 proto kernel scope link src 192.168.100.16

 

[nunner]

Hi,

        address 192.168.100.16/24
        gateway 192.168.0.1

can you actually reach your default gateway?

 

[jacekp]

Hi,

Yes, I can ping it from my PVE host shell:

root@pve:~# 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=1.56 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.79 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.72 ms
^C
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2005ms
rtt min/avg/max/mdev = 1.559/1.689/1.786/0.095 ms

 

[vesalius]

How about the other direction? Can the default gateway or anything in the 192.168.0.0 subnet ping 192.168.100.16? What are you using as a router? Does that router know, sometimes requires static routes, where and what interface to use to send data, DNS/web, back to the 192.168.0.0 subnet?

 

[jacekp]

Hi,

Apologies for late reply. The inverse is true, tho after a restart I found out that PVE expects to have a static IP, but it doesn't get it.
PVE expects to be on IP 192.168.100.16, but it got IP 192.168.0.90.

Once the IP changed to be in range 192.168.0 then internet started working. So I believe the problem was in IP mismatch.

Thank you to both of you for your help. One last question - do you know how to mark this thread as solved?

 

[vesalius]

Edit your original First post. Click the "No Prefix" adjacent the thread title and select "solved from the drop-down menu/popup. Save the edit.

 

[jacekp]

Done, thank you.

 

[weedse]

I got my gateway in range but my internet doesnt seem to work...
I got 192.168.2.12 and gateway 192.168.2.1
VM seem to have internet no problem but I cant apt update or use any other shell scripts to install stuff
(also 100% packet loss on basic pings to google etc)

 

[sw-omit]

I got my gateway in range but my internet doesnt seem to work...
I got 192.168.2.12 and gateway 192.168.2.1
VM seem to have internet no problem but I cant apt update or use any other shell scripts to install stuff
(also 100% packet loss on basic pings to google etc)

1. Why hyjack a 1,5 year old post instead of posting a new thread, you can always just link back to what you've already looked at? Because it's marked as solved, quite often it's just skipped over by people too.
2. Let's start smaller, can you ping your router, and do you ping google via it's (DNS-)name, google.com, or via it's (IPv4) IP, 8.8.8.8?