[SOLVED] No internet at Host

turkel

Member
Nov 16, 2019
9
1
8
34
Hello, So yet another internet issue with proxmox setup. All VMs LXCs are ok and I am also able to access proxmox ip to manage it, but node is not able to get access to internet. Cant ping to google, gateway ip but able to ping itself and VMs.

ip -c a
Bash:
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
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether f8:b1:56:bb:26:28 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet6 fe80::fab1:56ff:febb:2628/64 scope link
       valid_lft forever preferred_lft forever
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 12:7f:9a:38:fd:fd brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.10/24 brd 192.168.1.255 scope global dynamic vmbr0
       valid_lft 484sec preferred_lft 484sec
    inet6 fe80::107f:9aff:fe38:fdfd/64 scope link
       valid_lft forever preferred_lft forever
4: veth107i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP group default qlen 1000
    link/ether fe:9e:0d:78:e1:2a brd ff:ff:ff:ff:ff:ff link-netnsid 0
5: fwbr107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:90:57:d0:b3:66 brd ff:ff:ff:ff:ff:ff
6: fwpr107p0@fwln107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether ae:61:59:05:7a:ef brd ff:ff:ff:ff:ff:ff
7: fwln107i0@fwpr107p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP group default qlen 1000
    link/ether 92:89:d5:9b:28:c2 brd ff:ff:ff:ff:ff:ff
8: veth108i1@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i1 state UP group default qlen 1000
    link/ether fe:e1:9e:1a:90:32 brd ff:ff:ff:ff:ff:ff link-netnsid 1
9: fwbr108i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6a:cb:98:af:e5:89 brd ff:ff:ff:ff:ff:ff
10: fwpr108p1@fwln108i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 5a:74:01:3a:bc:07 brd ff:ff:ff:ff:ff:ff
11: fwln108i1@fwpr108p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i1 state UP group default qlen 1000
    link/ether c6:d1:3c:63:32:25 brd ff:ff:ff:ff:ff:ff
12: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether b2:c3:a1:5e:a9:bf brd ff:ff:ff:ff:ff:ff
13: tap116i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether 52:5e:0f:f9:43:1a brd ff:ff:ff:ff:ff:ff

/etc/network/interfaces
Bash:
auto lo
iface lo inet loopback

auto enp0s25
iface enp0s25 inet manual

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet dhcp
        bridge-ports enp0s25
        bridge-stp off
        bridge-fd 0

/etc/resolv.conf
Bash:
nameserver 192.168.1.1
nameserver 81.21.XX.XX
nameserver 8.8.8.8

/etc/hosts
Bash:
127.0.0.1 localhost.localdomain localhost
192.168.1.10 MyServer.doain.com MyServer

# 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

It is been almost a day I am on it and still no luck, please take a look, I am sure someone able to solve issue easily as my setup pretty standart with dhcp.


Regards,
Turkel.
 
The host probably has no route - it's usual to give the host a static IP and gateway

what does ip route show?
 
I use dhcp becouse it is easy to see status of all VMs in Mikrotik router DHCP server, I assign static ip through DHCP already.

ip route
Bash:
default via 192.168.1.1 dev vmbr0
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.10
 
My route info looks slightly different to yours

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.250

try
ip route replace to default via 192.168.1.1 dev vmbr0 proto kernel onlink

and see if that gives the host internet access
 
after running:
ip route replace to default via 192.168.1.1 dev vmbr0 proto kernel onlink

ip route
Bash:
default via 192.168.1.1 dev vmbr0
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.10

and Host which is 192.168.1.10 still not have internet and cant ping gateway 192.168.1.1
 
Last edited:
I have checked many forms and most of them says this issue happened after upgrade to proxmox v 7 like I did. Actually I have upgraded several month ago but didnt checked host as I dont need to, but now it is mandotary due to some change need to be applied to host.
 
your most obvious step here is to set the host IP and gateway as static, reboot and test
 
  • Like
