[Lxc-users] What's the setup for macvlan on the host to talk to containers?

[Andy Phillips]

Hi
  You can call it what you like. One guide I found used # as in eth0#1 but I 
didn't like that. I just use : because its familiar to people and its a 
close conceptual match. I've used 'fred' and etha in testing.
   On the versions thing you may find that stock ubuntu 10.04 allows you to 
create macvlans but will not display them properly or support the 'mode' 
attribute. Best to update to the version that matches your kernel.
   Andy


----- Original Message -----
From: Whit Blauvelt <whit at transpect.com>
To: atp <Andrew.Phillips at lmax.com>
Cc: Gordon Henderson <gordon at drogon.net>; lxc-users at lists.sourceforge.net 
<lxc-users at lists.sourceforge.net>
Sent: Tue Jul 06 19:07:07 2010
Subject: Re: [Lxc-users] What's the setup for macvlan on the host to talk to 
containers?

On Tue, Jul 06, 2010 at 06:36:48PM +0100, atp wrote:
> You'll need a recent version of iproute2.
>
> I have iproute2-2.6.34.tar.bz2

Think I need to update that. Ubuntu sadly doesn't reveal the real version,
just "iproute2-ss091226", but since "ip link help" shows no mode option,
that's likely why my first attempt wasn't going anywhere.

>   ip link add link bond200 name bond200:0 address 00:aa:bb:cc:dd:ee \
>   type macvlan mode bridge

Is there a necessity to the :0 naming convention (as with eth0:0 before
iproute2 gave us direct multi-IP assignments)?

>   In terms of the conceptual model, think of it as the same as an ip
> alias, or secondary ip address, but at the mac level.

Thanks much,
Whit



The information in this e-mail and any attachment is confidential and is intended only for the named recipient(s). The e-mail may not be disclosed or used by any person other than the addressee, nor may it be copied in any way. If you are not a named recipient please notify the sender immediately and delete any copies of this message. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any view or opinions presented are solely those of the author and do not necessarily represent those of the company.