Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 27 Aug 2014, 17:25
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Puppy as a wifi access point - OLD !!
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 3 [39 Posts]   Goto page: 1, 2, 3 Next
Author Message
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Tue 24 May 2011, 06:12    Post subject:  Puppy as a wifi access point - OLD !!  

Important Update Feb 2013:
This package updated for Slacko 5.4 here -
http://www.murga-linux.com/puppy/viewtopic.php?t=84269
All wifi drivers are now supported, not just the ath_pci and hostap drivers.

A Linux computer can be used as wifi access point ("hotspot") using the hostapd application, now attached.
Unfortunately at the time of writing Puppy is at version 5.2.x with a 2.6.33 kernel, and only these three wifi drivers are currently supported:
hostap_pci - for Prism2/3 based PCI wifi devices
hostap_cs - for Prism2/3 based PCMCIA wifi devices
ath_pci (MADWiFi) - for Atheros AR521x PCI/miniPCI/PCMCIA wifi devices

The ath_pci driver is not provided in Puppy 5.2.x, since it conflicts with the standard ath5k driver, but I have provided this driver (2 different versions) below.


INSTRUCTIONS:
i) Install the hostapd dotpet and bridge-utils dotpets from the bottom of this post.
ii) Also install one of the madwifi dotpets if you have an Atheros AR512x wifi device (PCI or PCMCIA), and reboot.

I will assume the use of a MADWiFI-compatible wifi device under Puppy 5.1/5.2.x
If you're using a hostap-compatible wifi device, alternative commands are shown in red.

First have a think about:
- what you want your Access Point to be known as - this is the SSID.
- whether you want WPA or WPA2 encryption, or no encryption.
- if encryption, what passphrase. Then you should convert your chosen ASCII passphrase into its true 64 digit hex value, using this command -
Code:
wpa_passphrase <ssid> <passphrase>

All of these parameters then need to be entered into the configuration file; /etc/hostapd.conf
I have pre-configured this file for the SSID of "Puppy_Hotspot", using WPA2 encryption, with the PSK passphrase "woof1234".
so there's no need to change anything - you can just use my settings if you wish.
But it's worth opening /etc/hostapd.conf in Geany just to see what I'm talking about. You will see that I have commented out the PSK password (woof1234) and used the full passphrase hex value, calculated as explained earlier.
Note the relevant value for WPA2 encryption: "wpa_pairwise=CCMP"
If you want to use the older WPA encryption, you will need: "wpa_pairwise=TKIP"
And if you want no encryption, you will need: "wpa=0"
For the hostap_pci/hostap_cs drivers, change "interface=ath0" to "interface=wlan0", and change "driver=madwifi" to "driver=hostap", and change "hw_mode=g" to "hw_mode=b".


Now connect your Puppy computer's ethernet interface to some form of modem/router. This will be the internet connection that you are about to share via your wifi interface.
If you have previously set up your ethernet interface with Puppy's Network Wizard, these settings must be killed. First bring down the ethernet interface -
Code:
ifconfig eth0 down

Now you must kill the dhcpcd daemon - THIS IS VERY IMPORTANT.
Go to Menu > System > System Status and Config > Pprocess process manager
and somewhere in the list of processes you should see "dhcpcd -d -l eth0"
Select it, and press "End process"
Now you need to remove the stale dhcpcd run file with this command -
Code:
rm -f /var/run/dhcpcd-eth0.*


Now change your wifi driver from its default "Station/Managed" mode to "AP/Master" mode -
Code:
ifconfig ath0 down
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmode ap

Or for the hostap_pci/hostap_cs drivers, do this instead
ifconfig wlan0 down
iwconfig wlan0 mode Master


Next you need to bridge your ethernet interface to your wifi interface, with these commands:
Code:
ifconfig eth0 0.0.0.0 up
ifconfig ath0 0.0.0.0 up
modprobe bridge
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 ath0

Or for the hostap_pci/hostap_cs drivers, change "ath0" to "wlan0".
Note that your Puppy computer is now seen on the LAN by its bridged interface: br0.
Now in theory it's optional to give the Puppy computer an IP address for its bridged interface,
but in practice I found this is essential. So do this -
Code:
rm -f /var/run/dhcpcd-br0.*
dhcpcd -t 30 -h puppypc -d br0

I found that this may take 15 seconds or so! dhcpcd seems to struggle with a "br0" interface.
Various code will run by, and eventually you should see "...forking to background".

Now you're finally ready to run the hostapd daemon
Code:
hostapd /etc/hostapd.conf -dd

