[lxc-devel] [PATCH 3/3] allow lxc.network.pair to specify host-side name for veth interface
Daniel Lezcano
dlezcano at fr.ibm.com
Thu Nov 19 21:17:33 UTC 2009
Michael Tokarev wrote:
> Daniel Lezcano wrote:
>> Michael Tokarev wrote:
>>> Daniel Lezcano wrote:
>>>> Michael Tokarev wrote:
>>> []
>>>>> Speaking of veth - is there any other "link" for such a device except
>>>>> of a bridge? I can't think of one. And this makes whole thing to
>>>>> fly,
>>>>> I think.
>>>> The code in lxc assumes it is a bridge which covers 99% of the use
>>>> cases, but that could be bonding for example or vlan.
>>>
>>> Bonding -- you mean two or more veth pairs bound together?
>>
>> http://www.linuxfoundation.org/en/Net:Bonding
>
> Daniel, I know what is bonding. I don't understand what do
> you mean here by mentioning bonding in context of veth.
Ah, ok. Sorry, that was not a kind of RTFM, just an inadequate quick
answer :)
> The only case I can think of in this context is to bond
> two veth interfaces together as I mentioned, but it is
> nearly useless.
Yes right.
> Do you agree or disagree that the only useful application
> for "link" in this context of veth is a bridge?
I agree.
>>> As for vlan, right now it is a bridge again, you have to bridge
>>> the vlan interface and veth host side.
>>>
>>> So it looks like it is either bridge or nothing (NAT/routing).
>>>
>>> In which case current way plus my 2 patches seems to be the best route.
Ok, I reviewed them and I am ok. I will apply the first patch of the
patchset and the remaining patches after the 0.6.4 version. Do you mind
to update the man page lxc.conf in the meantime ?
Thanks
-- Daniel
More information about the lxc-devel
mailing list