Quoting David Serrano (dserra...@gmail.com):
Hi,
At $work we're currently using KVM and setting it up so that it uses a
previously opened TAP interface: 'kvm -net tap,fd=3'. This way, we are
able to create the interface a set up a couple of ebtables filters on
it before going on. Now, we
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
