[SOLVED] Networking vlan - Web interface not reachable in vlan

[nobody0815]

Hello Community,

i'm new to Proxmox and i startet with it a few weeks ago.
I've migratet a few VMs from ESX to proxmox. After a misconfiguration in Bios and an Reset, i've the Problem that the interface isn't reachable any more.

But only on one LAN Socket.
Normally i use only the enp10s0 and everything works fine, except the Web Interface.
I've splittet the Network in a few vlan, and my PC is in vlan 2 - vmbr2.
vmbr100 is the Internet Port. The traffic from my pc is routet via vmbr2 (Gateway 10.0.1.1) over the vmbr1.100 and is ok. If i connect the eno1 in the switch Port with the VLAN ID 2 (vmbr1.2) the interface is reachable on both adresses (10.0.1.5 and 10.0.1.7).
Does anybody have an idea?

 

[vesalius]

In your final state do you intend to use both eno1 and enp10s0 ports or only enp10s0 for both internet (wan) and internal networks (lan)?

specifically, to put the proxmox Management IP on vlan2, using a VLAN aware linux bridge (vmbr1), you would move the CIDR 10.0.1.7/24 and gateway 10.0.1.1 to the vmbr1.2 line and not need the vmbr2 line at all. See Example: Use VLAN 5 for the Proxmox VE management IP with VLAN aware Linux bridge

Similarly, You could also move the CIDR 10.0.5.5/24 to the vmbr1.5 line and CIDR 10.0.6.5/24 to the vmbr1.6 line and do away with vmbr5 and vmbr6.

vm/lxc guest can all use the VLAN aware vmbr1 linux bridge directly when you create their network devices just assign whatever VLAN tag you require (2-4094 supported by default) in the guest network card using vmbr1 as the bridge. You do not have to create each VLAN separately for this to work.

VLAN awareness on the Linux bridge: In this case, each guest’s virtual network card is assigned to a VLAN tag, which is transparently supported by the VLAN aware Linux bridge.

 

[nobody0815]

Hi vesalius,

thanks for your reply! I want to use only one ethernet connection (enp10s0).
I know, that it's possible to eliminate all vmbr >1 but i liked it to have the text note available and not adding the vlanID manually.
I'ts a kind a comfort, don't remember the ID when adding new NIC to the VM:



After changing config, still the same Problem (also testet before):
10.0.1.7 and 10.0.1.5 not reachable until plug in the eno1


even no Ping to Proxmox. To the VM is no problem - with or without the eno1 active in VLAN 2 over the switch.
Any other hint?

 

[vesalius]

What does the /etc/network/interfaces file look like? I suspect you might inadvertently be mixing the 2 examples below from this link (VLAN 802.1Q), but I can't tell from the GUI pic-
Example: Use VLAN 5 for the Proxmox VE management IP with traditional Linux bridge
Example: Use VLAN 5 for the Proxmox VE management IP with VLAN aware Linux bridge

Another option to try is simply removing the VLAN aware checkbox from vmbr1, given you are defining the VLANs and I think most closely following the Example: Use VLAN 5 for the Proxmox VE management IP with traditional Linux bridge example.

 

[nobody0815]

Thank you again,
I'll try, if Im. @home - cant check now

I've passed the link and found this in my config - "auto enp10s0" is too much?

Here's the etc/network/interfaces:
auto lo iface lo inet loopback iface eno1 inet manual auto enp10s0 iface enp10s0 inet manual auto vmbr0 iface vmbr0 inet static address 10.0.1.5/24 bridge-ports eno1 bridge-stp off bridge-fd 0 auto vmbr1 iface vmbr1 inet manual bridge-ports enp10s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 auto vmbr1.100 iface vmbr1.100 inet manual auto vmbr1.2 iface vmbr1.2 inet manual auto vmbr100 iface vmbr100 inet manual bridge-ports vmbr1.100 bridge-stp off bridge-fd 0 auto vmbr1.3 iface vmbr1.3 inet manual auto vmbr1.4 iface vmbr1.4 inet manual auto vmbr1.5 iface vmbr1.5 inet manual auto vmbr3 iface vmbr3 inet manual bridge-ports vmbr1.3 bridge-stp off bridge-fd 0 auto vmbr4 iface vmbr4 inet manual bridge-ports vmbr1.4 bridge-stp off bridge-fd 0 auto vmbr5 iface vmbr5 inet static address 10.0.5.5/24 bridge-ports vmbr1.5 bridge-stp off bridge-fd 0 auto vmbr6 iface vmbr6 inet static address 10.0.6.5/24 bridge-ports vmbr1.6 bridge-stp off bridge-fd 0 auto vmbr1.6 iface vmbr1.6 inet manual auto vmbr2 iface vmbr2 inet static address 10.0.1.7/24 gateway 10.0.1.1 bridge-ports vmbr1.2 bridge-stp off bridge-fd 0

 

[vesalius]

So, if you edit /etc/network/interfaces directly and delete whole vmbr2 section, then change vmbr1.2 section to the below followed by a reboot, does that allow you to ping 10.0.1.7 from the switch or 10.0.1.1 gateway?

auto vmbr1.2
iface vmbr1.2 inet static
        address 10.0.1.7/24
        gateway 10.0.1.1

What is enp10s0 physically plugged into ... a managed switch? if so, how is that switch port configured? Is vlan2 tagged or untagged on that switchport?

 

[nobody0815]

1st i wanna thank you very very much for helping me.

Cant test yesterday, so today i've tested.
I made the changes, but i can't still access.
After thinking again and again. i changed the IP of the vmbr0 on eno1 to 1.0.9.5 and tadaa... everything works.
The Problem seems to be that two network Devices could be in the same network / subnet.
I' can't really explain...