The time now is Mon 20 May 2013, 04:37
All times are UTC - 4 |
|
Page 1 of 2 [30 Posts] |
Goto page: 1, 2 Next |
| Author |
Message |
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
 Posted: Thu 20 Sep 2007, 09:12 Post subject:
 wpa and 2.17 are a no go? problem not a 2.17 issue, sorry |
|
having been away from puppy for a bit (caused by hardware and distraction issues) i return to find a few versions have gone by. when i ran into the hardware part of things i was using 2.13, and connecting to internet with a netgear wg511u pci card, the pci slot on my laptop went south, and i had to go to a usb wifi adapter. at that time i was connecting with wpa-psk security just fine.
now the rub:
not being as up to speed as i would like to be i didn't know how to get the linux driver for the usb adapter (not included in the network wizard) installed, and the ndiswrapper route didn't work ether under 2.13. i downloaded 2.17 full drivers and burned the disk in the hopes that using the driver i read about here, http://www.murga-linux.com/puppy/viewtopic.php?p=139192#139192 would help since i couldn't figure out how to get the driver from earlier in that thread to work. this brought some measure of success in that the adapter does "see" my ap now, but can't connect due to the wpa setting (and maybe other things). the other things that i mention are that the indicator light on the stick doesn't act like it does under win98se. under se the light is on most the time, only flickering off from time to time, while under 2.17 the light only flashes on for very short and rare times.
so i ask:
is wpa and 2.17 a no go (which would be a bug), or is there something wrong with my setup (which would mean i need another part of the forum)?
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
 |
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Thu 20 Sep 2007, 11:24 Post subject:
|
|
after making another attempt at getting device working under 2.13 i find that while 2.14 seems to get closer to working it also does not make the wpa-psk connection. looks like i need to look someplace for the fix to this problem.
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
tempestuous
Joined: 10 Jun 2005
Posts: 4944
Location: Australia
|
| Posted: Thu 20 Sep 2007, 11:26 Post subject:
|
|
laptopnewbee,
First, dhcpcd is broken in 2.17.1. You should get the "fixed" version here -
http://www.murga-linux.com/puppy/viewtopic.php?t=21177
And you might as well get the revised Network Wizard while you're there, even though it won't affect WPA support.
BUT DON'T USE THE WIZARD (old or new) with your Realtek-based wifi device!
The Realtek driver has only just recently been made available for Puppy 2.17, so no one has had a chance to check WPA compatibility.
I just went to the Realtek wifi forum to do some investigation now
https://sourceforge.net/forum/forum.php?forum_id=652149
and I see that the Realtek drivers are WPA compatible, but strangely, they require the "ipw" parameter with wpa_supplicant.
This is new information to me, and I can say that the Network Wizard will not accommodate this requirement. So the only option (until we modify the Wizard) is to run the wpa_supplicant commands manually.
First open /etc/wpa_supplicant.conf in geany and modify it to include your SSID and Personal Security Key.
Then run these commands
| Code: | modprobe r8187 ## (or r8180)
ifconfig wlan0 up
rm /var/run/wpa_supplicant/*
wpa_supplicant -i wlan0 -D ipw -c /etc/wpa_supplicant.conf -dd |
now open a second xterminal
| Code: | rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d wlan0 |
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Thu 20 Sep 2007, 12:10 Post subject:
|
|
| Quote: | First, dhcpcd is broken in 2.17.1. You should get the "fixed" version here -
|
i got 2.17, not 2.17.1.
| Quote: | Then run these commands
Code:
modprobe r8187 ## (or r8180)
ifconfig wlan0 up
rm /var/run/wpa_supplicant/*
wpa_supplicant -i wlan0 -D ipw -c /etc/wpa_supplicant.conf -dd
now open a second xterminal
Code:
rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d wlan0
|
where should i be when i open each of these xterms?
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
tempestuous
Joined: 10 Jun 2005
Posts: 4944
Location: Australia
|
| Posted: Thu 20 Sep 2007, 12:21 Post subject:
|
|
If you mean "where do I find the xterminal", in Puppy it's rxvt.
If you mean "what directory should I be located in", anywhere, it doesn't matter.
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Fri 21 Sep 2007, 10:31 Post subject:
|
|
tried what you said, and it didn't work. the first group of commands gave me this:
| Code: |
sh-3.00# modprobe r8187 ##
sh-3.00# ifconfig wlan0 up
sh-3.00# wpa_supplicant -i wlan0 -D ipw -c /ect/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/ect/wpa_supplicant.conf' driver 'ipw' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/ect/wpa_supplicant.conf' ->'/ect/wpa_supplicant.conf'
Reading configuration file '/ect/wpa_supplicant.conf'
Failed to read or parse configuration '/ect/wpa_supplicant.conf'.
Failed to add interface wlan0
Cancelling scan request
Cancelling authentication timeout
sh-3.00#
|
did i do something wrong?
BTW that first line would not work without the "##"
what i ended up with is the connection going up and down and not able to get an IP with the commands you gave for it
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
Everitt
Joined: 19 Dec 2006
Posts: 331
Location: Leeds,UK or Birmingham, UK
|
| Posted: Fri 21 Sep 2007, 11:08 Post subject:
|
|
| laptopnewbee wrote: | | Code: |
sh-3.00# wpa_supplicant -i wlan0 -D ipw -c /ect/wpa_supplicant.conf -dd
|
did i do something wrong? |
Looks like you have a typo. It should be: | Code: |
sh-3.00# wpa_supplicant -i wlan0 -D ipw -c /etc/wpa_supplicant.conf -dd
|
/etc/, not /ect/
I don't know if this is the only problem, but it would cause some kind of error I'd have though.
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Fri 21 Sep 2007, 11:29 Post subject:
|
|
sure would cause issues, there is no /ect directory in my puppy. 
thanks for catching it. will go test it with correct line. 
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
tempestuous
Joined: 10 Jun 2005
Posts: 4944
Location: Australia
|
| Posted: Sat 22 Sep 2007, 21:06 Post subject:
|
|
laptopnewbee, I have investigated how to modify the Network Wizard to (potentially) support WPA with Realtek wifi devices,
... but there's no point me making this change until you report your results.
Even if you are unsuccessful, I need to see error messages, particularly anything relating to "ipw".
| laptopnewbee wrote: | | where should i be when i open each of these xterms? |
Maybe you're launching a terminal from ROX? That's unnecessary. Just click on the "console" icon on the desktop.
| laptopnewbee wrote: | | Code: | | sh-3.00# modprobe r8187 ## |
BTW that first line would not work without the "##" |
That sounds crazy. "modprobe r8187" is definitely correct. If the command runs without showing anything, that means there were no errors and the module loaded successfully.
And you did add your SSID and Personal Security Key to /etc/wpa_supplicant.conf, right?
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Thu 27 Sep 2007, 09:46 Post subject:
|
|
| tempestuous wrote: |
laptopnewbee, I have investigated how to modify the Network Wizard to (potentially) support WPA with Realtek wifi devices,
... but there's no point me making this change until you report your results.
Even if you are unsuccessful, I need to see error messages, particularly anything relating to "ipw".
|
under 2.17 my lappy freezes after a short while running these lines:
| Code: |
sh-3.00# modprobe ieee80211_crypt-rtl
sh-3.00# modprobe ieee80211_crypt_wep-rtl
sh-3.00# modprobe ieee80211_crypt_tkip-rtl
sh-3.00# modprobe ieee80211_crypt_ccmp-rtl
sh-3.00# modprobe ieee80211-rtl
sh-3.00# modprobe r8187
sh-3.00# ifconfig wlan0 up
sh-3.00# rm /var/run/wpa_supplicant/*
sh-3.00# wpa_supplicant -i wlan0 -D ipw -c /etc/wpa_supplicant.conf -dd
|
i will attempt hand copying some of the output from that this coming weekend.
i do however have some ipw related output copied already:
| Code: |
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATING -> DISCONNECTED
|
and
| Code: |
No keys have been configured - skip key clearing
wpa_driver_ipw_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
|
also how do i determine if my PSK is properly entered in the .conf file? when i enter it as text:
(the actual psk different of course) i get some indication that it isn't correct
| Code: |
WPA: 4-Way Handshake failed - pre-shared key may be incorrect
|
however if i enter it through the wizard and save it i do get a 64 place numeric string, if i input it to a ascii to hex converter i get 9 hex type character pairs.
note: i have not tried running the code with ether the 64 place string, or the hex output yet.
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
tempestuous
Joined: 10 Jun 2005
Posts: 4944
Location: Australia
|
| Posted: Thu 27 Sep 2007, 11:20 Post subject:
|
|
Well done. It looks like wpa_supplicant is at least half-working, and the "ipw" parameter is definitely correct for the r8187 driver.
| laptopnewbee wrote: | | how do i determine if my PSK is properly entered in the .conf file? |
Sensible question. wpa_supplicant uses a separate utility, wpa_passphrase, to convert your passphrase to hex digits.
To be certain that there is no problem with this conversion, you can pre-convert the passphrase to hex key as such -
| Code: | | wpa_passphrase <ssid> <passphrase> |
and the resultant hex key entered into the configuration file instead of the passphrase ... but make sure you don't enclose the hex key in quotation marks, otherwise wpa_supplicant will assume you are using a passphrase.
On the subject of quotation marks, it's good to use these to enclose your SSID, especially if your SSID contains spaces or special characters.
Another suggestion: we have already learned that the r8187 driver fails to load some sub-modules that it requires, so I can think of some more modules which might be needed (WPA encryption-related). Do this before running the wpa_supplicant command -
| Code: | modprobe aes
modprobe arc4
modprobe crc32c
modprobe michael_mic |
And I forgot to mention WPA2. Puppy's /etc/wpa_supplicant.conf is only suitable for WPA. If your router is set for WPA2, please use /etc/wpa_supplicant2.conf instead (its contents are slightly different). Then the command would be -
| Code: | | wpa_supplicant -i wlan0 -D ipw -c /etc/wpa_supplicant2.conf -dd |
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Fri 28 Sep 2007, 09:27 Post subject:
|
|
when i tried entering my psk as text i was getting the incorrect passkey message, when i used the profile configuration part of the network wizard it did in fact convert it to hex correctly. i still can't connect though.
| tempestuous wrote: |
Another suggestion: we have already learned that the r8187 driver fails to load some sub-modules that it requires, so I can think of some more modules which might be needed (WPA encryption-related). Do this before running the wpa_supplicant command -
| Code: |
modprobe aes
modprobe arc4
modprobe crc32c
modprobe michael_mic
|
|
that may have changed the lines of feedback scrolling by (they seem to look different) and made them flow by smoother and faster, but it still goes on and on. (maybe that pink bunny has gotten in there someplace)
| tempestuous wrote: |
And I forgot to mention WPA2. Puppy's /etc/wpa_supplicant.conf is only suitable for WPA. If your router is set for WPA2, please use /etc/wpa_supplicant2.conf instead (its contents are slightly different). Then the command would be -
|
checked the router and it looks like it only does wpa, and not wpa2, but thanks for offering all thoughts.
i have decided to give an open ap a try this weekend just to see if puppy will actually run this device at all. since i have access to an ap that is wide open (not even a login page), an ap with a forward to a login page, and this one at work with wpa-psk, i can test all three.
if i can get connected to an open ap but am unable to make wpa work, i may just ask the boss about changing to mac address whitelist for security.
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
peterthewolf
Joined: 25 Dec 2005
Posts: 15
Location: Knaresborough UK
|
| Posted: Mon 01 Oct 2007, 17:32 Post subject:
|
|
If it is any help I found that a DLINK DWL G122 C1 usb stick using WPA and using the RT73 software did not work with 2.17 but did work with 3.00Beta2 but again does not work with 3.00Beta3
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Tue 02 Oct 2007, 14:03 Post subject:
|
|
ok.
having spent some weekend time working on this issue i found that my wg111v2 usb wifi adapter does not even connect to a wide open AP. i'm now thinking that there is an issue with the driver for it. i have tested it in both 2.13, and 2.17. the 2.13 is a full hdd install while the 2.17 is using pfix=ram with the cd.
i do wish i knew what it was that had it half working the 1 time that it did seem to be up. the light was flashing, and monitoring it with rutilt showed it getting a signal from the router and then losing it over and over again. currently i have not even been able to get rutilt to load because it seems to need an active wifi device to be willing to load.
i have downloaded a driver file for the rtl8187 from the realtek website, but i don't know how to set up puppy to compile it. i know there should be a devx_213 file needed, but don't know what directory to put it in.
i also spent time trying the device on another distro which claimed that it works "out of the box" in the hopes that i could find something to help. it didn't work any better, and without using their more complicated commands on the command line (which had me more lost than using the puppy command line) i had no hope of changing things there. i really need to put in time learning the command line for linux.
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
laptopnewbee
Joined: 19 Aug 2006
Posts: 165
|
| Posted: Thu 04 Oct 2007, 20:59 Post subject:
|
|
thanks to the help from mainly tempestuous, i am sending this post through my wg111v2 wifi device while puppy is booted! 
two things were changed along the way. sadly one of the paramiters that has been changed is the most important. i'm using a non-encrypted hotspot to connect. the other thing that was changed is that i'm running 3.00 retro.
here is how i got the device to work:
using the puppy package manager i installed rtl8187-k2.6.18.1.pet, then i opened rxvt where i input all the following code:
| Code: |
# modprobe ieee80211_crypt-rtl
# modprobe ieee80211_crypt_wep-rtl
# modprobe ieee80211_crypt_tkip-rtl
# modprobe ieee80211_crypt_ccmp-rtl
# modprobe ieee80211-rtl
# modprobe r8187
# ifconfig wlan0 up
# modprobe aes
# modprobe arc4
# modprobe crc32c
# modprobe michael_mic
|
then i just opened the network wizard (i had rutilt up to watch the effects of what i did on it's graphic interface) and a few clicks had me connected.
now i admit that i tried some shortcuts first, but this is what worked.
i don't see any reason why this should miss working with other versions of puppy and the wg111v2 device (now that i know that all those lines seem to be required) as long as the driver is compiled for the kernel. i do have both packages, and will test with 2.17 and 3.00 (the not retro version), but as there is some issue with the newer kernel and redirecting login pages that will have to wait till i visit a different hotspot.
again thanks for the help!
along the way the network wizard informed me that something could not do wpa encryption, but i believe it was talking about the driver because the hardware does wpa under 98se.
_________________
so much to learn, so late a start.
|
|
Back to top
|
|
|
|
|
Page 1 of 2 [30 Posts] |
Goto page: 1, 2 Next |
|
|
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
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index » House Training » Bugs ( Submit bugs )
