On Sun, 2006-09-03 at 14:41 +0200, Loïc Minier wrote: > Hi, > > On Fri, Sep 01, 2006, Carlos Moffat wrote: > > Just to check, I tried madwifi-ng-{source,tools} r1587 from > > snapshot.debian.net. That one didn't work either. I had to go back to > > r1500 to be able to connect again. I hope this info helps. > > Did you bring the master interface up first? There are now two > interfaces by default which you should see in "ifconfig -a", on my > system, these are named ath1 and ath0_rename by default. You should > bring both interfaces up (via ifconfig $interface up for example) > before calling dhclient on the "VAP" interface (on my system, > it's named ath0_rename by default). > > Bye,
I have two interfaces coming up: wifi0 and ath0. Both are up, as far as I can tell. Both have the same name regardless of what version of the driver I used. A question: Is udev involved in bringing up the interface? A few months ago, I had trouble with udev renaming the interfaces [1]. Following the advice in that bug report, I did: rm -rf /etc/udev/rules.d/z45_persistent-net-generator.rules /etc/udev/rules.d/z25_persistent-net.rules which solved the problem. I wonder if that would cause trouble? Cheers, Carlos [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357025
signature.asc
Description: This is a digitally signed message part