Bug #4799
closed
Emulex OCE11102-NT & PFSENSE 2.2.2 & VLAN TAG
Added by Romain Amar about 10 years ago.
Updated about 10 years ago.
Description
Hello,
I bought a 10Gbe Emulex OCE11102-NT. The network card works fine on FreeBSD 10.1. I tried to configured some VLANs on the Same port and it's not working at all.
After opening a case at Emulex, we found that the VLAN Tag received by the network card is always 0 (we dump the vlan ID thanks to the driver). So The card send the packet untagged even it's on a tagged interface.
I use the driver in FreeBSD 10.1 (oce.ko). I use the second port as untagged traffic and everything is okay.
Can I do something to correct this behaviour ?
- Status changed from New to Rejected
- Priority changed from Urgent to Very Low
We can't call this a bug since that isn't a driver we include or have any capability to test. It appears you copied the .ko file from FreeBSD to pfSense, which is not something we recommend. Though it can work in some cases, results are mixed.
You could try to run ifconfig on the interface and use some combination of -vlanhwtag, -vlanhwfilter, and/or -vlanhwcsum to see if results may be improved.
The driver module would need to be built as a part of pfSense or included in the pfSense kernel in order for it to have a better chance of success. Feel free to open a low-priority feature request ticket with a "Future" target to include the oce driver and we can look into it eventually.
Thank you for your quick answer.
I tested this morning opnsense (the fork from pfsense and based on FreeBSD 10.1) and the vlan taggued traffic on my emulex network card works well.
I’m really surprised that it’s working with opnsense and not pfsense. I used the same driver oce.ko. If you have any idea, I’m interested.
Also available in: Atom
PDF