Hi,

On Tue, Jan 03, 2012 at 04:16:26PM +0100, Jaap Keuter wrote:
> Just to reignite interest in this matter (this bug, ifupdown or  
> whatever) I submit a sample interfaces file I just experimented with.
> It configures an anonymous ethernet interface (eth0) with one vlan  
> (vlan21). This vlan is assigned an IPv4 and IPv6 address.
> It works on Squeeze, configuring the right addresses on the network  
> interface, but with annoying error messages.
Actually it does not work.

Try ifdown vlan21.
The problem here is that we actually need to split up address
configuration and interface configuration, *or* we need to put
those together.
like:

Together:

iface vlan21
     vlan_raw_device eth0
     inet static
        address 192.168.21.1
        netmask 255.255.255.0
     inet6 static
        address fd01:abcd:0:21::1
        netmask 64

Bringing iface vlan21 down or up configures the device *and*
configures all addresses on that device. I actually want a
refresh with that (so you don't have to bring down your interface
to change your ipv6).

Or split:

iface vlan21 inet static
     vlan_raw_device eth0
        address 192.168.21.1
        netmask 255.255.255.0

iface vlan21 inet6 static
        address fd01:abcd:0:21::1
        netmask 64
        vlan_raw_device eth0

ifdown --proto inet vlan21 # just no ipv4
ifdown --proto inet6 vlan21 # just no ipv6
ifdown vlan21 # remove the interface

In both cases we need changes to ifupdown.
It's time to restart thinking ifupdown. It's from an era that
aliases were normal and extra addresses on an interface were
aliases. That's not even possible with ipv6.  So we need to
change that:

First we must re-establish what the functionality of ifupdown
should be. Remember that this ifupdown design probably also finds
it way into openwrt or other systems.
Second we must describe the syntax needed in the interfaces file
to get to that functionality. Possibly without breaking any
existing systems.

So, yes, the story continues.
-- 
.signature not found



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to