Bug #1000

lagg not working set to failover.

Added by Rick Baranowski almost 9 years ago. Updated over 8 years ago.

Operating System
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


I have been testing pfsense2.0 Beta4 11-07-2010 and the lagg interfaces with failover don't seem to be working. I am testing on vmware using em0 and em1 as lagg0 set to failover on the WAN. When I disconnet em0 taffice stops until em0 is reconnected. I have tried the same thing on the LAN lagg1 with em2 and em3 and got the same results.

On top of this when I tried to change the lagg0 to LACP from failover, the machine crashed (screen shot attached) Upon it's reboot it was giving me a interface mismatch and wanted to go throw the assignment of the interfaces again. It would not accpect the changes and kept saying interface mismatch applying the setting. Had to reload the whole OS.

crash.gif (8.66 KB) crash.gif Rick Baranowski, 11/08/2010 04:22 PM
output.txt (3.63 KB) output.txt Rick Baranowski, 11/30/2010 10:07 PM


#1 Updated by Chris Buechler almost 9 years ago

  • Project changed from pfSense Packages to pfSense

#2 Updated by Chris Buechler almost 9 years ago

  • Category set to Operating System
  • Target version set to 2.0

#3 Updated by Chris Buechler almost 9 years ago

the not coming back after the panic is another issue entirely that needs another ticket open on it, I have a config from a similar scenario. It's possible under some circumstances to completely trash the config with a panic and it's not recoverable short of removing the broken XML. I have an example, and a way to easily replicate, will post another ticket later.

#4 Updated by Ermal Luçi almost 9 years ago

Can you show your system logs?
lagg(4) is made to handle this, so only if something in pfsense is putting down the whole lagg(4)!?

Please show even an ifconfig output and arp -a

#5 Updated by Scott Ullrich over 8 years ago


Please show a ifconfig -a output and arp -a output

#6 Updated by Rick Baranowski over 8 years ago

Output attached

#7 Updated by Ermal Luçi over 8 years ago

I think its an em(4) problem since it is not reporting that it lost its link state.

#8 Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Closed

Closing since it relates to #1093.

Also available in: Atom PDF