Your mail client did something that mine doesn't render very well, I
hope I've understood all the questions.
On Tue, 23 Apr 2013, Niels B. - IPcop List wrote:
> /sbin/insmod /lib/modules/`uname -r`/kernel/drivers/net/wireless/hostap_crypt.o
> /sbin/insmod /lib/modules/`uname -r`/kernel/drivers/net/wireless/hostap.o
> /sbin/insmod /lib/modules/`uname -r`/kernel/drivers/net/wireless/hostap_pci.o
> This loads some modules with drivers for the wlan nic (does it work with any?)
I believe that hostap_pci works only with PCI devices like the MA311G
and that there's another version of that driver for laptops which use
PCMCIA devices. I believe the other drivers work with any devices.
> /root/prism2_srec -r wlan0 /root/rf010704.hex
> I have no guess what this does... ???
In my notes you'll see somewhere that the firmware originally supplied
in the Netgear MA311G had a serious fault which prevented it from
acting as an access point. After I'd spent a few days digging into
the behaviour of the firmware and discovered what it was doing wrong I
found that everybody else on the planet who worked with these things
apparently already knew about it, and several revised firmare versions
were available for the MA311G wireless card. The file 'rf010704.hex'
is one such firmware, and 'prism2_srec' is a utility to load it into
the card. There are two main types of firmware, one type for flashing
into the non-volatile storage on the MA311G card, an oepration which
is done only once, and one type for loading into the card's RAM every
time it is switched on. As far as I know there is no functional
difference between the two types of firmware, but several versions of
each became available in the few years after the card itself first
became available. I chose the RAM version mainly because flashing the
non-volatile storage in the card carries some small risk of damaging
it, and because the machines can easily write the RAM on each boot. I
chose one of the versions of the RAM firmware which worked, and didn't
look at the others after that.
> /usr/sbin/iwpriv wlan0 host_roaming 2
> I guess this does some sort of access point searching
It tells the client that it can associate with an access point.
> /usr/local/sbin/iwconfig wlan0 mode managed
> This sets the access point mode
It tells the client to be a client which will associate with an access
point. I use IPCop machines at both ends of wireless links; at one
end IPCop is an access point and at the other IPCop is a client. Two
scripts (one for the access point IPCOp and one for the client IPCop)
are in the link that I posted. Of course you don't have to use IPCop
as a client just because you're using it as an access point, you can
use anything which can be suitably configured. I use devices such as
the WRT54GS running OpenWRT as clients with IPCop access points and
also vice versa.
The access point script contains the line ".../iwconfig mode Master"
in place of the line ".../iwconfig mode managed".
> /usr/local/sbin/iwconfig wlan0 essid "xxx"
> This sets the SSID of the access point
Yes. The one to associate with.
> /usr/local/sbin/iwconfig wlan0 key "xxxxxxxxxxxxxxxxxxxxxxxxxx"
> This sets the needed security key to get access
> (does it work with WPA-PSK and WPA2-PSK ?)
WPA-PSK and WPA2-PSK are not supported by the MA311G.
> /usr/local/sbin/iwconfig wlan0 channel X
> This sets the channel the access point works on
> /usr/local/sbin/iwconfig wlan0 ap xx:xx:xx:xx:xx:xx
> This sets the MAC address of the access point
Yes and yes.
> /sbin/ifconfig wlan0 192.168.x.x netmask 255.255.255.0 broadcast 192.168.x.x up
> This gets the wlan interface up and sets its ip address(?)
It tells the interface what IP address, netmask and broadcast to use
and to go 'up', i.e. to become active on the network.
> Does the wlan interface show up in the normal setup and web page
> from the start, or is it only visible there after I configured it,
> or is it never visible in these destinations?
> If any of the stated above is not okay, please correct me.
I don't use the IPCop Web interface but I imagine that it will be
necessary to put the right values in /var/ipcop/ethernet/settings to
get the Web interface to show what you want to be shown. It would be
best for you to experiment with that and if you find any problems let
me know here on the list. There's no point in my trying to make any
tests here because I could easily have changed things here which you
haven't changed in your IPCop, which might render the tests useless.
> But so far a big thanks to you.
> You saved my ip cop from getting blown away ;)