Quoting Yury Vidineev (ade...@yandex.ru): > Looks like it isn't correlate. On host:
Uh, 5 and 6, 14 and 15, ... > cat /sys/class/net/veth*/iflink|sort -n > 6 > 15 > 60 > 63 > 65 > 66 > 71 > 75 > 76 > 82 > 85 > 88 > 91 > > In containers: > > for i in $(lxc-ls); do ssh $i cat /sys/class/net/eth0/iflink; done|sort -n > 5 > 14 > 59 > 62 > 70 > 81 > 84 > 87 > 90 > > > On Monday, July 01, 2013 10:26:44 AM Serge Hallyn wrote: > > You can probably correlate it using /sys/class/net/$veth/iflink, > > which should have consecutive values for link and peer. > > > > Quoting Yury Vidineev (ade...@yandex.ru): > > > Thank you for the answer! It's almost exactly what I need. But is it > > > possible to know name of interfaces without containers restart? > > > > > > On Monday, July 01, 2013 02:08:10 PM Claudio Kuenzler wrote: > > > > > Hello > > > > > Can anyone suggest me a way to determine which veth* interface belongs > > > > > to > > > > > which container? > > > > > > > > You have the possibility to add the veth interface name into the lxc > > > > config: > > > > > > > > lxc.network.veth.pair = veth0-$name > > > > > > > > > > > > Using this, you'll immediately know to which lxc container the interface > > > > belongs. > > -- > Sincerely, > Yury Vidineev ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
