esh Bandewar
> Subject: Re: [PATCH net-next 9/9] ipvlan: introduce individual MAC addresses
>
> On Mon, 2017-05-08 at 15:29 +, Chiappero, Marco wrote:
> > > -Original Message-
> > > From: Jiri Benc [mailto:jb...@redhat.com]
> > > Sent: Thursday
t; .
> > Miller ; Kirsher, Jeffrey T
> > ; Duyck, Alexander H
> > ; Grandhi, Sainath
> > ; Mahesh Bandewar
> > Subject: Re: [PATCH net-next 9/9] ipvlan: introduce individual MAC
> > addresses
> >
> > On Thu, 4 May 2017 09:37:00 +, Chiappero, Marco wr
Mahesh Bandewar
> Subject: Re: [PATCH net-next 9/9] ipvlan: introduce individual MAC addresses
>
> On Thu, 4 May 2017 09:37:00 +, Chiappero, Marco wrote:
> > This looks conceptually wrong. Yes, ipvlan works at L3 (which is an
> > implementation detail anyway), but slaves
On Thu, May 4, 2017 at 9:43 AM, Jiri Benc wrote:
> On Thu, 4 May 2017 09:37:00 +, Chiappero, Marco wrote:
>> This looks conceptually wrong. Yes, ipvlan works at L3 (which is an
>> implementation detail anyway), but slaves are Ethernet interfaces and
>> should behave as much as possible as such
vger.kernel.org
>> Cc: David S . Miller ; Kirsher, Jeffrey T
>> ; Duyck, Alexander H
>> ; Grandhi, Sainath
>> ; Mahesh Bandewar
>> Subject: Re: [PATCH net-next 9/9] ipvlan: introduce individual MAC addresses
>>
>> On Tue, 2017-05-02 at 15:08 +, Chiappero,
On Thu, 4 May 2017 09:37:00 +, Chiappero, Marco wrote:
> This looks conceptually wrong. Yes, ipvlan works at L3 (which is an
> implementation detail anyway), but slaves are Ethernet interfaces and
> should behave as much as possible as such regardless, with an
> individual MAC address assigned.
exander H
> ; Grandhi, Sainath
> ; Mahesh Bandewar
> Subject: Re: [PATCH net-next 9/9] ipvlan: introduce individual MAC addresses
>
> On Tue, 2017-05-02 at 15:08 +, Chiappero, Marco wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@re
On Tue, 2017-05-02 at 15:08 +, Chiappero, Marco wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > On Thu, 2017-04-27 at 11:20 -0500, Dan Williams wrote:
> > > On Thu, 2017-04-27 at 15:51 +0100, Marco Chiappero wrote:
> > > > Currently all the slave device
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> On Thu, 2017-04-27 at 11:20 -0500, Dan Williams wrote:
> > On Thu, 2017-04-27 at 15:51 +0100, Marco Chiappero wrote:
> > > Currently all the slave devices belonging to the same port inherit
> > > their MAC address from it
Hi Marco,
[auto build test ERROR on net/master]
[also build test ERROR on v4.11-rc8]
[cannot apply to net-next/master next-20170427]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Marco-Chiapper
On Thu, 2017-04-27 at 11:20 -0500, Dan Williams wrote:
> On Thu, 2017-04-27 at 15:51 +0100, Marco Chiappero wrote:
> > Currently all the slave devices belonging to the same port inherit
> > their
> > MAC address from its master device. This patch removes this
> > limitation
> > and allows every sla
On Thu, 2017-04-27 at 15:51 +0100, Marco Chiappero wrote:
> Currently all the slave devices belonging to the same port inherit
> their
> MAC address from its master device. This patch removes this
> limitation
> and allows every slave device to obtain a unique MAC address, by
> default
> randomly g
Currently all the slave devices belonging to the same port inherit their
MAC address from its master device. This patch removes this limitation
and allows every slave device to obtain a unique MAC address, by default
randomly generated at creation time.
Moreover it is now possible to correctly mod
13 matches
Mail list logo
