Re: network-manager as default? No!

[Stig Sandbeck Mathisen <ssm@debian.org>]

Timo Juhani Lindfors <timo.lindfors@iki.fi> writes:

> I'd be interested in seeing real-life ifupdown configurations that
> handle these.

Here's an example from one of my servers that handles _some_ of them.
(Addresses rewritten to rfc3330 space, and no explicit IPv6 config):

* Two bonded ethernet interfaces for redundant layer two networking to
  distinct switches. (miimon vs arp_ip_target is another discussion).

* Interfaces are added to bonding device when discovered.

* Two extra VLAN interfaces.

,----
| auto eth0 eth1 bond0 vlan101 vlan102
| 
| iface eth0 inet manual
|   bond-master bond0
|   bond-primary eth0 eth1
| 
| iface eth1 inet manual
|   bond-master bond0
|   bond-primary eth0 eth1
| 
| iface bond0 inet static
|   bond_slaves none
|   bond_mode   active-backup
|   bond_miimon 100
|   address     192.0.2.2
|   netmask     255.255.255.248
|   gateway     192.0.2.1
| 
| iface vlan101 inet static
|   vlan-raw-device bond0
|   address 192.0.2.162
|   netmask 255.255.255.248
| 
| iface vlan102 inet static
|   vlan-raw-device bond0
|   address 192.0.2.170
|   netmask 255.255.255.248
`----

My major gripe with ifupdown is the lack of CIDR in "address", but I can
live with that. :)

-- 
Stig Sandbeck Mathisen
                      ooo, shiny!