05.01.2025 - work-in-progress = definitely not complete...
During installation you were asked for Hostname(FQDN), IP address, Netmask, Gateway and DNS Server. The values you enter must fit to your local network. You can not simply wish to use a random IP address like 1.1.1.1 ;-)
Assumption for the following:
Solution: you need to specify the port number to use as it is not the default one. You need to enter https://192.0.2.26:8006.
Wrong cabling: Make sure both ends of the cable are connected ;-)
Both NIC and the switch should have a small LED signalling “LINK”-presence = an electrical connection has been established.
a) Your router probably has a web interface - take a look at it and you will find the required information somewhere! This is basically the source-of-truth! While you are here search for "DHCP address range" for Ethernet connected devices. Write down an address outside of that range but inside the same network.
b) Linux: open a command prompt and look at the output of
Use the listed name for the next command:
c) Windows: open a CMD prompt and examine the output of:
Now we don’t assume but we know our network is 192.0.2.x/24. If you knew this from the beginning you had already entered an unused address during setup.
"Conflict"-pitfall: make sure to use a non-DHCP address as conflicts (= the use of one specific address by two or more devices at the same time) are really difficult to detect and may generate "strange" behavior!
Check:
The important part is “...state UP” for both the physical NIC “ens18” and the bridge “vmbr0”.
You had entered “incompatible” data during installation. Or perhaps you switched your upstream router after the fact. In any case your current setup does not fit to the actual LAN. Just deep dive into the Linux command line to repair the wrong setting.
There should be two editors available: “vi” (relatively complicated) and “nano” (relatively simple). The network configuration is in a simple textfile, open it with
“ens18” may be different, but it must be identical on both occurrences. Leave the editor, make sure to save your modification. Load the new configuration:
Now you should be able to ping that gateway:
As the gateway is pingable now, it should route traffic to the outside world:
If DNS is configured correctly the same server can be ping’ed by name, in this case:
Todo:
See also
During installation you were asked for Hostname(FQDN), IP address, Netmask, Gateway and DNS Server. The values you enter must fit to your local network. You can not simply wish to use a random IP address like 1.1.1.1 ;-)
Assumption for the following:
- you use the Internet Protocol Version 4 in a home setup behind a normal router/gateway
- your PVE setup is very basic, without bells or whistles: one physical NIC and one logical bridge "vmbr0"
- you use a wired connection, WLAN is basically not supported (#2)
- my Test-PVE is named “pnz”. This is not relevant, but that name is quoted below and you just should know what it means ;-)
- the desired configuration of this PVE: address = 192.0.2.26 / netmask = 255.255.255.0 / gateway = 192.0.2.254 - yours will be different
Trivial misunderstandings act like pitfalls
URL scheme: while doing everything right you entered the IP address of PVE in your browser but it does not work, you only get a “timeout” error message.Solution: you need to specify the port number to use as it is not the default one. You need to enter https://192.0.2.26:8006.
Wrong cabling: Make sure both ends of the cable are connected ;-)
Both NIC and the switch should have a small LED signalling “LINK”-presence = an electrical connection has been established.
Step zero for everything: know your landscape!
To know the data you need to enter during setup (or during re-configuration) you need to know your LAN first. There are several ways to know your actual environment. For this part use another device which is connected to the very same LAN-to-be-used and is working. (Do not use a WLAN-connected device as your PVE is hopefully using Ethernet.)a) Your router probably has a web interface - take a look at it and you will find the required information somewhere! This is basically the source-of-truth! While you are here search for "DHCP address range" for Ethernet connected devices. Write down an address outside of that range but inside the same network.
b) Linux: open a command prompt and look at the output of
Code:
~$ ip route show | grep default
default via 192.0.2.254 dev enp1s0
Code:
~$ ip -4 address show dev enp1s0
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet 192.0.2.123/24 brd 192.0.2.255 scope global dynamic enp1s0c) Windows: open a CMD prompt and examine the output of:
ipconfig - look for “IPv4-address”, “Subnet mask” and “Default gateway” . (Or similar, my Windows is German...)Now we don’t assume but we know our network is 192.0.2.x/24. If you knew this from the beginning you had already entered an unused address during setup.
"Conflict"-pitfall: make sure to use a non-DHCP address as conflicts (= the use of one specific address by two or more devices at the same time) are really difficult to detect and may generate "strange" behavior!
On the PVE
You need to use the physical console, as there is not network yet. ;-) Log in as root.Problem area A: wiring
Both ends of the cable should be plugged in and signalize connectivity.Check:
Code:
root@pnz:~# ip link
1: ...
2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether bc:24:11:9b:f3:b8 brd ff:ff:ff:ff:ff:ff
altname enp0s18
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether bc:24:11:9b:f3:b8 brd ff:ff:ff:ff:ff:ffProblem area B: wrong configuration
Generic help: look at Link #1 for more guidance.You had entered “incompatible” data during installation. Or perhaps you switched your upstream router after the fact. In any case your current setup does not fit to the actual LAN. Just deep dive into the Linux command line to repair the wrong setting.
There should be two editors available: “vi” (relatively complicated) and “nano” (relatively simple). The network configuration is in a simple textfile, open it with
nano /etc/network/interfaces or “vi”. Edit (and save!) that file to look like this:
Code:
root@pnz:~# nano /etc/network/interfaces
Code:
auto lo
iface lo inet loopback
iface ens18 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.0.2.26/24
gateway 192.0.2.254
bridge-ports ens18
bridge-stp off
bridge-fd 0
source /etc/network/interfaces.d/*
Code:
root@pnz:~# ifreload -a # no output = no error ;-)Now you should be able to ping that gateway:
Code:
root@pnz:~# ping 192.0.2.254
PING 192.0.2.254 (192.0.2.254) 56(84) bytes of data.
64 bytes from 192.0.2.254: icmp_seq=1 ttl=64 time=0.291 ms
64 bytes from 192.0.2.254: icmp_seq=2 ttl=64 time=0.332 msAs the gateway is pingable now, it should route traffic to the outside world:
Code:
root@pnz:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=43.1 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=14.7 msIf DNS is configured correctly the same server can be ping’ed by name, in this case:
Code:
root@pnz:~# ping one.one.one.one
PING one.one.one.one (1.1.1.1) 56(84) bytes of data.
64 bytes from one.one.one.one (1.1.1.1): icmp_seq=1 ttl=55 time=21.4 ms
64 bytes from one.one.one.one (1.1.1.1): icmp_seq=2 ttl=55 time=14.7 msTodo:
- DNS - "/etc/resolv.conf" ...
- no Web Gui because no pveproxy listens on 8006
- ...
See also
- #1 https://pve.proxmox.com/wiki/Network_Configuration#_default_configuration_using_a_bridge
- #2 https://pve.proxmox.com/wiki/WLAN
- https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_network_configuration
- https://forum.proxmox.com/search/7994094/?q=FabU&c[title_only]=1&c[users]=UdoB&o=date - some more of this series of posts may be added over time...
Last edited:
