ifdown

[Denys Vlasenko]

On Friday 17 June 2011 17:54, David Henderson wrote:
> > what happens if you temporarily rename the interface to a more standard
> > name, like eth0 (use nameif to do this), and see if it's the name lan01
> > causing you problems. That would help nail it down.
> >
> > -C
> >
> 
> I don't recall any issues when using the eth0 naming scheme, but unless 
> the network adapter isn't being renamed somewhere by the ifrename binary 
> (or there's a bug in busyboxes ifdown), then I can't understand why just 
> naming the adapter lan01 would be the cause of the problem.  That's not 
> a special name used in anything that I'm aware of. :)

Yes, ethN must not be special in any way (except that eth0 is a default name
for many networking tools, but all such tools have an option to specify
iface by hand).

> Also, it further  
> complicates the situation because ifconfig doesn't have any issues bring 
> down the interface, just ifdown.  Any other thoughts?

I have some:

http://busybox.net/~vda/no_ifup.txt

-- 
vda