On Tue, Apr 8, 2008 at 15:21:00 +0200, Bart Samwel wrote: > Hi Julien, > > Julien Cristau wrote: >> If logical interfaces are used with ifup, they're not correctly >> reenabled by 62-ifup.sh, because 55-down-interfaces.sh loses that >> information. The following patch fixed that for me: > > OK, so you're saying that logical interfaces are somehow different from > other interfaces? Just to help me understand the situation here (I don't > completely get it yet), could you tell me what's in > /etc/network/run/ifstate on your machine? And is it correct that this > patch makes it call ifup on the full string from the > /etc/network/run/ifstate file (stored in IFUP_INTERFACES), while calling > ifdown on only the part on the left side of the =? Could you explain a > bit why it should work like that? > /etc/network/run/ifstate contains: lo=lo wifi=foo lan=bar
lo, wifi and lan are the network devices. foo and bar are logical interfaces defined in /etc/network/interfaces. ifdown doesn't need the physical/logical mapping (it's already in ifstate anyway), but ifup does. In particular for the wifi interface, I have different settings for different locations, and I'd like them preserved over suspend/resume. Calling 'ifup wifi' doesn't set the proper parameters with iwconfig, so it's useless, and using the full string from ifstate makes it work. Likewise, when I want to manually configure the interface, I call 'ifup wifi=foo' or 'ifup wifi=baz' depending on where I am. Does that clear things up? Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
