What I am about to describe may very well be outside of your experience level. If it is then I apologize. This method is very technical but it works.
I have the same wireless network card. I have not yet tried to get it working with Knoppix. I have got it working with both Suse 9.3 Pro (a hard drive installed distro) and Whax (a Live CD distro).
The WG311 v2 is not identical to the WG311 v1. Netgear must have changed some of the chips on the card because the drivers & methods that were reported to work with v1 do not work as good (if at all) with v2. This means that we must use a driver wrapper called ndiswrapper. It is a translator driver that makes a network card driver for MS Windows work on Linux.
Normally the progression of how drivers work looks like:
Linux kernel -> Linux network driver -> network card
With Ndiswrapper, it looks like:
Linux kenerl -> ndiswrapper -> Windows network driver -> network card
So now you see that it requires not 1 but 2 pieces, the ndiswrapper & the windows driver. Suse 9.x and Whax include ndiswrapper. Knoppix 3.8.x and up _may_ include ndiswrapper (i don't know). You can follow the generic ndsiwrapper installation instructions at http://ndiswrapper.sourceforge.net/m...p/Installation and there is WG311 v2 specific advice at http://ndiswrapper.sourceforge.net/m...tgear_WG311_v2.
Much of this next set of info is pulled from: http://ndiswrapper.sourceforge.net/m...ofessional_9.x. The Windows driver for the WG311 v2 card is ftp://downloads.netgear.com/files/wg...pa_1_0_1_7.zip. Extract out only the Windows XP folder and its contents since the rest of the files are not needed. Use whatever to get the drivers, I've used wget as an example. You can use a webrowser. All the command must be done as root user (use command 'su -' to become root user).This continues from the guide atOnce your in the directory containing the .inf file install the driver using ndiswrapperCode:wget ftp://downloads.netgear.com/files/wg...pa_1_0_1_7.zip unzip wg311v2_wpa_1_0_1_7.zip cd 1.0.1.7 cd Driver cd Windows\ XPYou can check the driver installed ok using...Code:ndiswrapper -i wg311v2.infLink the ndiswrapper to the wlan0 interface like so (puts an ndiswrapper file in /etc/modprobe.d/)...Code:ndiswrapper -lStart up ndiswrapper using modprobe, this will then give you a wlan0 interface in the wireless config tools (iwconfig), (Don't try a modprobe without installing the drivers first, it just won't work!)Code:ndiswrapper -mYou can check that everything loaded ok by looking at the "dmesg" outputCode:modprobe ndiswrapperYou should see something like this... (don't worry about the references to "kernel tainting", it's ok)Code:dmesg | tail -20module ndiswrapper unsupported by SUSE/Novell, tainting kernel.
ndiswrapper version 1.0@050205 loaded (preempt=no,smp=yes)
ndiswrapper: driver wg311v2 (NETGEAR, Inc.,04/04/2004,6.0.2.23) loaded
ACPI: PCI interrupt 0000:02:01.0[[A]] -> GSI 19 (level, low) -> IRQ 185
ndiswrapper: using irq 185
http://ndiswrapper.sourceforge.net/m...ure_interface:Configure interface:
Use iwconfig to configure wireless network interface. First, see if the interface is available, with:This tool is not likely to be present on your system : it is part of the package, which you should install. This will print the wireless interface e.g., wlan0. In the examples below wlan0 is used replace wlan0 with the interface reported by iwconfig above.Code:iwconfig
You can scan for the Access Point using the commandYou may have to set the network name before it can scan & find your Access Point. If the scan does not find your AP, replace ESSID with *your* ESSID network name, then try issuing the commandCode:iwlist wlan0 scanbefore the using the commandCode:iwconfig wlan0 essid ESSIDThe wireless configuration to be used should match what your Access Point AP uses. First, find out if you can see your access point (AP) withCode:iwlist wlan0 scanIf this lists your AP, you can continue. Otherwise, you may have one of two problems: Your AP doesn't broadcast SSID see the FAQ for more information or the radio of the card is off again, see the FAQ for details. If you see the AP in scan above, set the operating mode of the interface according to your setup. In most cases, it is ManagedCode:iwlist wlan0 scanIf you use encryption WEP, set the key:Code:iwconfig wlan0 mode ManagedYou can use 10 hex digits for 40-bit encryption or 26 hex digits for 128-bit encryption. You may need to use open security mode instead of restricted depending on the setup of your AP. If you want to write the key in ASCII use s: e.g. iwconfig wlan0 key restricted sassword. Set the network nameCode:iwconfig wlan0 key restricted TheWEPKeyInHexReplace ESSID with the network name used by your AP.Code:iwconfig wlan0 essid ESSID
At this point, check to make sure that ESSID is set in output of iwconfig wlan0. If you see the ESSID as you set, you can proceed to next step. If you see ESSID: off/any, then your card is not associated to AP. Check if WEP encryption is set exactly as used by AP and the AP broadcasts ESSID. See FAQ for more details. Until ESSID is set in output of iwconfig wlan0, you may not use wlan0 as network interface.
Now, setup the network parameters for the interface wlan0. This varies from distribution to distribution. Refer to your distribution's documents on how to do this. Once this is done, you can use network tools to bring up the network e.g.,
orCode:ifconfig wlan0 uporCode:dhclient wlan0Code:dhcpcd wlan0