On 05/10/2011 12:24 AM, Ulli Horlacher wrote:
On Mon 2011-05-09 (22:52), Daniel Lezcano wrote:
On 05/09/2011 03:10 PM, Ulli Horlacher wrote:
I have a lxc host (zoo 129.69.1.68) with a container (vmtest8 129.69.8.6).
I want all host/container communication to be internal without network
On Wed 2011-05-11 (11:29), Daniel Lezcano wrote:
If you create a bridge, attach the physical interface to it, give the
bridge the ip address you usually give to eth0, (make sure ifconfig eth0
0.0.0.0) and then give an IP address to the container on the same
network than eth0, that will
On Tue 2011-05-10 (20:08), C Anthony Risinger wrote:
I believe Daniel is saying you can pass each container two interfaces -- one
is the public and one is a local only private network for your host and
containers.
Then I have secondary addresses for each server and I have to decide
manually
Hallo,
Maybe I misunderstand your question, please tell me so.
It seems to me you want to just script this routing stuff, this is
possible in lxc on the host (use lxc.network.script.up), then all you
need is configure properly the network interface in the guest os (in
debian
I have a lxc host (zoo 129.69.1.68) with a container (vmtest8 129.69.8.6).
I want all host/container communication to be internal without network
traffic going via external router.
I know I can setup host routes like:
root@vms2:# route add -host 129.69.8.6 gw 129.69.1.68
root@vms2:# route -n
On 05/09/2011 03:10 PM, Ulli Horlacher wrote:
I have a lxc host (zoo 129.69.1.68) with a container (vmtest8 129.69.8.6).
I want all host/container communication to be internal without network
traffic going via external router.
Maybe I misunderstood but why don't you setup a bridge for the
On Mon 2011-05-09 (22:52), Daniel Lezcano wrote:
On 05/09/2011 03:10 PM, Ulli Horlacher wrote:
I have a lxc host (zoo 129.69.1.68) with a container (vmtest8 129.69.8.6).
I want all host/container communication to be internal without network
traffic going via external router.
Maybe
