Greetings, Akshay Karle!
> I've been looking at ways to isolate the network of each unprivileged
> container that I create. I was thinking of putting each container in it's
> own vlan or creating a macvlan in private mode. I haven't had success with
> either. I also tried creating bridges for ever
Hello,
I've been looking at ways to isolate the network of each unprivileged
container that I create. I was thinking of putting each container in it's
own vlan or creating a macvlan in private mode. I haven't had success with
either. I also tried creating bridges for every container and attaching
Hi Fajar,
> > $ grep -v ^# .local/share/lxc/lxc-geschke/config
> >
> > lxc.include = /usr/local/share/lxc/config/debian.common.conf
> > lxc.include = /usr/local/share/lxc/config/debian.userns.conf
> > lxc.arch = x86_64
> >
> > lxc.include = /usr/local/share/lxc/config/debian.common.conf
> > lxc.in
Whooo. Thanks in advance, guys!
I'm not a programmer, cannot work by myself on this, but look forward
the feature.
Please keep the list posted, I'm sure many of us are interested and also
willing to test the code.
Cheers,
tamas
On 10/16/2015 07:08 PM, Serge Hallyn wrote:
Absolutely! I've n
This seems like NAT issue on the host. Did you do "iptables -t nat -I -o
lxcbrX -o phyY -j MASQUERADE"?
b.
On 14 October 2015 at 11:25, wrote:
> I use raw socket to send an ip packet and fill the source ip 5.5.5.5. I
> use tcpdump to capture it:
>
> * 15:01:29.385061 IP 5.5.5.5 > 224.0.0.18