Fresh install sees network but not internet

F

FirmwareMan3000

New Member
Feb 5, 2021
3
0
1
47
I bought a used Dell Poweredge R720 as a compilation machine and for a ZFS z3 share.
I'm trying out Proxmox VE 6.2.

For some reason Proxmox can't see the internet, but all other bare-metal OSes I've tried on the HW can see it just fine.
Proxmox can see the rest of my network and the network can see it, so I'm at a loss.
Can someone a lot smarter than me point me in the correct direction?

Here are the outputs of some usual commands:

root@poweredge:~# 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
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether c8:1f:66:e8:39:3d brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c8:1f:66:e8:39:3e brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c8:1f:66:e8:39:3f brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c8:1f:66:e8:39:40 brd ff:ff:ff:ff:ff:ff
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c8:1f:66:e8:39:3d brd ff:ff:ff:ff:ff:ff
inet 192.168.0.15/24 brd 192.168.0.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::ca1f:66ff:fee8:393d/64 scope link
valid_lft forever preferred_lft forever

root@poweredge:~# ip r
192.168.0.0/24 dev vmbr0 proto kernel scope link src 192.168.0.15

Any help is appreciated.
 
Sorry for the late reply. I'm in the Los Angeles area (GMT-8) time zone.
Thank you for the assistance. Here's the info you asked for:

root@poweredge:~# 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 eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.0.15/24
gateway 192.168.0.15
bridge-ports eno1
bridge-stp off
bridge-fd 0
 
Last edited:
Figured it out.
After installing Proxmox VE 6.3 and trying several other things, I realized it was the gateway and DNS settings.

I've never had to ensure correctness of those numbers before when installing an OS. Now I know.

For any one else who run across this issue:
The "gateway" IP addr asked for by the Proxmox installer is whatever your router has assigned to itself.
In my case 192.168.0.1.
The router then DHCPs address starting at 192.168.0.2

My router also listed the DNS servers provided by my ISP. The IP addr can be modified in /etc/resolv.conf.
 
Hi,

I have the very same problem and similar network config as the op but I had already configured the gateway/dns and still cannot connect to the internet.

I'm very new to proxmox, not sure how to diagnose where the problem is and would appreciate any help ?

:~# ip route
default via 10.168.33.1 dev vmbr0 proto kernel onlink
10.168.33.0/24 dev vmbr0 proto kernel scope link src 10.168.33.76

:~# ip neigh
10.168.33.78 dev vmbr0 lladdr b4:2e:99:3d:d4:2a REACHABLE
10.168.33.1 dev vmbr0 FAILED

:~# iptables -nvL
Chain INPUT (policy ACCEPT 16912 packets, 6785K bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 11723 packets, 6648K bytes)
pkts bytes target prot opt in out source destination



:~# ip addr
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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:a5:12:b8:32:86 brd ff:ff:ff:ff:ff:ff
inet6 fe80::2a5:12ff:feb7:2286/64 scope link
valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:a6:12:a8:32:87 brd ff:ff:ff:ff:ff:ff
4: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:a6:12:a8:32:88 brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:a6:12:a8:32:89 brd ff:ff:ff:ff:ff:ff
6: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:a6:12:a8:32:8a brd ff:ff:ff:ff:ff:ff
7: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 00:a6:12:a8:32:8b brd ff:ff:ff:ff:ff:ff
8: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:a6:12:a8:32:8b brd ff:ff:ff:ff:ff:ff
inet 10.168.33.76/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::2a5:12ff:feb7:228b/64 scope link
valid_lft forever preferred_lft forever




:~# 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 enp6s0 inet manual

auto enp1s0
iface enp1s0 inet manual

iface enp2s0 inet manual

iface enp3s0 inet manual

iface enp4s0 inet manual

iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.168.33.76/24
gateway 10.168.33.1
bridge-ports enp6s0
bridge-stp off
bridge-fd 0


:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:86 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:87 brd ff:ff:ff:ff:ff:ff
4: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:88 brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:89 brd ff:ff:ff:ff:ff:ff
6: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:8a brd ff:ff:ff:ff:ff:ff
7: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:8b brd ff:ff:ff:ff:ff:ff
8: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 00:a6:12:a8:32:8b brd ff:ff:ff:ff:ff:ff
 
Last edited:
from your proxmox host can you ping 10.168.33.1 and can you ping 8.8.8.8
 
bobmc said:
from your proxmox host can you ping 10.168.33.1 and can you ping 8.8.8.8
Click to expand...
Thank you for the quick response

