netdev - Re: [PATCH next v1] ipvlan: assign unique dev-id for each slave device.

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20170104.133053.1438331328167852153.davem@davemloft.net>
Date:   Wed, 04 Jan 2017 13:30:53 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     mahesh@...dewar.net
Cc:     edumazet@...gle.com, netdev@...r.kernel.org, maheshb@...gle.com
Subject: Re: [PATCH next v1] ipvlan: assign unique dev-id for each slave
 device.

From: Mahesh Bandewar <mahesh@...dewar.net>
Date: Tue,  3 Jan 2017 12:47:16 -0800

> From: Mahesh Bandewar <maheshb@...gle.com>
> 
> IPvlan setup uses one mac-address (of master). The IPv6 link-local
> addresses are derived using the mac-address on the link. Lack of
> dev-ids makes these link-local addresses same for all slaves including
> that of master device. dev-ids are necessary to add differentiation
> when L2 address is shared.
> 
> Signed-off-by: Mahesh Bandewar <maheshb@...gle.com>

Applied, thanks.