OPNsense Forum
Archive => 22.1 Legacy Series => Topic started by: bugvito on April 15, 2022, 02:02:43 am
-
I have been looking forward to setup a new low power box with intel interfaces rather than my current proxmox setup. My VM works fine, but I wanted to do away with the USB dongles, potentially have the ability to offload some functions, the two layers of updates, etc...
I have a small box with 4xi225-v, and while the ports worked out of the gate with a fresh install (bare metal), originally 22.1.5, now updated to 22.1.6, I am struggling with traffic on vlan interfaces.
My WAN consists of 2 vlans, while my LAN port has 4. DHCP fails on the WAN interfaces, while DHCP works for the clients on the LAN.
Traffic however does not go through on any vlan interfaces. Assigning physical ports, however, DHCP and traffic works fine.
This seems to be the same issue that is now solved for linux:
https://forum.proxmox.com/threads/unable-to-pass-vlan-to-trunk.90862/
https://forum.proxmox.com/threads/is-anyone-using-i225-v-nic-in-their-pve-setup.76708/
Is this being looked into by any chance, or does anybody know of potential workarounds? I'd rather avoid proxmox, but at this time, it appears to be the simplest workaround, defeating what I was trying to achieve.
Any help is welcomed!
-
I just got a new low powered box (J4125 with 4 I225-V NICs).
I've got vlans working without issue for my VM trunk port.
The only issue I had was with MAC spoofing on the WAN. It was flapping the interface.
Edit: I did notice a small amount of out errors showing only on the VLAN interfaces. I haven't noticed them when working on the VMs.
Edit2: I started noticing more errors later on when upgrading other devices to 2.5Gbps ports.
Looks like it is caused from the tagged vlans. If I set up as untagged the errors stop.
-
I reinstalled OPNsense bare-metal, (22.1.2); rather than import a config, I simplified the setup from scratch with only WAN(vlan 34/35) and a MGMT port. The WAN got an IP on vlan 35 and 34 as it should. I updated OPNsense to be able to install the IGMP proxy plugin, but after the upgrade to 22.1.6 without any other changes, I was no longer able to get a WAN IP on vlan 35 nor 34.
At this point I think that I'm mixing too many variables. The NICs may be fine (verified revision 3 and firmware > 1.45), the drivers (igc) could be the culprit if they changed between 22.1.2 and 22.1.6, or maybe something else is at play. My proxmox setup with some QNAP 5Gbps dongles (virtio to OPNsense) works fine with 22.1.6 and is solid so far, with the same vlan setup.
At this point I'll have to shelf this little box until i225 support is more mature, and/or when I have time to look deeper into it.
-
After looking at other topics, I ended up testing compiling the IGD driver and then tried OpnSense 22.7pre3 (disabling the compiled driver). Both options solved my problem, but having to recompile the IGD driver each time the kernel is updated is rather inconveniencing. With 22.7pre3, all has been working fine for the past hour:
https://forum.opnsense.org/index.php?topic=27299.msg137706#msg137706 (https://forum.opnsense.org/index.php?topic=27299.msg137706#msg137706)
I'll drop off of this topic as there are too many variables, and other topics that may be more focused than this one.
-
I just lost a few hours troubleshooting a failed migration to a similar 4xi225-V box (an aliexpress N5105 special).
I have multiple VLANs on my LAN interface and don't have (full) connectivity on those interfaces. Notably I did appear to have ICMP and ARP connectivity to the switch, but DHCP and WEB UI didn't work. I didn't do any network captures but it smells like IP offload is broken in the igc driver. I think you've come to the same conclusion given your driver updates seem to improve things.
Doing an interface re-config back to a non-VLAN interface worked fine.
If I get some more time I'll try the 22.7 prerelease to confirm.
-
So just to confirm the 13.1 base beta:
# opnsense-update -bkzr 22.7.b
# opnsense-shell reboot
appears to have solved my vlan issues on the i225, I assume there's some updates in the igc driver which have resolved things.
I look forward to the official 22.7 release!