Issue with igb and lagg (was Re: Problem with link aggregation + sshd)

Freddie Cash fjwcash at gmail.com
Wed Sep 12 19:40:49 UTC 2012


On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro <auryn at zirakzigil.org> wrote:
> On 09/11/2012 11:34 PM, Freddie Cash wrote:
>>
>> On Sep 11, 2012 2:12 PM, "Giulio Ferro" <auryn at zirakzigil.org
>> <mailto:auryn at zirakzigil.org>> wrote:
>>  >
>>  > Well, there definitely seems to be a problem with igb and lagg.
>>  >
>>  > igb alone works as it should, but doesn't seem to work properly in
>> lagg.
>>  >
>>  > To be sure I started from scratch from a 9.0 release with nothing but:
>>  >
>>  > /etc/rc.conf
>>  > ---------------------------------------------------
>>  > ifconfig_igb0="inet ..."
>>  >
>>  > ifconfig_igb1="up"
>>  > ifconfig_igb2="up"
>>  > ifconfig_igb3="up"
>>  >
>>  > cloned_interfaces="lagg0"
>>  > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport
>> igb3 192.168.x.x/24"
>>  >
>>  > sshd_enable="YES"
>>  > ---------------------------------------------------
>>  >
>>  > This doesn't even manage to start sshd, it just hangs there at boot.
>>  >
>>  > Disabling lagg configuration everything works correctly.
>>  >
>>
>> Just curious: does it work if you split the lagg configuration from the
>> IP config:
>>
>> ifconfig_lagg0="laggproto ..."
>> ifconfig_lagg0_alias0="inet 192..."
>>
>> I've had problems in the past with cloned interfaces not working right
>> if you do everything in one ifconfig line. Never spent much time
>> debugging it, though, as the split config always worked.
>>
>
> Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9
> RELEASE)
>
> I still think the problem is with lagg and / or igb.
> Someone should look into it.

Thanks for checking.  I've used lagg(4) with igb, just not on 9.x.

You're right, it seems to be pointing to the igb(4) driver in 9.x
compared to < 9.0.

-- 
Freddie Cash
fjwcash at gmail.com


More information about the freebsd-net mailing list