Which chains are used for container to container?
On Fri, Sep 19, 2014 at 5:29 PM, Shidan wrote:
> First I spoke to soon (by saying the problem is fixed with dnat for the
> output chain), now I can now ping the containers from the host and visa
> versa but not container to container
EROUTING -d -i eth0 -j
DNAT --to-destination
iptables -t nat -D OUTPUT -d -j DNAT
--to-destination
What am I missing for container to container addressing using the external
IPs?
-- Shidan Gouran
On Fri, Sep 19, 2014 at 12:51 AM, Dave Pedu wrote:
>
> Instead of using ipt
Just figured it out a fix, I think. For containers to address each other by
both external and internal IPs, I set the DNAT rule on the OUTPUT and
PREROUTING chain, instead of just on the PREROUTING as above.
On Thu, Sep 18, 2014 at 11:03 PM, Shidan wrote:
> I think the case of having a 1 t
I think the case of having a 1 to 1 assignment of external IPs to
containers is an important use case to document somewhere.
On Thu, Sep 18, 2014 at 12:09 PM, Shidan wrote:
> Hello I have multiple external IP addresses and set up iptables so that
> each container is assigned one external
Hello I have multiple external IP addresses and set up iptables so that
each container is assigned one external IP on the lxcbr0 NATed bridge in a
1 to 1 fashion similar to this example:
root@SERVER:/var/log# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source
names I have
created and nothing happens.
What would be the proper way to do this. I am using lxc-autostart to start
the containers.
--Shidan
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
I now am trying to get containers working on my laptop with GUIs using the
same setup of putting the network interface in a bridge so that there is no
NATing or private networks on the host.
So far I have been unsuccessful and I suspect its because the interface is
a wireless one, however, with vi
n the host and 'brctl show' and
> 'ifconfig -a' output.
>
> Quoting Shidan (shi...@gmail.com):
> > Thanks for the help Stéphane and Serge.
> >
> > I've set it up so that the host device is a bridge br0, I then assigned
> > those IP addresses w
on, 2014-06-09 at 10:46 -0400, Shidan wrote:
> > > I tried it both in the individual configuration files and the main
> > > one. I actually can't get lxc-autostart to work even in a session as
> > > the user that owns the container right now and lxc-ls is not
field
wrote:
> Stéphane,
>
> On Mon, 2014-06-09 at 10:12 -0400, Stéphane Graber wrote:
> > On Mon, Jun 09, 2014 at 10:07:05AM -0400, Shidan wrote:
> > > I now am trying to get an unprivilaged container to auto-start, I put
> the
> > > following in ~/.config/lxc/def
I now am trying to get an unprivilaged container to auto-start, I put the
following in ~/.config/lxc/default.conf:
lxc.start.auto = 1
lxc.start.delay = 5
I also tried putting it in the main /etc/lxc/default.conf file. For both
cases it doesn't work and lxc-ls --fancy shows the autostart flag as
hat it will use the hosts mac address with the outside world.
On Thu, Jun 5, 2014 at 2:32 PM, Stéphane Graber wrote:
> On Thu, Jun 05, 2014 at 05:35:10PM +, Serge Hallyn wrote:
> > Quoting Shidan (shi...@gmail.com):
> > > Hello, on my host I have 4 VLAN interfaces on e
Hello, on my host I have 4 VLAN interfaces on eth0
(eth0:1, eth0:2, eth0:3, eth0:4) and each one has its own assigned public
IP address.
I want to create 4 unprivileged containers and assign a unique VLAN
interface to each, similar (I think) to a PHYS network type. How should I
go about doing this
13 matches
Mail list logo
