OoO En cette matinée ensoleillée du mardi 13 décembre 2011, vers 09:18, Andrew Shadura <bugzi...@tut.by> disait :
>> iproute has now support for network namespaces. For example: >> # ip netns create ns1 >> # ip link set eth1 netns ns1 >> # ip netns exec ns1 ip addr add 192.168.1.1/24 dev eth1 >> It would be great if ifupdown had support for netns as well. It would >> need to: 1. move the given interface into the appropriate namespace >> (like with "ip link") 2. configure the interface as usual (but is now >> in another namespace) 3. execute any up/down script into the >> appropriate namespace >> Either we could rely on "ip netns" to do all that or do it ourselves >> (but with compatibility with "ip netns") by issuing the appropriate >> setns() call before handling the interface. As ifupdown uses ifconfig, >> it seems easier to use the first approach. Each call could be wrapped >> in "ip netns exec" when the "netns" keyword is present. > I will look at this a bit later --- I have much work to do now; > meanwhile, check the newest experimental version out; it uses iproute2 > already, so if you provide any ideas or even patches it'd be great. I will try to provide you some patches. -- Vincent Bernat ☯ http://vincent.bernat.im Follow each decision as closely as possible with its associated action. - The Elements of Programming Style (Kernighan & Plauger)
pgpIiHnlBG5GE.pgp
Description: PGP signature
