Removal of deprecation for network_interfaces != AUTO

[Sam Leffler]

Matthew Seaman wrote:
> Sam Leffler wrote:
>> Brooks Davis wrote:
>>> On Tue, Jun 02, 2009 at 06:33:15AM +0100, Matthew Seaman wrote:
>>>  
>>>> Brooks Davis wrote:
>>>>
>>>>   
>>>>> I've never seen a valid use case, just failures to understand the
>>>>> current system.
>>>>>       
>>>> My laptop has iwi0 and bge0 interfaces.  At work, both of these obtain
>>>> addresses and default routes by DHCP, but from two completely 
>>>> different DHCP
>>>> servers.  When I'm plugged into the wired network I want the bge0 
>>>> interface to
>>>> be the default route, but iwi0 comes first in the list of 
>>>> interfaces produced
>>>> by ifconfig, so it gets configured first and sets the route.  Of 
>>>> course, when
>>>> I'm not plugged into the wired network I want iwi0 to have the 
>>>> default route,
>>>> so I can't just use dhclient.conf to disregard routing information 
>>>> on that
>>>> interface.
>>>>
>>>> All in all, setting network_interfaces="bge0 iwi0 lo0" does exactly 
>>>> what I
>>>> want with minimal effort.
>>>>     
>>>
>>> This is an interesting use case.  This is certainly the easiest way
>>> to do this in 7.  FYI, it won't work by default in 8.0 because we
>>> only run dhclient from devd so there is no ordering unless you set
>>> synchronous_dhclient="YES".  What I've been thinking here is that we
>>> should have a way to tell dhclient which interface(s) to prefer for a
>>> default route.  I've been meaning to fix that for a while, but since
>>> I've been using a cardbus wireless device, I've not needed to scratch
>>> that itch.
>>>   
>> Some people prefer to use lagg's failover handling to handle the 
>> wired-wireless switchover.
>
> How does that work if the two interfaces are in entirely different 
> networks?
> Can you trigger an arbitrary action (such as modifying the routing table)
> when a lagg interface fails over?

Sorry, didn't read your note well enough.  I don't think lagg is 
applicable to your setup.

    Sam