The last two lines you see will be
"ath0: Setup of interface done.
l2_packet_receive - recvfrom: Network is down"
Don't worry, this means success.

Any wifi client (running on any operating system) should now be able to connect to your Puppy access point.

THE GOOD NEWS IS THAT I HAVE CREATED A SCRIPT WITH ALL THESE COMMANDS!
The script is installed at /usr/bin and it's called "Wifi-AP-launch.sh"
Obviously you can run this script from an rxvt terminal, but better still, I have created a desktop launch-script called "Wifi-AP-launch". With ROX, go to /usr/bin and drag the icon for "Wifi-AP-launch" (not Wifi-AP-launch.sh") onto the desktop. This is ready to go, but it has a generic icon. To give it a nice icon, right-click it, select File 'Wifi-AP-launch' > Set Icon...
and this will present a window. Use ROX to drag /usr/local/lib/X11/pixmaps/Wifi-AP-48.png into the window.
Done!

UPDATE: just because your Puppy computer is now a wifi Access Point, don't assume it's acting as a router ... it's not. See my later post about router/server/network considerations -
http://www.murga-linux.com/puppy/viewtopic.php?p=551738#551738
hostapd-0.7.3.pet
Description 
pet

 Download 
Filename  hostapd-0.7.3.pet 
Filesize  184.1 KB 
Downloaded  1179 Time(s) 
bridge-utils-1.5.pet
Description 
pet

 Download 
Filename  bridge-utils-1.5.pet 
Filesize  28.78 KB 
Downloaded  1320 Time(s) 

Last edited by tempestuous on Fri 08 Feb 2013, 22:51; edited 4 times in total
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Tue 24 May 2011, 06:15    Post subject:  

Here is the "standard" version of the ath_pci (MADWiFi) driver, for Atheros AR521x PCI/PCMCIA wifi devices.
This driver is only compatible with Puppy 5.1/5.2
After installing this dotpet, reboot.
This package modifies Puppy's MODULESCONFIG file so that the new ath_pci driver is then used in preference to Puppy's existing ath5k driver.
madwifi-0.9.4-r4139-k2.6.33.2.pet
Description  for Puppy 5.1/5.2
pet

 Download 
Filename  madwifi-0.9.4-r4139-k2.6.33.2.pet 
Filesize  282.53 KB 
Downloaded  837 Time(s) 
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Tue 24 May 2011, 06:17    Post subject:  

The "standard" ath_pci driver will not work with Atheros AR5007EG variants of the chipset, as found in miniPCI cards typically bundled with certain laptops, such as early ASUS Eee models.
So here is the suitable madwifi-HAL variant of the ath_pci driver, for these wifi devices.
madwifi-hal-0.10.5.6-r4126-k2.6.33.2.pet
Description  for Puppy 5.1/5.2
pet

 Download 
Filename  madwifi-hal-0.10.5.6-r4126-k2.6.33.2.pet 
Filesize  400.29 KB 
Downloaded  800 Time(s) 
Back to top
View user's profile Send private message 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Tue 24 May 2011, 10:09    Post subject:  

Upload image of eeepc taken from phone story to follow and other stuff.
image from phone comes when usb phone modem plugged in on boot. need to disconect phone and reboot before boot will complete.
interface is usb0. made a mistake during first try(somename.tar.gz) . will now disconnect and reboot and try again.
wifi-mad-installed.jpg
 Description   
 Filesize   13.11 KB
 Viewed   7279 Time(s)

wifi-mad-installed.jpg

somename.tar.gz
Description 
gz

 Download 
Filename  somename.tar.gz 
Filesize  1.19 KB 
Downloaded  617 Time(s) 
DSC00443.JPG
Description 
jpg

 Download 
Filename  DSC00443.JPG 
Filesize  398.19 KB 
Downloaded  693 Time(s) 

_________________

ASUS EeePC Flare series 1025C 4x Intel Atom N2800 @ 1.86GHz RAM 2063MB 800x600p ATA 320G
_-¤-_

<º))))><.¸¸.•´¯`•.#.•´¯`•.¸¸. ><((((º>
Back to top
View user's profile Send private message Visit poster's website 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Wed 25 May 2011, 03:36    Post subject:  

so far inconclusive.
at the moment no second wifi machine that i can access to test-see if my eeepc is broadcasting and available.

for checking:

1/ my wifi device is atheros AR5001 and I am using madwifi-hal-0.10.5.6-r4126-k2.6.33.2.pet is this correct?

2/ i must start my gprs/3g usb0 connection using pupdial before beginning to issue the sequence of commands that start with
Code:
wlanconfig ath0 destroy
 wlanconfig ath0 create wlandev wifi0 wlanmode ap
 iwconfig ath0 mode Master
?

3/if i want to have an OPEN wifi connection with no encryption how would the modifications of hostapd look? my guess is with the key info commented like so:
Quote:

##### hostapd configuration file ####

interface=ath0
#interface=wlan0
bridge=br0
driver=madwifi
#driver=hostap
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=Puppy_Hotspot
#macaddr_acl=1
#accept_mac_file=/etc/hostapd/accept
auth_algs=3
ignore_broadcast_ssid=0
eapol_key_index_workaround=0
eap_server=0
#wpa=1
#wpa_psk=cf28b5badf3966964bbd9165f2ed2950b6750d218d968660b224397758258b47
#wpa_passphrase=woof1234
#wpa_psk_file=/etc/hostapd.wpa_psk
#wpa_key_mgmt=WPA-PSK
#wpa_pairwise=CCMP

or/and not issue this command
Code:
wpa_passphrase Puppy_Hotspot woof1234



4/ does this output
Code:

 Using interface ath0 wit - recvfrom: Network is down
l2_packet_receive - recvfrom: Network is down
l2_packet_receive - recvfrom: Network is down
l2_packet_receive - recvfrom: Network is down

mean that others are looking at my wifi connection and cant or haven't connected, or mean that my gprs/3g connection is not connected to my newly created wifi connection?.

5/ is wifi0 correct for my setup in this line
Code:
# wlanconfig ath0 create wlandev wifi0 wlanmode ap


6/later i when i am sure that my wifi is active, i will want to know about setting up a introduction or even login screen for OPEN wifi.

7/perhaps wifi reference links for this info?
8/anyone else getting this going.
9/ list of some laptops with the correct wifi cards
and/or
correct wifi dongles that can be bought separately that will function.
10/ can/should i see my own Puppy wifi being broadcast in the network wizard. i can't at the moment.
networkwizard.jpg
 Description   interfaces look ok
 Filesize   62.59 KB
 Viewed   7270 Time(s)

networkwizard.jpg

br0.jpg
 Description   br0 seems ok.
 Filesize   52.51 KB
 Viewed   7263 Time(s)

br0.jpg


_________________

ASUS EeePC Flare series 1025C 4x Intel Atom N2800 @ 1.86GHz RAM 2063MB 800x600p ATA 320G
_-¤-_

<º))))><.¸¸.•´¯`•.#.•´¯`•.¸¸. ><((((º>
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Wed 25 May 2011, 06:58    Post subject:  

OK aarf, let's try to fix this.
First I must say I'm a little nervous about you using an internet connection from a mobile phone, where the interface is "usb0". I would be more confident if you were accessing the internet from an ADSL modem via ethernet.
But anyway, your situation means that in the above instructions you must change all instances of "eth0" with "usb0".
Don't run any commands which involve eth0, because your ethernet interface is unconnected, and has no involvement with your setup. You are passing network traffic between usb0 and ath0.

i) I did a bit more reading about hostapd configuration. First I suggest these changes to the hostapd.conf file:

auth_algs=1
this specifies "open authentication" which seems to be the norm for wifi access points.

wpa=2
this specifies WPA2, consistent with my other example settings.

hw_mode=g
Only for Atheros wifi devices, not for hostap users. This allows the access point to operate at G speeds instead of the default B mode, but still allows B clients to connect at the slower speed.

If you want to set up your access point with no encryption, I believe that you need this -
wpa=0

ii) When configuring the ath0 interface, apparently "iwconfig ath0 mode Master" is unnecessary.
Add this command instead -
Code:
iwconfig ath0 essid "Puppy_Hotspot"


iii) when you launch hostapd, add "-dd" so you can see results in detail, thus
Code:
hostapd /etc/hostapd.conf -dd



aarf wrote:
1/ my wifi device is atheros AR5001 and I am using madwifi-hal-0.10.5.6-r4126-k2.6.33.2.pet is this correct?

Atheros naming conventions are confusing, but yes, you have the correct driver. It's been well established that the Atheros miniPCI wifi device in the Eee 701 requires the madwifi-HAL driver.

aarf wrote:
2/ i must start my gprs/3g usb0 connection using pupdial before beginning to issue the sequence of commands that start with wlanconfig ...

Yes.

aarf wrote:
3/if i want to have an OPEN wifi connection with no encryption how would the modifications of hostapd look? my guess is with the key info commented like so: ...

Yes, comment out most of the lines that start with "wpa..." except "wpa=". This should be "wpa=0" although information about this on the web is contradictory.

aarf wrote:
or/and not issue this command
Code:
wpa_passphrase Puppy_Hotspot woof1234

Actually that command is not necessary at all. It's only necessary to convert your passphrase into full wpa_psk hex value, so you can enter this value into the configuration file. Once the configuration file has been set up, the command is no longer needed.

aarf wrote:
4/ does this output
Code:
l2_packet_receive - recvfrom: Network is down

mean that ...

I don't know. If you continue to see this message, you might need to post a question on the hostapd mailing list.

aarf wrote:
6/later i when i am sure that my wifi is active, i will want to know about setting up a introduction or even login screen for OPEN wifi.

I don't know of any application in Linux which will do that.

aarf wrote:
10/ can/should i see my own Puppy wifi being broadcast in the network wizard. i can't at the moment.

No, because your wifi interface is being used as an access point. To be able to "see" this interface from the same computer you would need to connect a second wifi device!
Back to top
View user's profile Send private message 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Thu 26 May 2011, 02:09    Post subject:  

tempestuous what is the source of the nervousness? legal, security, hardware incompatibility? "ADSL modem via ethernet" you mean like build you own prison type of domestic arrangement. sorry not me.

anyhows i am thinking that i will purchase a wifi dongle to test this on some nearby computers, also to get better range for my own personal use and to spread the puppy word over a larger immediate area when we get this sorted. so i need some recommendations and advice there so i dont get one that isn't supported somewhere along the line..attached is wifi some stuff that is available locally.
wifi.gnumeric.bz2
Description 
bz2

 Download 
Filename  wifi.gnumeric.bz2 
Filesize  3.14 KB 
Downloaded  410 Time(s) 
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Thu 26 May 2011, 02:57    Post subject:  

I'm not worried about wireless internet access, itself. In fact I use a standalone 3G wireless modem ... but mine has an ethernet interface, so my Linux boxes see it as a conventional ethernet network device.

My nervousness relates only to the nature of the "usb0" interface; I'm unfamiliar with this, and I'm unsure if it behaves like all other network interfaces?? I may worrying unnecessarily, it's just an unknown area for me.

Regarding the purchase (and setup) of a USB wifi adapter, I don't go out testing every piece of new hardware myself. I can only help people set up troublesome wifi hardware in Linux if I'm told the device ID and/or chipset.

... but before you go out and buy a new wifi adapter, I suggest you test your new hostapd hotspot with a KNOWN-GOOD wifi adapter. And this doesn't necessarily need to be a Linux machine; Windows and Mac (and Android!) wifi clients are fine to test with.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Thu 26 May 2011, 03:40    Post subject:  

On your gnumeric list of USB wifi dongles, the first two are difficult to find on Google, the most promising are the Buffalo WLI-UC-G300N and D-Link DWA-140.
Back to top
View user's profile Send private message 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Thu 26 May 2011, 10:03    Post subject:  

so i went to do a covert wifi test operation on the display models at the superstore. stuck in my trusty 8g kingston usb and rebooted, got to grub then after selecting the puppy i wanted to boot, got message: unsupported file system. it is ext2. laptop was a new lenovo. left quickly at this point as the attendant was hovering. they didn't have any suitable wifi dongles there. will go to the specialty computer store tomorrow.
edit just checked again, the puppy i was trying to boot isnt on the kingston drive. but still in the grub menu. my bad.
Back to top
View user's profile Send private message Visit poster's website 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Fri 27 May 2011, 06:59    Post subject:  

D-link DWA-140 RangeBooster N™ USB Adapter connected and functioning in lupu525 (not functioning in puppeee4.4rc2 no drivers I guess).. yet to test puppy hotspot.
d-link140.jpg
 Description   
 Filesize   39.87 KB
 Viewed   7125 Time(s)

d-link140.jpg

Back to top
View user's profile Send private message Visit poster's website 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Sun 29 May 2011, 06:12    Post subject:  

note: only thing remaining to try is dlink140 in windows on external computer with ath0 on puppy to see if hotspot is working on eeepc
.......
all below on eeepc only.
have been trying various combinations of wlan0, usb0, and ath0 and have determined that D-link dwg140 on wlan0 using "usb" driver is NOT going to be the wifi source or sender of puppyhotspot. just checking that because it isn't of one the supported drivers in tempestuous's first post
Quote:
Unfortunately at the time of writing Puppy is at version 5.2.x with a 2.6.33 kernel, and only these three wifi drivers are currently supported:
hostap_pci - for Prism2/3 based PCI wifi devices
hostap_cs - for Prism2/3 based PCMCIA wifi devices
ath_pci (MADWiFi) - for Atheros AR521x PCI/miniPCI/PCMCIA wifi devices


some output and notes mixed together (some possibly garbled and mixed up):
Quote:

.....
ath0 switched off.
usb0 not plugged in and:
wlan0 not plugged in
# wlanconfig wlan0 destroy
wlanconfig: ioctl: No such device
# wlanconfig wlan0 create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: No such device

wlan0 plugged in not connected
# wlanconfig wlan0 destroy
wlanconfig: ioctl: Network is down
# wlanconfig wlan0 create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: No such device

wlan0 plugged in connected
# wlanconfig wlan0 create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: No such device
# wlanconfig wlan0 destroy
wlanconfig: ioctl: Operation not supported
# wlanconfig wlan0 create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: No such device
#


..........
ath0 off
usb0 connected wlan0 connected

# wlanconfig wlan0 destroy
wlanconfig: ioctl: Network is down
# wlanconfig wlan0 create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: No such device
# iwconfig wlan0 mode Master
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Network is down.
# ifconfig usb0 0.0.0.0 up
# ifconfig wlan0 0.0.0.0 up
# modprobe bridge
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
# brctl addbr br0
# brctl addif br0 usb0
# brctl addif br0 wlan0
# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
ioctl(SIOCGIFINDEX): No such device
madwifi driver initialization failed.

..............
wlan0 active and connected
# wlanconfig wlan0 destroy
wlanconfig: ioctl: Operation not supported
#



..................
since dlink140 has driver "usb" which is not a supported driver for puppyhotspot???

I attempt to transfer internet connection from wlan0 to ath0
i.e. wlan0 as input, ath0 as puppyhotspot also to check if ath0 is broacasting. wlan0 connected to internet before the following terminal input.

# wlanconfig ath0 destroy
# wlanconfig ath0 create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: Input/output error
#
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Wed 01 Jun 2011, 05:16    Post subject:  

aarf wrote:
have determined that D-link dwa140 on wlan0 using "usb" driver is NOT going to be the wifi source or sender of puppyhotspot.

Correct. You must use your inbuilt wifi device with the ath_pci driver.

aarf wrote:
D-link DWA-140 RangeBooster N USB Adapter connected and functioning in lupu525
...
on wlan0 using "usb" driver

Yes, the Ralink wifi drivers have a "quirk" in that they report their driver name as "usb". If you run the "lsmod" command you should see that the actual driver in use will be either rt2800usb or rt2870sta. In fact, these two drivers will both try to claim the wifi device, so you could experiment to see if one works better than the other by going to -
Menu > System > BootManager configure bootup > Give preference to one module over another:

And there's even a third driver you can use is these two fail - the proprietary rt3572sta/rt3370sta drivers from
http://www.murga-linux.com/puppy/viewtopic.php?p=481085#481085
Exactly which one depends on your USB device ID.
Back to top
View user's profile Send private message 
aarf

Joined: 30 Aug 2007
Posts: 3620
Location: around the bend

PostPosted: Wed 01 Jun 2011, 15:28    Post subject:  

Code:
#lsmod
<snip>
usbcore   91279  7 rt2870sta,uvcvideo,usbhid,usb_storage,uhci_hcd,ehci_hcd

are you saying with different driver it may be possible to rebrand an external internet wifi signal into puppyhotspot on my eeepc? that would be cool.

running into head winds with this so it has taken a backseat for now.

other puppy users would still need the name a dongle that uses the correct drivers to be plugged into a non-wifi computer or into a laptop with the wifi enabled by an unsupported driver.

_________________

ASUS EeePC Flare series 1025C 4x Intel Atom N2800 @ 1.86GHz RAM 2063MB 800x600p ATA 320G
_-¤-_

<º))))><.¸¸.•´¯`•.#.•´¯`•.¸¸. ><((((º>
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5238
Location: Australia

PostPosted: Wed 01 Jun 2011, 21:44    Post subject:  

aarf wrote:
are you saying with different driver it may be possible to rebrand an external internet wifi signal into puppyhotspot on my eeepc?

No.
I was saying that there's a choice of three different Ralink wifi drivers which can be used with the DWA-140.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 3 [39 Posts]   Goto page: 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1421s ][ Queries: 13 (0.0077s) ][ GZIP on ]