Network wizard Beta version for testers
Actually the current version of the wizard should work with WPA-PSK/TKIP.shockwave wrote:Ok i tried it in wpa tsk and still nothing. Any ideas. Also if it doesn't now, will this eventually work with psk?
So yes, it should work for yours because it is the only one supported.
It could be that your addapter does not work with any of the WPA drivers included.
Hopefully Tempestuous will have an answer.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
shockwave, I have no idea what you mean by "regular wpa"? Are you getting confused with WEP?
WPA-PSK/TKIP is the most basic and common form of WPA, and it definitely works with wpa_supplicant in Puppy.
There is also WPA-PSK/AES which hopefully SHOULD (?) work by adding "CCMP" to the configuration file as explained earlier in this thread - http://www.murga-linux.com/puppy/viewto ... 5152#95152
The best way to troubleshoot WPA with your device is to take the Wizard out of the equation and run all of the setup commands manually as I mentioned earlier. Once you have things working this way, you're ready to try the Wizard again.
WPA-PSK/TKIP is the most basic and common form of WPA, and it definitely works with wpa_supplicant in Puppy.
There is also WPA-PSK/AES which hopefully SHOULD (?) work by adding "CCMP" to the configuration file as explained earlier in this thread - http://www.murga-linux.com/puppy/viewto ... 5152#95152
The best way to troubleshoot WPA with your device is to take the Wizard out of the equation and run all of the setup commands manually as I mentioned earlier. Once you have things working this way, you're ready to try the Wizard again.
Rarsa, I don't think I put that very well! All I was really meaning was that it is not important to get WPA working on my set-up if the wizard works for other people.rarsa wrote:And all the users that will need the functionallity really appreciate your testing (even if they don't realize they do)barriew wrote:Just to remind you that I don't particularly need this facility - I was just trying to help Rarsa by testing.
I myself don't even need the wizard
Tempetuous
An interesting aside - I tried WEP via the wizard which was OK,but could only get 11Mb not 54, and I noticed on RutilT that the link was disconnecting and reconnecting every few seconds. The laptop was a few centimetres away from the router and works fine on an open connection.
Barrie
I took your intention as you meant it. That's why I thanked you in the name of the users that really need the wizard.barriew wrote:Rarsa, I don't think I put that very well! All I was really meaning was that it is not important to get WPA working on my set-up if the wizard works for other people.
So, in working with you to solve the problem you report you are helping others and that's how I see it.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
Been out for a bit, see there is new progress. I will respond to your comments a couple pages back.
http://www.usr.com/support/5410/54xx-ug/four.html
Thus when you enter a channel number the frequency field should be changed by the wizard, and vice versa (in fact that table looks like it is not WPA-specific, but applies also to WEP and to no encryption). That page may give you other ideas of things to put in the wizard too.
Whatever you do, it should be consistent. Either all chipset names, or all driver names. And if you do that, you should label the list "chipset" or "driver" as appropriate. IIRC part of my problem was that everything in the wizard referred to drivers or modules, but the list was chipsets. Another difficulty I had was that you have things like "pci:" in the front of each name, and the only atheros thing there had pci: in front of it. Well my device is a pcmcia card, so I thought that pci thing would not apply. It did work though when I finally tried it. What is that preamble thing for anyway? Maybe, if you have a pci-type driver that works as well for pcmcia, the thing to do would be to have two separate table entries, pointing to the same thing.
I guess my preference would be for chipset names, with a flyover containing the driver name.
FYI here (starting about in the middle of the page) are the common different ways the .conf file can be set up using WPA:
http://www.freebsd.org/doc/en_US.ISO885 ... eless.html
(It may be enough to implement only WPA-PSK in the wizard though.)
And here's another look at the parameters:
http://student.cosy.sbg.ac.at/~shuber/f ... icant.conf
One thing I was curious about. I wanted to look at what the output of the wizard was; i.e., I wanted to see how the boot process called the scripts, where the wpa_supplicant.conf file was, etc. Can you tell me that, and possibly even put that information at the end of the wizard, just in case a file needs to be tweaked or something like that?
Yes, I agree with breaking it down between basic and advanced. Most will be served by the basic screen.Before it always showed all fields and that totally confused many new users, so I take your experience as a nod that hidding these fields is the right thing to do.
Look at this page, which has a setup program for WPA:I didn't know! can you tell me more?In the advanced screen, you can enter "channel" or "frequency" IIRC. Of course those two are connected
http://www.usr.com/support/5410/54xx-ug/four.html
Thus when you enter a channel number the frequency field should be changed by the wizard, and vice versa (in fact that table looks like it is not WPA-specific, but applies also to WEP and to no encryption). That page may give you other ideas of things to put in the wizard too.
Hmmm, that's a tough question. I assume by "human" you are referring to the chipset name. This is all difficult for users because they know what device they bought, but we require them (for good reasons) to supply at least a chipset name, and a further difficulty would be requiring even another step for them, the driver name. It would require a fair amount of research to chase all that down.I debated for a moment with my self, Should I use "human" labels or the actual driver name "madwifi", "hostap", "wext".
Whatever you do, it should be consistent. Either all chipset names, or all driver names. And if you do that, you should label the list "chipset" or "driver" as appropriate. IIRC part of my problem was that everything in the wizard referred to drivers or modules, but the list was chipsets. Another difficulty I had was that you have things like "pci:" in the front of each name, and the only atheros thing there had pci: in front of it. Well my device is a pcmcia card, so I thought that pci thing would not apply. It did work though when I finally tried it. What is that preamble thing for anyway? Maybe, if you have a pci-type driver that works as well for pcmcia, the thing to do would be to have two separate table entries, pointing to the same thing.
I guess my preference would be for chipset names, with a flyover containing the driver name.
FYI here (starting about in the middle of the page) are the common different ways the .conf file can be set up using WPA:
http://www.freebsd.org/doc/en_US.ISO885 ... eless.html
(It may be enough to implement only WPA-PSK in the wizard though.)
And here's another look at the parameters:
http://student.cosy.sbg.ac.at/~shuber/f ... icant.conf
One thing I was curious about. I wanted to look at what the output of the wizard was; i.e., I wanted to see how the boot process called the scripts, where the wpa_supplicant.conf file was, etc. Can you tell me that, and possibly even put that information at the end of the wizard, just in case a file needs to be tweaked or something like that?
I booted in 2.13 and tried your latest -5 wizard.
Looks like a step backward! First, it now seems to assume I'm going to use WPA - never asks me any choice between no encryption, WEP or WPA like the -4 version did. I need to be able to run unencrypted, of course. And there is no basic/advanced page, which is a shame. I liked that basic page, nice and basic.
It wouldn't connect either. But when I tried the -4 version again, it didn't either. Or do I have to reboot to connect? Seems I didn't have to last time, IIRC. In fact I had a question about installing - can I install one on top of the other? There seemed no way to uninstall...
Looks like a step backward! First, it now seems to assume I'm going to use WPA - never asks me any choice between no encryption, WEP or WPA like the -4 version did. I need to be able to run unencrypted, of course. And there is no basic/advanced page, which is a shame. I liked that basic page, nice and basic.
It wouldn't connect either. But when I tried the -4 version again, it didn't either. Or do I have to reboot to connect? Seems I didn't have to last time, IIRC. In fact I had a question about installing - can I install one on top of the other? There seemed no way to uninstall...
Ok I tried putting doing all the modprobes, but still didn't work. I am using aes encryption. I am also noticing that everytime I restart the computer my settings aren't being saved. I have it set to save to usb, but each time i have to do the
modprobe firmware_class
modprobe ieee80211
modprobe ieee80211softmac
modprobe bcm43xx
to get my card to work
when i ran net-setup.sh i got this
/etc/networkusermodules:no such file or directory
killall: wpa_supplicant: No process killed
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
cat: /tmp/wpa_status.txt: no such file or directory
Thanks for all the help. I really appreciate it. I appologize for having no clue..I have only been using linux for a very short while.
modprobe firmware_class
modprobe ieee80211
modprobe ieee80211softmac
modprobe bcm43xx
to get my card to work
when i ran net-setup.sh i got this
/etc/networkusermodules:no such file or directory
killall: wpa_supplicant: No process killed
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
cat: /tmp/wpa_status.txt: no such file or directory
Thanks for all the help. I really appreciate it. I appologize for having no clue..I have only been using linux for a very short while.
Well, it refers to drivers or modules when I am talking about drivers modules.PaulBx1 wrote:IIRC part of my problem was that everything in the wizard referred to drivers or modules
The WPA drivers are something different, that's why I qualified it 'WPA driver". This is also a though one and one I went around thinking how to name that field.
Ejem, ejem... that is not my list. I do not provide the drivers. I provide the wizard. Barry provides the drivers and sets the labels in that list.PaulBx1 wrote:Another difficulty I had was that you have things like "pci:" in the front of each name
Ejem ejem... I guess that I haven't been clear enough on the limitations of the UI toolset.I guess my preference would be for chipset names, with a flyover containing the driver name.
Yes, I know that WPA does many things. But I'm implementing and testing one at a time.FYI here (starting about in the middle of the page) are the common different ways the .conf file can be set up using WPA
Are you pulling my leg? I gave you that information in this postOne thing I was curious about. I wanted to look at what the output of the wizard was
http://www.murga-linux.com/puppy/viewto ... 5332#95332
Thank you for taking the time to comment on the wizard. It is clear that when I have to explain something in a post, the wizard is not doing the best job explaining it through the UI.
The new interface will be an order of magnitude (at least) clearer.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
Shockwave,shockwave wrote:I am using aes encryption.
Sorry for your trouble, but as the title of this thread says, this first release of the wizard with WPA, only supports WPA-PSK/TKIP.
I have NOT implemented AES yet.
I will do it, once I know that I've cleaned up the bugs with TKIP, but I cannot clean the bugs and issues with TKIP if people don't test TKIP.
If you could test with TKIP it would be great. If not maybe you can help once AES is implemented.
Thank you for your help.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
All I can say is that something went wrong with your installation.PaulBx1 wrote:I booted in 2.13 and tried your latest -5 wizard.
Looks like a step backward!
My guess? you uninstalled instead and went back to the 2.13 version.
You can try 2.14-6, minor changes:
- fixed some wording.
- Kill wpa_supplicant before trying to reconfigure.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
Version 2.14-6 uploaded
Here are the changes
- Show more information on the list of scanned networks: Now the fly over tooltip shows the signal strenght for each network.
- Fixed some wording replacing "Ethernet" with "Network" and the word "above" with the word "below" refering to the location of the interfaces.
- Kill wpa_supplicant before trying to reconfigure an interface. (Before if you configured something WPA and then tried to configure it Open or WEP, it would fail because WPA had taken over.
Here are the changes
- Show more information on the list of scanned networks: Now the fly over tooltip shows the signal strenght for each network.
- Fixed some wording replacing "Ethernet" with "Network" and the word "above" with the word "below" refering to the location of the interfaces.
- Kill wpa_supplicant before trying to reconfigure an interface. (Before if you configured something WPA and then tried to configure it Open or WEP, it would fail because WPA had taken over.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
rarsa-thanks for the reply. I just wanted to make sure. I siwtched my connection to wpa-psk with tkip encryption. it's still not working. I am getting the same thing as before. I believe I may be missing some files. This is the message i get
/etc/networkusermodules:no such file or directory
killall: wpa_supplicant: No process killed
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
cat: /tmp/wpa_status.txt: no such file or directory
How can I create these files if I am missing them. I have my info saving to the USB, but i have to reinstall the drivers to the card each time I boot doing the following.
modprobe firmware_class
modprobe ieee80211
modprobe ieee80211softmac
modprobe bcm43xx
thanks for all the help. I am very impressed with your program and will try to keep helping however I can.
/etc/networkusermodules:no such file or directory
killall: wpa_supplicant: No process killed
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
failed to connect to wpa_supplicant -wpa_ctr_open: No such file or directory
cat: /tmp/wpa_status.txt: no such file or directory
How can I create these files if I am missing them. I have my info saving to the USB, but i have to reinstall the drivers to the card each time I boot doing the following.
modprobe firmware_class
modprobe ieee80211
modprobe ieee80211softmac
modprobe bcm43xx
thanks for all the help. I am very impressed with your program and will try to keep helping however I can.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Tried -5 wizard. Connected first time.
Saved configurations but will not reconnect automatically on reboot. I have to restart the wizard and select the saved profile to connect.
I am booting from the CD with the session saved on the hard drive.
Using 2.13
Thinkpad 600
128M ram
Belkin 54g ver5
Atheros (madwifi)
Saved configurations but will not reconnect automatically on reboot. I have to restart the wizard and select the saved profile to connect.
I am booting from the CD with the session saved on the hard drive.
Using 2.13
Thinkpad 600
128M ram
Belkin 54g ver5
Atheros (madwifi)
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I think the new version(s) overwrite any old ones.shockwave wrote:in order to try the new version do I need to first remove the prior ones? If so what is the code to do that? thanks
shockwave, after loading your 4 driver modules, I suggest you then load these cryptographic modules -
modprobe michael_mic
modprobe aes
modprobe arc4
modprobe libcrc32c
modprobe crc32c
modprobe ieee80211_crypt
modprobe ieee80211_crypt_ccmp
modprobe ieee80211_crypt_tkip
These modules SHOULD load automatically, but by loading them manually we ensure that they can successfully be found in Puppy's zdrv file, which has otherwise been a problem in the past.
Now you're in a good position to run the Wizard.
temptuous,
After loading all of that I am still getting the same error
cat: /etc/networkusermodules: no such file or directory
cat: /etc/networkusermodules: no such file or directory
killall:wpa_supplicant: no process killed
failed to connect to wpa_supplicant - wpa_ctrl_open: no such file or directory (this one is repeated several times)
After loading all of that I am still getting the same error
cat: /etc/networkusermodules: no such file or directory
cat: /etc/networkusermodules: no such file or directory
killall:wpa_supplicant: no process killed
failed to connect to wpa_supplicant - wpa_ctrl_open: no such file or directory (this one is repeated several times)
Ok i think I may have kind of solved my problem. DO i need to save the profile before I can shoose to use it? I am now being able to talk to my router, but am unable to connect. I am noticing that I seem that the killall:wpa_supplicant always comes up as: no process killed so does that mean that it is not killing the connection each time i try? I also noticed that now neither my browser nor e-mail client will connect