I have a 802.11 g/2.4 Ghz Wireless PCI Adapter model Dlink DWL-G520+

I would like to set it up in linux
What I did was use ndiswrapper and loaded the win driver, everything worked fine
Using my LifeDrive I connected to this WiFi Ad-Hoc and it worked fine

However, in my Palm LifeDrive I can specify the IP address that the device should use when it connects via WiFi

How can I specify an IP address for WiFi in Linux?

I have a few other questions I'll appreciate if I can get some answers

This computer that uses linux works as a Samba server

I would like some laptops to be able to access that Samba server (192.168.0.10) through WiFi

So I want those laptops to connect to the Samba server (which has the DWL-G520+ Wireless PCI Adapter), via WiFi
Is that possible?

Can I make this system a Wi-Fi Access Point?

I would love my Palm to be able to detect this network, connect to it, receive it's IP address via DHCPD, and then have access to the internet

ports 25, 110, 80 and 443

I would also like the laptops in my office to connect to this computer via WiFi, and they should be able to see the rest of the Samba network

You do this with the ifconfig command. Check out the man page, but the basic syntax is ifconfig device IP address. So if your wireless is wlan0, then the command to give it an IP address would be:

ifconfig wlan0 192.168.0.x

If you're not running in AdHoc mode, you'll also need to set up a gateway with the route command. This will need to point to the ip address of your router:

route add default gw xxx.xxx.xxx.xxx Where xxx is the IP address of the router.

Yes, this should be possible. You just treat it like any other Samba server. In other words, the WiFi part is irrelevant, you would set it up as you would with any other ethernet card.
Yes, you should be able to do this. There is a good tutorial here. It is aimed at Slackware users, but whatever distro you're using should work similarly.

Thanks for your suggestions, I will read the document and post any comments here

So can I setup an Access Point to allow my Palm LifeDrive and other Laptop computers to browse the internet if I am ONLY allowed to set up this device as "Ad-Hoc" mode?

(when I try to set it up as Master, I receive an error, and when I set it up as Managed, I cannot set up the ESSID)

If I'm reading this correctly (along with a couple other google hits), using ad hoc mode for this should be acceptable. I would think the critical piece here would be to set up iptables so that the access point can act as a router.

Ndiswrapper doesnt support master mode. Depending on your chipset you might get away with hostap or if your very very lucky your chipset has some kind of native support. See this http://wiki.linuxquestions.org/wiki/...n_access_point

Well I was able to set ip up as Ad-Hoc, and I was able to connect my PalmOne LifeDrive, and download email, view web pages...

So I will check this tomorrow, thanks for the advice

What excactly is Ad-Hoc, Master and Managed?

Why was I able to use my linux as a WiFi access point then?

I've read http://wiki.linuxquestions.org/wiki/...n_access_point and notice that they recommend me to use the drivers from this page:

http://wiki.linuxquestions.org/index...00&action=edit

"You have to login to edit pages.
Return to Main Page."

Which is the best driver?

I went to http://acx100.sourceforge.net
However compiling the kernel is a bit of a hassle, and I wonder if I'll be able to use
if I use those drivers

I'll appreciate suggestions

Today I was able to install with ndiswrapper, and use it as an Ad-Hoc
With a few changes to iptables, I was able to use my PalmOne LifeDrive to access the WiFI, and then I was able to browse, check my email...
And from a laptop I was able to see the samba shares, everything was working allright

I wonder, if this worked ok, why should I use this other driver?

I mean what is Managed vs Master vs Ad-Hoc?

http://www.linuxquestions.org/linux/...s_Access_Point

I read that page

That HowTo included an iptables tutorial that explained me how to add some rules to my firewall

After doing that I was able to install use my WiFi Linux server as an AccessPoint to provide
Samba and Internet (I tested ports 80, 110, 25) access to Laptops and PDAs

So does this mean that the only problem left is internet access?

Basically, Master is supposed to be used when the card acts as an access point, Managed mode is used when you have an existing access point and want to connect to it and AdHoc is used when you don't have an access point available, but want to connect to another computer. AdHoc is roughly the wireless equivalent of a cross-over cable.

As for drivers, I'm not sure what chipset that card uses. The link you give is for the ACX100 chipset, and if your card uses that, then it would likely be a better choice than ndiswrapper. If you can tell us what chipset that card has, we can tell you if that driver is appropriate.

Thanks for your help

I wasn't able to set it up as Master or Managed, only as Ad-Hoc
Today I wrote some scripts and made iptables load at startup, forwarding some nat rules

I used ndiswrapper, and today I tested Samba and Internet and they both work fine

Two laptops and one PalmOne Life drive were able to access the internet

And both laptops were able to access the Samba shares that are on the same machine as the WiFi card

Thanks everyone for yoru support, I don't see why I would try to use the other driver if Ad-Hoc and ndiswrapper work allright

Congrats on getting it to work!

I guess the answer to your last question is how comfortable you are in depending on Windows drivers. Some people believe that they shouldn't use ndiswrapper if there are functional Linux drivers available.