Problems with vlan's on lagg interfaces

rcasas

I have 2 physical interfaces (em0 and em1) joined with loadbalance as lagg0

This lagg0 interface has also 4 VLAN's, vlan1, vlan2, vlan4 and vlan5

I hace also another 2 unused physical interfaces bge0 and bge1

I had this working, but last week I've upgraded to the last snapshot and pfSense starts with problems sometimes, and sometimes it reboots with a kernel panic.

The problem seems to be trying to assign vlan's before lagg interface has been started at all.

I've commented out interfaces_lagg_configure and interfaces_vlan_configure on function interfaces_configure, and added manually the configuration, and the system boots with no problems.

rcasas

I've uncommented out interfaces_lagg_configure, and only assigned manually the VLAN's, and all is working ok:

/* set up LAGG virtual interfaces */
interfaces_lagg_configure();

/* set up VLAN virtual interfaces */
//interfaces_vlan_configure();
mwexec("ifconfig vlan1 create");
mwexec("ifconfig vlan1 vlan 1 vlandev lagg0");
mwexec("ifconfig vlan2 create");
mwexec("ifconfig vlan2 vlan 2 vlandev lagg0");
mwexec("ifconfig vlan4 create");
mwexec("ifconfig vlan4 vlan 4 vlandev lagg0");
mwexec("ifconfig vlan5 create");
mwexec("ifconfig vlan5 vlan 5 vlandev lagg0");

With interfaces_vlan_configure uncommented, the times the firewall boots, it always had vlan4 and vlan5 with the right configuration, but vlan1 and vlan2 had always their parent interface unassigned.

eri--

Can you please try comment out lines 119 and 120 of interfaces.inc where it is asked to the parent interface ot set vlanhwtagg and vlanmtu and see if that fixes the problem.
It would help find the problem.

Thank you for the report.

rcasas

@ermal:

Can you please try comment out lines 119 and 120 of interfaces.inc where it is asked to the parent interface ot set vlanhwtagg and vlanmtu and see if that fixes the problem.
It would help find the problem.

Thank you for the report.

I've tried to do this, but I've had the same problem. After a rollback to my changes, the machine booted up without problems. I'm sorry but it's not about vlanmtu or vlanhwtagg.

eri--

Yes i know where the problem is.
It's in em/igb/ixgb driver. I added a patch but it was malformed so it got reverted from the builds and i have to redo it when i find time.

I will post again when the patch is in the builds to ask if everything works for you.

If you have the ability to build the driver yourself the aptch is here: https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/3eb98c77146f9f9f6f954cc95cbdcaa1163ec837

arska

Hi ermal,

This has come up as a problem also for us. The patch doesn't look very complicated, but i'm too much of a freebsd kernel noob to find the source in the correct version to rewrite/reapply the patch.
Any progress on your side ? Can you fix it or point me in the right direction to let me fix it ?

Thanks,
Aarno

eri--

This was fixed in FreeBSD 8 which should be pfSense primary os for 2.0.
For 2.0 based on 7.2 you have to merge the patch yourself since it is not in the builds.

http://svn.freebsd.org/viewvc/base/head/sys/dev/e1000/if_em.c?r1=195851&r2=195857
This is the fix that went in the tree of freebsd fro 8.0.