netdev - Re: Bonding with tun-devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1400769153.5367.160.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Thu, 22 May 2014 07:32:33 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Veaceslav Falico <vfalico@...hat.com>
Cc:	Linus Gasser <list@...kas-al-nour.org>, netdev@...r.kernel.org
Subject: Re: Bonding with tun-devices

On Thu, 2014-05-22 at 15:24 +0200, Veaceslav Falico wrote:

> No worries, I figured it out why it's misbehaving. Basically now bonding
> expects every slave to have support of setting the mac address (that's in
> short), but tun device is a IP device, which doesn't support mac addresses.
> 
> A workaround would be to use tap devices, as they're more "real" and
> support mac address setting.
> 
> I'll, though, try to figure out how to make bonding work even on NOARP
> devices if it doesn't need to fiddle with OSI level 2...

Yes, it sounds some regression was added at some point.

It shouldnt be difficult to fix this.
 

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html