John Beck wrote: > * all interfaces are plumbed
On issue with that. > * all wired interfaces are brought up (per above) That also seems fine for a default. What about IPMP and standby interfaces ? > * all wireless interfaces are off (i.e., left plumbed, but not brought up) For wireless devices they could be on if the radio is on, otherwise they are off (well they have to be). Though I think what you said below might be better to avoid split personality mode. > * in the event that no wired interface can be brought up (either because > no cable is plugged in, or nothing is live at the other end), then one > wireless interface can be brought up, using some TBD preference if there > is more than one such interface available I think system with multiple wireless interfaces are probably rare. For those that do have multiple why not just bring them all online, just as you do for wired links. The interesting case for multiple wireless interfaces maybe that the reason the user has more than one is because the hardware supports different wireless systems (eg NIC1 does 'a' and NIC2 does 'b/g'). For wireless you also need to be concerned with which network you attach to - today wificonfig profiles give that but in the future NWAM needs to provide that. By wireless are we just talking about WiFi or are things like GPRS or 3G considered in here too ? What about IP over bluetooth (yeah I know we don't have a bluetooth stack yet but we might get one - no we NEED one). > For security reasons, bridging networks must be not permitted by > default. At first I read this as bridge as in ethernet bridge. I then realised that you mean being mulit homed between to different classifications of network (eg SWAN and Internet). For that reason I think I agree that if there is a wired link go with that and only bring up wireless links if there are no wired ones. For systems that actually need both wired and wireless active then the admin needs to be able to configure that policy. -- Darren J Moffat