no, I can't ping either of those.
:~# ping 10.168.33.1
PING 10.168.33.1 (10.168.33.1) 56(84) bytes of data.
From 10.168.33.76 icmp_seq=1 Destination Host Unreachable
From 10.168.33.76 icmp_seq=2 Destination Host Unreachable
From 10.168.33.76 icmp_seq=3 Destination Host Unreachable

:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 10.168.33.76 icmp_seq=1 Destination Host Unreachable
From 10.168.33.76 icmp_seq=2 Destination Host Unreachable
From 10.168.33.76 icmp_seq=3 Destination Host Unreachable

Interestingly, if I ping my managment PC wifi IP, it's also unreachable but if I ping the lan ip (lan cable direct from pc to management port on the proxmox box (lan on port 6, wan is on port 1)) then I'm no longer getting 'host unreachable' but it just sits there without any response or update until I cancel the ping which shows ping results of hundreds of packets sent, 0 received

Also, while you were responding I had also edited my previous comment to include iptables and ip neigh results, the latter showing that vmbr0 FAILED but I don't know how to fix it.
During install (ISO install), the dhcp worked and I could see the IP request in my router which assigned an address from the dhcp pool.
I changed to a static IP outside the pool and continued the installation. Since restarting and first boot of proxmox I no longer see the proxmox box as a client in the asus merlin network clients.

I've also tried a proxmox reinstall and leaving the DHCP assigned IP address but same issue. No internet access from proxmox, can't ping gateway etc etc

1644717952461.png
 
Last edited:
Just a side question: do you use VLANs in your network? Does anything change when you enable „VLAN aware“ in your vmbr0?
 
Huch said:
Just a side question: do you use VLANs in your network? Does anything change when you enable „VLAN aware“ in your vmbr0?
Click to expand...
Hi,
Thanks Huch.
Not yet. I intend to use VLANs but that is separate at this point.
I did try the vlan aware on vmbr0 but it didn't change anything.
For now I'm just building the 'new' network, isolated from the old one.
The plan is to migrate away from the asus merlin router (so no vlans yet) to a protectli like 6 port fanless box (i7 AES with intel nic).
I was playing around with pfsense on it (which was humming along nicely with 4 vlans) before reading advice on using proxmox to have pfsense on a vm so I blew away the pfsense build (afte rbacking up first) and started down the path of the proxmox install (to be followed by a pfsense vm and vlans setup) but stumbled at the first hurdle after the proxmox install finished, so I'm nowhere near getting to VMs, pfsense or the vlan build yet.

