On Mon, 2006-09-04 at 08:02 +1000, Kel Modderman wrote:
> On Sunday 03 September 2006 22:41, 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,
>
> Loic, maybe you have been stung by a problem similar to:
>
> http://madwifi.org/wiki/UserDocs/Distro/Debian/TroubleshootingInstallation#rename_netif
>
> I did plead with Md to have madwifi VAP's excused from the persistent-net
> udev
> rule, but my argument was not sufficient enough for him to be bothered by it
> at that time.
>
> Thanks, Kel.That sounds about right. What I did at the time was simply to remove the persistent-net rule. Would that cause an issue with the newest madwifi drivers? I'm rather confused about this, as everything seems to be the same (modules load fine, etc etc.) than with the older (r1500) drivers, except that: 1) the name went from madwifi-ng to madwifi 2) can't get an IP. Weird. Thanks, Carlos
signature.asc
Description: This is a digitally signed message part