Reactions: turkel
No luck :((((((
here are the changes after setting static IP:


ip -c a
Bash:
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
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether f8:b1:56:bb:26:28 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet6 fe80::fab1:56ff:febb:2628/64 scope link
       valid_lft forever preferred_lft forever
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 12:7f:9a:38:fd:fd brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.10/24 brd 192.168.1.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::107f:9aff:fe38:fdfd/64 scope link
       valid_lft forever preferred_lft forever
4: veth107i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP group default qlen 1000
    link/ether fe:35:cc:b9:01:86 brd ff:ff:ff:ff:ff:ff link-netnsid 0
5: fwbr107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:90:57:d0:b3:66 brd ff:ff:ff:ff:ff:ff
6: fwpr107p0@fwln107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether ae:61:59:05:7a:ef brd ff:ff:ff:ff:ff:ff
7: fwln107i0@fwpr107p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP group default qlen 1000
    link/ether 92:89:d5:9b:28:c2 brd ff:ff:ff:ff:ff:ff
8: veth108i1@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i1 state UP group default qlen 1000
    link/ether fe:da:af:84:a0:ad brd ff:ff:ff:ff:ff:ff link-netnsid 1
9: fwbr108i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6a:cb:98:af:e5:89 brd ff:ff:ff:ff:ff:ff
10: fwpr108p1@fwln108i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 5a:74:01:3a:bc:07 brd ff:ff:ff:ff:ff:ff
11: fwln108i1@fwpr108p1: <BROADC
AST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i1 state UP group default qlen 1000
    link/ether c6:d1:3c:63:32:25 brd ff:ff:ff:ff:ff:ff
12: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether b2:c3:a1:5e:a9:bf brd ff:ff:ff:ff:ff:ff
13: tap116i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether 52:5e:0f:f9:43:1a brd ff:ff:ff:ff:ff:ff


/etc/network/interfaces
Bash:
auto lo
iface lo inet loopback

auto enp0s25
iface enp0s25 inet manual

auto eno1
iface eno1 inet manual

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

/etc/resolv.conf
Code:
nameserver 192.168.1.1
nameserver 81.21.XX.XX
nameserver 8.8.8.8

/etc/hosts
Code:
127.0.0.1 localhost.localdomain localhost
192.168.1.10 MyServer.maydomain.com MayServer

# 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
 
Last edited:
Dear all,
We are facing the same issue, we have upgraded our host to proxmox 7 and old configuration is no longer working, we have followed the pve wiki guide but we are unable to access our vm and cannot access them over internet. Any help will be greatly appreciated.
We also followed the configuration described above but it is not working.
 
Last edited:
  • Like
Reactions: turkel
Dear all,
We are facing the same issue, we have upgraded our host to proxmox 7 and old configuration is no longer working, we have followed the pve wiki guide but we are unable to access our vm and cannot access them over internet. Any help will be greatly appreciated.
We also followed the configuration described above but it is not working.
This is normally down to the nic interface names changing - please post the output of ip a on the host and the contents of your /etc/network/interfaces file
 
So this issue still not solved!
I got new SSD and installed fresh Proxmox so result is same, no internet at host, even right after the installation was done. All above interfaces, resolv.conf hosts networking have been checked, no luck.
 
So I need to get agree before solving the issues :p
The issue is with my Mikrotik Router, I have changed NIC and kept server IP same so Mikrotik stored old NIC MAC and blocked access to same IP with new NIC. Very wise of you Mikrotik :D
So People, before complaning about networking issues also check your router/switch parametrs too.

Thanks for all for all your attempts to solve my issue.
 
  • Like
Reactions: vesalius
So I need to get agree before solving the issues :p
The issue is with my Mikrotik Router, I have changed NIC and kept server IP same so Mikrotik stored old NIC MAC and blocked access to same IP with new NIC. Very wise of you Mikrotik :D
So People, before complaning about networking issues also check your router/switch parametrs too.

Thanks for all for all your attempts to solve my issue.
I have the same issue. Did you change Mikrotik's settings? Could you share solution?
 
I had the same issue with TL-WR829N. I've toggled NAT and LAN Ping and after that proxmox was able to connect to internet. :(
 

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!