Notifications

Clear all

Linux VLAN issue using the YT as guide

Proxmox help

Last Post by Dan Ken 3 days ago

6 Posts

2 Users

0 Reactions

29 Views

RSS

Posts: 4

Dan Ken

Topic starter

Dec 22, 2024 8:00 pm

(@danken)

Active Member

Joined: 4 days ago

I'm just following the "Proxmox VLAN Configuration" YouTube as a guide, and naturally I hit a wall.

In the pre-changes to "/etc/network/interfaces", these were the lines:

auto lo
iface lo inet loopback

iface enp60s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.99/24
        gateway 192.168.1.1
        bridge-ports enp60s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

iface wlo1 inet manual

source /etc/network/interfaces.d/*

At post-changed by switching 99 to 98:

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.98
iface vmbr0.98 inet static
address 192.168.1.98/24
gateway 192.168.1.1

source /etc/network/interfaces.d/*

I got this error after "ifreload -a":

error: netlink: eno1: cannot enslave link eno1 to vmbr0: operation failed with 'No such device' (19)
error: vmbro: bridge port eno1 does not exist
warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)

The video made no attempt to mentioned the `eno` parts, so I got this part wrong.

I read the thread "Can't get vlans to work in Proxmox" and "Why are these interfaces named this way?", so I got some rough ideas of what is going on, like not creating eno1 & 2. Even by editing out eno1, and back to enp60s0:

iface enp60s0 inet manual

bridge-ports enp60s0

I still didn't get Linux VLAN to work. What am I missing here?

5 Replies

Posts: 409

Brandon Lee

Admin

Dec 22, 2024 8:23 pm

(@brandon-lee)

Member

Joined: 14 years ago

@danken Hello and welcome to the forums! It looks like you may have some issues with the actual names of the interfaces as they exist on the system. One of the first things I would do is look and see what the actual interface names are:

ip link show

So, if I am following what your original config looked like your correct config might look something like this:

auto lo
iface lo inet loopback

iface enp60s0 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports enp60s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.98
iface vmbr0.98 inet static
        address 192.168.1.98/24
        gateway 192.168.1.1

source /etc/network/interfaces.d/*

Then you can reload your interfaces

ifreload -a

Let me know if this helps?

Thanks Dan!

Brandon

4 Replies

Dan Ken

(@danken)

Joined: 4 days ago

Active Member

Posts: 4

Dec 22, 2024 10:37 pm

Reply to

Brandon Lee

@brandon-lee

Hello and welcome to the forums!

Thank you.

One of the first things I would do is look and see what the actual interface names are:
ip link show

This was the result:

Io, status unknown

emp60s0, status down

wl01, status down

vmbr0, status unknown

vmbr0.98@vmbr0, status up

So, if I am following what your original config looked like your correct config might look something like this:

auto lo
iface lo inet loopback

iface enp60s0 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports enp60s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.98
iface vmbr0.98 inet static
        address 192.168.1.98/24
        gateway 192.168.1.1

source /etc/network/interfaces.d/*

Then you can reload your interfaces

ifreload -a

Pretty much, because I was just following the YT (and a comment). I did experimented, like with the 2nd code I posted earlier on eno1; and updated the "/etc/hosts" with the new 98 IP Address.

Btw, I cannot access the Proxmox Web GUI anymore (cannot be ping), after the failed Linux VLAN changes. So, now I need to input the cmds directly into the Proxmox machine's terminal.

Brandon Lee

Admin

(@brandon-lee)

Joined: 14 years ago

Member

Posts: 409

Dec 23, 2024 8:58 am

Reply to

Dan Ken

@danken Just following along. So you changed to the suggested config and still can't access, but didn't get errors on the ifreload -a command?

Also, have you made sure you have your switch tagged upstream where your proxmox host is uplinked? Are you trying to access the server from the same VLAN or different VLAN? To simplify things and rule out routing, I always start testing on the same VLAN just to establish you have connectivity.

Usually when you can't access IPs associated with VLANs, this usually comes down to a tagging problem.

Dan Ken

(@danken)

Joined: 4 days ago

Active Member

Posts: 4

Dec 23, 2024 9:52 pm

Reply to

Brandon Lee

@brandon-lee

Just following along. So you changed to the suggested config and still can't access, but didn't get errors on the ifreload -a command?

That's right. No access, but no error too.

The suggested config with "ip link show" result:

Io, status unknown

emp60s0, status up

wl01, status down

vmbr0, status up

vmbr0.98@vmbr0, status up

Also, have you made sure you have your switch tagged upstream where your proxmox host is uplinked?

The switch is tagged correctly (I think).

Untagged Port 1 is between my router & switch.

Tagged port 5 is between the proxmox host & switch.

Are you trying to access the server from the same VLAN or different VLAN? To simplify things and rule out routing, I always start testing on the same VLAN just to establish you have connectivity.

A different vlan, 20. Not using the native.

These were pretty much the same setting during the 'pre-changes'.

Btw, does this old line matter:

iface wlo1 inet manual

Dan Ken

(@danken)

Joined: 4 days ago

Active Member

Posts: 4

Dec 23, 2024 11:11 pm

Reply to

Brandon Lee

@brandon-lee

In the 'post-change', my router still cannot find the proxmox server. And the Proxmox server cannot ping to anything. The new url is correct with https

 https://192.168.1.98:8006

I tried untagged port 5, but no result.

I manually added the server's mac address vmbr0 & the new IP Address into my router's reservation. There is no other device using the 98 address.

I checked if I had misspell anything, and the only typo was 'wl01' (zero) when it should be 'wlo1' (lowercase O-letter).

However, no result in any of the above methods. How could this proxmox's Linux VLAN suddenly cause the server to be hidden?

Did the router's tagged VLAN 20 somehow conflicts with the Proxmox's Linux VLAN's vmbr0.98? Does the ID # have to be the same?

Forum Jump:

Previous Topic

Currently viewing this topic 1 guest.

Linux VLAN issue using the YT as guide

Like this:

Get the latest posts in your Inbox! 🔔