No Internet on Host

Meniny

New Member
Sep 12, 2024
1
0
1
Hello. I'm new to this.

A few days ago, I installed Proxmox VE on my PC, and everything was running fine until last night when I discovered that the host machine could no longer access the internet. However, all virtual machines are functioning properly and can access the internet without any issues. So, after backing up all the virtual machines, I reinstalled Proxmox VE, but the host machine still couldn't access the internet. This PC is connected via 2 Ethernet cables to my TPLink router, which is in bridge mode. Usually, when my computer or phone reconnects to WiFi, the IP address tends to change frequently.

I have tried:

  • Unplug one Ethernet cable, diable enp1s0/enp2s0
  • Reinstall Proxmox
  • Restart router
  • Change IP in /etc/network/interfaces
  • Reboot

Any ideas?

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

auto enp1s0
iface enp1s0 inet manual

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

auto enp2s0
iface enp2s0 inet dhcp

auto wlp3s0
iface wlp3s0 inet manual


source /etc/network/interfaces.d/*


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

iface enp1s0 inet manual

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

iface enp2s0 inet manual

iface wlp3s0 inet manual


source /etc/network/interfaces.d/*

Bash:
root@pve:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.10 pve.hotodogo.com 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

Bash:
root@pve:~# 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 mq master vmbr0 state UP group default qlen 1000
    link/ether e0:51:d8:13:8d:74 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether e0:51:d8:13:8d:75 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.20/24 brd 192.168.1.255 scope global dynamic enp2s0
       valid_lft 84184sec preferred_lft 84184sec
    inet6 2409:8a56:3220:d00:e251:d8ff:fe13:8d75/64 scope global dynamic mngtmpaddr
       valid_lft 259121sec preferred_lft 172721sec
    inet6 fe80::e251:d8ff:fe13:8d75/64 scope link
       valid_lft forever preferred_lft forever
4: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether c0:4b:24:c1:00:74 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 e0:51:d8:13:8d:74 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.10/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::e251:d8ff:fe13:8d74/64 scope link
       valid_lft forever preferred_lft forever
6: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
    link/ether 2e:05:f4:29:89:ef brd ff:ff:ff:ff:ff:ff
7: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 06:8a:a5:69:ca:44 brd ff:ff:ff:ff:ff:ff
8: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether aa:d9:5f:4f:33:54 brd ff:ff:ff:ff:ff:ff
9: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether 06:8a:a5:69:ca:44 brd ff:ff:ff:ff:ff:ff

Bash:
root@pve:~# ping bing.com
ping: bing.com: Temporary failure in name resolution

Bash:
root@pve:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.16 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.14 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.07 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.17 ms
^C
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.073/1.135/1.167/0.037 ms

Bash:
root@pve:~# nmap -sP "192.168.1.*"
Starting Nmap 7.93 ( https://nmap.org ) at 2024-09-13 05:26 CST
Nmap scan report for 192.168.1.1
Host is up (0.00099s latency).
MAC Address: FC:8D:13:A7:51:F0 (Unknown)
Nmap scan report for 192.168.1.2
Host is up (0.00047s latency).
MAC Address: C8:75:F4:71:3A:41 (Unknown)
Nmap scan report for 192.168.1.8
Host is up (0.031s latency).
MAC Address: 8C:B8:7E:1C:48:7D (Intel Corporate)
Nmap scan report for 192.168.1.9
Host is up (0.00012s latency).
MAC Address: BC:24:11:29:1B:95 (Unknown)
Nmap scan report for pve.hotodogo.com (192.168.1.10)
Host is up.
Nmap scan report for 192.168.1.20
Host is up.
Nmap done: 256 IP addresses (6 hosts up) scanned in 28.01 seconds

Bash:
root@pve:~# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 120.196.165.24
nameserver 211.136.192.6

Code:
root@pve:~# ip route
default via 192.168.1.1 dev vmbr0 proto kernel onlink
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.10
192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.20

Bash:
root@pve:~# apt update
Ign:1 http://security.debian.org bookworm-security InRelease
Ign:2 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
Ign:3 http://ftp.debian.org/debian bookworm InRelease
0% [Connecting to ftp.debian.org] [Connecting to security.debian.org] [Connecting to enterprise.pro^C
root@pve:~#

Bash:
root@pve:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

PLEASE HELP! I can't even install zsh on the host now.
 
Last edited:
By setting DHCP on enp2s0 you have configured the same network twice. You can set vmbr0 to DHCP and set enp2s0 back to manual. It seems like you have a DNS issue as well (not sure if it is just because you configured the same network twice). Can you try pinging 8.8.8.8 ?
 
  • Like
Reactions: Meniny

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!