Thanks for the feekback, but currently I cannot ping, and I do not need routing to ping. So, I still suspect that it's a driver issue.


Bo
















> Subject: Re: [Madwifi-users] routing/driver problems
> From: proski <at> gnu.org
> To: cuibo <at> msn.com
> CC: madwifi-users <at> lists.sourceforge.net
> Date: Wed, 3 Sep 2008 21:47:49 -0400
>
> On Tue, 2008-09-02 at 19:28 -0700, CuiBo wrote:
>
> > My understanding is that this is about as bare in terms of software as
> > you can go. And under these circumstances, if the madwifi driver is
> > working correctly, then I should be able to connect wirelessly to the
> > ar5006eg/5007eg, get an IP address, and be able to ping the
> > ar5006eg/5007eg interface. In short, I have tried the new hal
> > snapshots R3835 and R3861, I get a correct address on the remote
> > wireless interface, but I can't ping the ar5006eg/5007eg interface.
>
> If you can get an IP address, then the hardware and the driver are
> working. The routing problems have nothing to do with the driver and
> this list.
>
> --
> Regards,
> Pavel Roskin

使用新一代 Windows Live Messenger 轻松交流和共享！ 立即体验！

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Madwifi-users mailing list
Madwifi-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/madwifi-users