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  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]
Date:	Tue, 11 Nov 2014 16:39:55 -0800
From:	Cong Wang <>
To:	Hannes Frederic Sowa <>
Cc:	Mahesh Bandewar <>,
	netdev <>,
	Eric Dumazet <>,
	Maciej Zenczykowski <>,
	Laurent Chavey <>,
	Tim Hockin <>,
	David Miller <>,
	Brandon Philips <>,
	Pavel Emelianov <>
Subject: Re: [PATCH net-next 1/1] ipvlan: Initial check-in of the IPVLAN driver.

On Tue, Nov 11, 2014 at 3:22 PM, Hannes Frederic Sowa <> wrote:
> On Di, 2014-11-11 at 15:12 -0800, Cong Wang wrote:
>> On Tue, Nov 11, 2014 at 2:29 PM, Mahesh Bandewar <> wrote:
>> > This driver is very similar to the macvlan driver except that it
>> > uses L3 on the frame to determine the logical interface while
>> > functioning as packet dispatcher. It inherits L2 of the master
>> > device hence the packets on wire will have the same L2 for all
>> > the packets originating from all virtual devices off of the same
>> > master device.
>> Why do we need this from the beginning?
>> IOW, what problem does this solve while macvlan doesn't?
> I think it is good to reduce the number of mac addresses before a NIC
> switches into promisc mode.

Sounds like over-kill to have a new device just for not worrying about mac.
Or you mean our neigh table doesn't scale?
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists