[SOLVED] Problem with specific VLAN

jdchaiken

New Member
Jan 26, 2024
2
0
1
I've been banging my head against this for 2 days now, and need additional eyes.

I have new pve install from the ISO. I've installed openvswitch as well.

ISP ->> OPNSense --> HP Procurve Switch [to be decommissioned] --> TP-Link Omada Switch Stack --> PVE.

The problem I'm having is that if I try to use VLAN 100, I get no connectivity. Any other vlan i try to use works just fine. The VLANs are defined identically in the Omada stack, and assigned to the switches. I'm using a Profile that has [Untagged 1 -- Tagged 10,20,100,107,200].

The interfaces file below works on vlan107. If I move the address and gateway lines to vlan 100, and change the IPs appropriately, I get nothing. If I change to Vlan1, or 10, it works just fine.

Firewall logs are clean, and I have temporary permit any any rules for the vlans.

What am I missing?

On the HP Side, the config is
VLAN 1
untagged 1-25,27-28 # 26 is a dedicated DMZ port

VLAN 10
tagged 1-28

VLAN 100
tagged 1-28

VLAN 107
tagged 1-28

VLAN <DMZ>
untagged 26


/etc/network/interfaces
Code:
root@pve01:/etc/network# cat 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

auto enp4s0
iface enp4s0 inet manual
        ovs_type OVSPort
        ovs_bridge vmbr0
        ovs_options tag=1 vlan_mode=native-untagged

iface enp5s0 inet manual

iface enp6s0 inet manual

iface enp7s0 inet manual

iface enp8s0 inet manual

iface eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual


auto vlan100
iface vlan100 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbr0
        ovs_options tag=100
        ovs_mtu 1500

auto vlan107
iface vlan107 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbr0
        address 172.16.107.100/24
        gateway 172.16.107.1
        ovs_options tag=107
        ovs_mtu 1500

auto vlan1
iface vlan1 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbr0
        ovs_mtu 1500

auto vmbr0
iface vmbr0 inet manual
        ovs_type OVSBridge
        ovs_ports enp4s0 vlan100 vlan1 vlan107
        ovs_mtu 9000

source /etc/network/interfaces.d/*
 
Update: Well, I'm dumb. Needed to reboot OPNsense box.
what ???

no youre not dumb you should not have to reboot the opnsense box, only apply changes in the interface section
since its a fork of pfsense one thing i noticed is that you have to apply immediately after defining a new interface.

if you do several changes and press only apply on the last one interfaces are not getting reloaded.

which makes sense -you dont wanna reset states, reload interfaces etc on any possible change, so i suspect that apply changes
only reload services related to the current config page. since this is a fundamental core function i would expect it to be same on OPNsense as it is in pfsense
 

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!