Hello all,
I'm trying to setup the following simple config :
* a lxc host (single network interface, single public IP1)
* a lxc container (single public IP2)
I would like to achieve the same as OpenVZ venet, where all containers
have dedicated IPs, but are sharing the MAC address of the host.
On Wed, May 21, 2014 at 8:09 PM, Marc MAURICE
wrote:
> I finally made it work with veth mode, and a bridge on the host, but it's
> frustrating.
> And I have to manually generate and allow all mac adresses (required by my
> server hoster).
I'd just comment on this one first.
What is your hoster
I finally made it work with veth mode, and a bridge on the host, but it's
frustrating.
And I have to manually generate and allow all mac adresses (required by my
server hoster).
I'd just comment on this one first.
What is your hoster like? Is it like serverloft where you can buy
additional IP
On Wed, May 21, 2014 at 9:19 PM, Marc MAURICE
wrote:
>
>>> I finally made it work with veth mode, and a bridge on the host, but it's
>>> frustrating.
>>> And I have to manually generate and allow all mac adresses (required by
>>> my
>>> server hoster).
>>
>>
>> I'd just comment on this one first.
Thanks a lot.
I tried the config and it's *almost* working.
When pinging the output from the container : packets are going out with
the good MAC.
However, nothing in return.
From tcpdumps I figured out that my parent host is not responding to
arp for the container IP.
How do I tell my host
On Wed, May 21, 2014 at 10:34 PM, Marc MAURICE
wrote:
> Thanks a lot.
> I tried the config and it's *almost* working.
>
> When pinging the output from the container : packets are going out with the
> good MAC.
>
> However, nothing in return.
> From tcpdumps I figured out that my parent host is not
On Wed, May 21, 2014 at 11:22 PM, Fajar A. Nugraha wrote:
> On Wed, May 21, 2014 at 10:34 PM, Marc MAURICE
> wrote:
>> Thanks a lot.
>> I tried the config and it's *almost* working.
>>
>> When pinging the output from the container : packets are going out with the
>> good MAC.
>>
>> However, nothi
Hi,
thanks a lot for your answers.
well ... nothing outside the server should even know about the
container's MAC address. Because if the network setup is the same as
mine, then the provider's router would route all traffic for the
container thru main server's IP. In other words, the provider's r
Quoting Marc MAURICE (marc.maur...@objectif-libre.com):
> Hi,
> thanks a lot for your answers.
> >well ... nothing outside the server should even know about the
> >container's MAC address. Because if the network setup is the same as
> >mine, then the provider's router would route all traffic for th
Because host networking is very distro-dependent, we cannot do a lot
of things in upstream lxc. However we're starting to ship things
under config/, so if we can figure out how to do this for the most
common distros, that'd be nice.
If you blog a concise explanation/tutorial of the minimal steps
On Fri, May 23, 2014 at 11:16 AM, Marc MAURICE
wrote:
>> Because host networking is very distro-dependent, we cannot do a lot
>> of things in upstream lxc. However we're starting to ship things
>> under config/, so if we can figure out how to do this for the most
>> common distros, that'd be nice
11 matches
Mail list logo
