Re: [systemd-devel] systemd-nspawn network ping

2016-02-29 Thread Kai Krakow
Am Mon, 29 Feb 2016 16:38:59 +0800 (CST) schrieb kennedy : > I think it will be routed, I tied ping 169.254.x.x container to > container, and it's successed. And, I created the systemd-nspawn > container after 5 minus ago, the container's host0 network auto turns > ip on

Re: [systemd-devel] systemd-nspawn network ping

2016-02-29 Thread kennedy
Hello I think it will be routed, I tied ping 169.254.x.x container to container, and it's successed. And, I created the systemd-nspawn container after 5 minus ago, the container's host0 network auto turns ip on 169.254.x.x rather than 10.0.0.x . -- Yours Sincerely Han At 2016-02-29

Re: [systemd-devel] systemd-nspawn network ping

2016-02-28 Thread kennedy
Thanks! it works! but I had a little question. In my container, I run `route -n` it show me 3 result ,they are: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 2048 00 host0

Re: [systemd-devel] systemd-nspawn network ping

2016-02-28 Thread Kai Krakow
Am Sun, 28 Feb 2016 23:41:22 +0800 (CST) schrieb kennedy : > how to ping container to container each other in systemd-nspawn ? > I've tried --network-veth option but it doesn't work enough. You need to join all host-side veth interfaces into the same bridge. Make two files