Well I've tried this (after first steps with git) # terminal 1 root@vs-master:~# ip link add type veth
# terminal 2 root@vs-master:~# /bin/ns_exec -cmn /bin/bash about to clone with 40020000 clone: Invalid argument root@vs-master:~# echo $$ 7934 # terminal 1 root@vs-master:~# ifconfig veth0 0.0.0.0 up root@vs-master:~# brctl addif virbr0 veth0 bridge virbr0 does not exist! root@vs-master:~# brctl addif virbr1 veth0 root@vs-master:~# ip link set veth1 netns 7934 # terminal 2 root@vs-master:~# ifconfig veth1 up root@vs-master:~# dhclient veth1 There is already a pid file /var/run/dhclient.pid with pid 15307 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/veth1/1a:13:2e:39:53:2e Sending on LPF/veth1/1a:13:2e:39:53:2e Sending on Socket/fallback DHCPDISCOVER on veth1 to 255.255.255.255 port 67 interval 7 DHCPOFFER of 192.168.122.61 from 192.168.122.1 DHCPREQUEST of 192.168.122.61 on veth1 to 255.255.255.255 port 67 DHCPACK of 192.168.122.61 from 192.168.122.1 SIOCADDRT: No such process bound to 192.168.122.61 -- renewal in 1771 seconds. # terminal 1 root@vs-master:~# nc -4 -k -l 9999 # terminal 2 root@vs-master:~# while [ 1 ]; do > echo ab | nc 192.168.1.200 9999 > sleep 0.5s > done All had gone well, I had "ab" lines in terminal 1 without interruption. I've enhanced the terminal 2 script in order to check if "ab" was still comming into terminal 1 (because I've been a little lost with a big pile of ab) : # N=1; while [ 1 ]; do echo ab$N | nc 192.168.1.200 9999; ((N += 1)); sleep 0.5s; done No problem. I switched to "sleep 0.01s" and still no problem. Last script to test content length : # S=a; N=1; while [ 1 ]; do echo $N$S | nc 192.168.1.200 9999; ((N += 1)); S=${S}a; sleep 0.01s; done No problem. But actually, my VM is using br0 (with static IPs in 192.168.1.0 network) rather than virbr1 so how could I test this ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/616064 Title: Broken networking in kvm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/616064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs