Stephan Seitz <stse+deb...@fsing.rootsland.net> writes:
> The only thing that I miss from ifupdown (and I configured bonds,
> bridges and vlans) is a good IPv6 support. I can’t separately activate
> or deactivate IPv4 or IPv6 parts of an interface.
I have seen several requests for this feature, but I really don't
understand why you'd want that. If an interface is configured as a dual
stack interface, then I expect both stacks to be brought up and down
(near) simultaneously. In fact, the one thing I dislike about ifupdown
is the illusion that there can be both an "iface eth0 inet" and an
"iface eth0 inet6". There can't. It's the same interface running two
protocols. I would have preferred something like some routers do:
iface eth0
address ..
ipv6address ..
Juniper router do of course do this even better, splitting the IPv4 and
IPv6 configuration in separate "family" blocks, but still grouping all
the protocol families under the same "unit" (representing a VLAN,
physical port, or some other layer 2 interface). But that is a bit too
late to implement in ifupdown.
If you really want to handle the protocols individually, then don't
configure a dual stack interface in the first place. Use separate vlans
or ports.
Bjørn
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y63ex79x....@nemi.mork.no
