Bug#743309: needs support for network namespaces

2016-01-09 Thread Marco d'Itri
On Jan 09, Guus Sliepen wrote: > However, it becomes more difficult if, for example, you have two eth0 > interfaces in different namespaces, but also configured differently. Yes, but iproute already supports bind-mounting files in /etc/, so I just need to create /etc/netns/$NAMESPACE/network/int

Bug#743309: needs support for network namespaces

2016-01-09 Thread Guus Sliepen
> Currently if I run ifupdown in a second network namespace it will try > to use the same /run/network/ifstate state file of the main instance, > so it does not actually work at all. > > I see two possible implementations: > > - support configuring the state file name in /etc/network/interfaces >

Bug#743309: needs support for network namespaces

2014-04-01 Thread Marco d'Itri
Package: ifupdown Version: 0.7.48.1 Severity: wishlist Currently if I run ifupdown in a second network namespace it will try to use the same /run/network/ifstate state file of the main instance, so it does not actually work at all. I see two possible implementations: - support configuring the