-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello,
On Tue, 13 Dec 2011 09:13:36 +0100 Vincent Bernat <ber...@debian.org> wrote: > 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. Thanks for you mail! - -- WBR, Andrew -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJO5wpaAAoJEG6k0jEaLSaN6voQAJLCV7WeU72LQm0y6FtwYLJU MNvntZD6APmUK60HrKj7rHaV6I473e53W7Up0oXpgazCBIUTCQxTs+XX3IZNciqj AYyCFHuX/VO+PHYXRKOGuCPM3pegYPk5tnM3BYrtJCPSbf+2YhBpa0chJlVD3yn9 6vZ6jEe9nquNM6szukvQa8GeL8TqPiz2zn6GqClyx9iWPZVGaJ4jMfP2oaiz0XXs WQomXXxwldy0fxnwYvjfmp+XPwAAvv8CdROqr4nNuuArNrokHIRoHVPO2qCo8bKn 0z1Q3IetSzTHBb7foG+kkh6LGLfoKIl0vTJ9m/l99jRPgKm1g3yhu9Jk3CalfTcU aCj6sEWXaWJNm+6duiBAcy9jd45bti1QIG7NphU19cDXiL57Egb7IY23FB7G0jCx c2JGQROwfvR4eg2IRgBW5d91iNYjA0/bb3ML2W4DmnzX4zkQhcd9ETMF5mHp1fPR rRrITFIr5V/3Uktf+qmxXwt9AmBp5oqCwKZXsD98XmfZyERnQu+CGDG0BUnSWw5A o8obFApWfUXldKmujWWNCv01K8JcHxg1ol+R+c+j6aXFyQ4dffoY/gJdy2X+vs5B Lh9wyICsUcvgc+CE9CsLJJyAUUDeGUIhG7GUyxCGuUEs5p4JyNd7pWT0jtn5xR+o GQJticpGqaEa0eYw3KUq =d4DN -----END PGP SIGNATURE-----
