Bug 157182 - [lagg] lagg interface not working together with epair interface on bridge
Summary: [lagg] lagg interface not working together with epair interface on bridge
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.2-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-19 15:00 UTC by Frank Razenberg
Modified: 2018-05-30 23:49 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Razenberg 2011-05-19 15:00:24 UTC
The combination of an epair and lagg interface on a bridge seems to cause
problems. When both types of interfaces are added to a bridge, dmesg first
outputs 

 >> error setting interface capabilities on lagg0
 
 The bridge can still be used and it both interfaces are on placed on
 the bridge. It seems however that the epair and lagg do not communicate.
 
 Initially I believed this to be an epair problem and posted on freebsd-
 virtualization instead. For reference:
 http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-May/thread.html#707
 
 >> bound to 10.31.45.194
 
 ifconfig epair create
 ifconfig bridge create 
 ifconfig bridge0 addm lagg0 
 ifconfig bridge0 addm epair0a
 >> error setting interface capabilities on lagg0
 ifconfig epair0a up
 
 dhclient epair0b
 >> no DHCPOFFERS received
 
 ifconfig bridge0 destroy
 
 ifconfig lagg0 destroy
 
 dhclient em0
 >> bound 10.31.45.194
 
 ifconfig bridge0 addm em0
 ifconfig bridge0 addm epair0a
 ifconfig bridge0 up
 dhclient epair0b
 >> works
 
 # Note that simply removing lagg0 from the bridge and adding em0 to it instead
 # does NOT work. We need to use a completely new bridge.

How-To-Repeat: csup 8.2-STABLE
build/install/boot into kernel with options VIMAGE
have dhcp server on network
I had a em0 interface, not sure if it works better with others.

ifconfig lagg create laggproto lacp laggport em0
ifconfig em0 up
dhclient lagg0
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2011-05-21 23:36:21 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Fix up formatting and assign.
Comment 2 Oleksii Samorukov freebsd_committer freebsd_triage 2017-01-27 12:35:35 UTC
I just tested - bug is still present on 11-RELEASE
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:48:16 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 4 Peter Clifton 2018-05-30 23:49:53 UTC
I believe this bug might be (potentially) related to my FreeNas 11.1 box falling off the network occasionally, and not being able to renew an IP via DHCP.

(The main lagg0 interface is a memeber of bridge0, where epair devices link to jails).

I did "ifconfig bridge0 down", and was immediately able to get an IP address with dhclient, whereas before DHCP broadcast packets never appeared to reach the router.