Right now it's a laptop direct lan to port 6 on the fanless proxmox box (which was defined as the management port during the install config) and a lan from the asus router to port 1 on the proxmox/fanless (which will eventually be the wan from the modem.
The intention was to use the asus router just for updates and config before installing pfsense in a vm container (almost everything I wanted was identical to this guide https://circuitguy.medium.com/home-network-virtualized-pfsense-install-f9f3279db446) but I can't even do an 'apt update' on first boot.
I keep reading about issues with proxmox 7/Debian new systemd version that changes how the MAC addresses of Linux network bridge devices are calculated.

With Proxmox VE 7 / Debian Bullseye, a new systemd version is used, that changes how the MAC addresses of Linux network bridge devices are calculated. (ref https://forums.lawrencesystems.com/...an-aware-bridge-on-active-backup-bond/10699/4)

Seems all was fine in proxmox 6.4 until this change in v7
I tried the config from se_marc on Jul 15 2021 at this link
https://forum.proxmox.com/threads/p...e-causes-no-internet.92529/page-2#post-403414
but that didn't work either.
sry for the rant !!! :D but I've spent the last 2 days trying to get proxmox up and running from just a bare install.
I don't know if it's me, the fanless box or proxmox but might have to try some other VM if I can't get this sorted, which is a shame because I really like everything else about proxmox ;)
 
Last edited:
Is 10.168.33.1 the ip address of your isp router - or something else?
Can you ping 10.168.33.1 from a physical device on your network - either LAN or Wifi?
 
is enp6s0 connected directly to the isp router or is there a network switch between them?
 
bobmc said:
Is 10.168.33.1 the ip address of your isp router - or something else?
Can you ping 10.168.33.1 from a physical device on your network - either LAN or Wifi?
Click to expand...
10.168.33.1 is the asus router which is bridged to the isp modem.
lan cable from lan port on asus router is connected to port 1 (enp1s0)
Can ping 10.168.33.1 from every other device on the network, both physical lan and wifi.
The proxmox box is the only exception when using either static or dhcp.

bobmc said:
is enp6s0 connected directly to the isp router or is there a network switch between them?
Click to expand...
enp6s0 is the management port with the laptop only connected to it. No intermediate switch.
Its the only way I can connect to the proxmox box.
Nothing else on the network can see the proxmox box when it has dhcp or static IP
 
Last edited:
Gavcol said:
10.168.33.1 is the asus router which is bridged to the isp modem.
lan cable from lan port on asus router is connected to port 1 (enp1s0)
Can ping 10.168.33.1 from every other device on the network, both physical lan and wifi.
The proxmox box is the only exception when using either static or dhcp.


enp6s0 is the management port with the laptop only connected to it. No intermediate switch.
Its the only way I can connect to the proxmox box.
Nothing else on the network can see the proxmox box when it has dhcp or static IP
Click to expand...
So I can see from your earlier comments that you're planning to install pfSense and have this become your LAN router. So I imagine enp1s0 is going to be your WAN port.

However, because your proxmox host is connected to the ISP router on port 1 which doesn't have a route or gateway, proxmox is sending all the internet traffic out of enp6s0 which is connected to your laptop only.

So really need to define and understand what your network settings are going to be, then download pfsense to your laptop, give vmbr0 and your laptop an ip address in your new LAN subnet, upload the pfsense iso to proxmox storage, create a pfsense vm with one nic on vmbr0 and another connected to enp1s0, give pfsense a LAN address which will become the new LAN gateway, set this new gateway on vmbr0 and you should be routing traffic through pfsense
 
@bobmc Thanks so much for all your help and sticking with me on this ;)
bobmc said:
So I can see from your earlier comments that you're planning to install pfSense and have this become your LAN router. So I imagine enp1s0 is going to be your WAN port.
Click to expand...
Yes, exactly

bobmc said:
However, because your proxmox host is connected to the ISP router on port 1 which doesn't have a route or gateway, proxmox is sending all the internet traffic out of enp6s0 which is connected to your laptop only.
Click to expand...
Oh holy gawwd !!!! So the linux bridge wasn't pointed to the right nic/port and all I had to do to get the internet going was change the bridge port from enp6s0 to enp1s0 and with that, I'm able to now run the apt update.
I could have sworn I tried that yesterday already and it didn't work. Maybe it was when I had stuffed around with my DNS at the same time, but either way, it was right there in front of me. So embarrassing !!!

bobmc said:
So really need to define and understand what your network settings are going to be, then download pfsense to your laptop, give vmbr0 and your laptop an ip address in your new LAN subnet, upload the pfsense iso to proxmox storage, create a pfsense vm with one nic on vmbr0 and another connected to enp1s0, give pfsense a LAN address which will become the new LAN gateway, set this new gateway on vmbr0 and you should be routing traffic through pfsense
Click to expand...
Yes, I have the design already drafted (at a high level) of vlans 1-5 and subnets. Also have pfsense iso ready to go.
I'll have
- a managed switch physically on nic 2 (enp2s0) all for vlan 2 only (main network with vpn for PCs, laptops, Nas)
- an ubiquiti AP physically on nic 3 (enp3s0) for vlans 2, 3(devices not using vpn), 4(guest wifi) & 5(IoT). I have the vlans already setup and working in the AP.

Though I'm expecting the proxmox bridges configs may trip me up for pfsense.
Just to check I understand you correctly, do you mean :
- Create pfsense vm with a nic (any nic, say enp4s0) on vmbr0 (in the pfsense vm ?)
- and another nic (say enp5s0) on enp1s0 ? (in the pfsense vm again ? this one I'm confused about)
- give pfsense an IP which becomes the new gateway (no prob with that one)
- change the gateway on vmbr0 to the new gateway ip (no prob there)
- OVS bridge enp2s0 to vmbr0 (giving managed switch routing to internet)
- OVS bridge enp3s0 to vmbr0 (giving ubiquiti AP routing to internet)
- recreate the vlans and firewall rules in pfsense to control what vlans get to go to the internet and which of them with or without vpn (hoping the bridging in proxmox is done right or I'll be stuffing around with them too for a week !! :D :D)
 
Last edited:
  • Like
Reactions: tofugeek
Yes, if the vmbr is vlan aware and you tag vlan 5 on the Home Assistant VM and on the switch port
 
  • Like
Reactions: Gavcol
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom