cvs commit: src/sys/net if_tap.c

[Roman Kurakin]

John Polstra wrote:

>On 13-Aug-2004 Roman Kurakin wrote:
>  
>
>>John Polstra wrote:
>>    
>>
>>>On 13-Aug-2004 Roman Kurakin wrote:
>>>      
>>>
>>>>John Polstra wrote:
>>>>        
>>>>
>>>>>That's pretty much correct.  IFF_UP is an administrative control
>>>>>that expresses the desired state of the interface.  The driver never
>>>>>changes IFF_UP.  IFF_RUNNING is the driver's idea of the _actual_
>>>>>
>>>>>          
>>>>>
>>>>PPP state machine can remove IFF_UP. For example if connection is not 
>>>>persistent and link
>>>>was broken for any reason.
>>>>
>>>>        
>>>>
>>>I call that a bug.
>>>
>>>      
>>>
>>This is not a bug, this is feature of protocol. Some times link should 
>>go down (or other
>>state from which it could go up only by administrator (or program) 
>>intervention).
>>    
>>
>Sorry, but I disagree.  PPP should clear IFF_RUNNING in that case,
>but should leave IFF_UP untouched.
>  
>
But in that case we need some other way to bring line up again, since we 
unable just
to ifconfig XXX up. This is possible to implement but very inconvenient.

Could you describe why is so bad that some administrative action could 
be canceled
due to protection or some other reasons by device state machine? 
Especially if users
have a choice to allow this action or not. If users have a choice this 
action could be treated
on behalf of administrator and thus like administrative action.

rik

>John
>
>
>  
>