Pong wrote:
>> Another trick I realized is that if you do not want to mess >> around with chipsets and drivers, you can just spend extra >> and buy an Access Point like the Dlink DWL-2000AP+, plug >> it into your Ethernet port and voila, you're wirelessly >> connected!
> that is a really neat trick! > how much is the "overhead" cost on that AP? > and where to buy? =)
Access points should be available wherever they sell the wireless Lan adapters. In the case of the Dlink, I got a DWL-G520+ PCI adapter for around P2,700 (or was it P2,900) while I got the DWL-2000AP+ for under P5,000 at Acenet, Shoppesville Plus.
Brands other than Dlink, such as Surecom or Edimax would be a lot cheaper although the DWL-2000AP+ is supposed to support a "10x turbo mode" when communicating with another Dlink wireless device that also supports such a mode (such as the DWL-G520+).
If try use the Linux ACX111 drivers for the Dlink DWL-G520+ though (I'm not brave enough - or have the time anymore - to engage in this adventure), I'm not sure if the turbo mode is supported. But since my setup is:
DWL-G520+ on Win XP machine <--> DWL-2000AP+ on Linux machine
I should be getting that turbo speedup...
>> In fact this is the setup I'm using right now and it works, >> except ironically enough it's the driver for this newly >> bought CNET PRO200 Ethernet card I'm using to connect to the >> access point that's the source of some problems... [EMAIL PROTECTED]@[EMAIL PROTECTED]
> is that particular card problematic even without the AP attached to it?
Yep. But the problem seems to have disappeared after I upgraded to kernel 2.6.10 up from Slackware 10's default 2.4.20. Don't forget also that the PRO200 needs the 'dmfe' driver for its Davicom DM9102AF chip, not the 'tulip' one which seems to be what hotplug will usually detect by default on most distros.
When I used the 'tulip' driver on 2.4.20, ifconfig seems to work properly
but pings and everything else actually wouldn't work. I Googled around
and discovered you had to use the 'dmfe' driver, not 'tulip' so I edited /etc/hotplug/blacklist to get it to use that.
That made things work, but only temporarily, as the connection would die within a few minutes. I decided to try upgrading my kernel to 2.6.10 to see if it would fix things (and boy am I _pooped_ right now since a lot of other things also had to be changed and reconfigured) and the PRO200 seems to be finally stable and working!! (knock on silicon)
Another bloody [EMAIL PROTECTED]@!%^! Linux adventure... :-D
-- reply to: a n d y @ n e o t i t a n s . c o m http://www.neotitans.com Web and Software Development -- Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
