Network wizard Beta version for testers

[tempestuous]

do zydas addapters work with wext?

Yes, according to this - http://zd1211.ath.cx/wiki/DriverRewrite in the "Status" section.
And this - http://zd1211.ath.cx/wiki/WPAConfiguration

shockwave, the bcm43xx driver is definitely compatible with wpa_supplicant.

[shockwave]

tempestuous, thats what I found as well. What do you think my problem could be. I am running to other computers (ubuntu) off the same connection just fine. I have tried all the options given, but so far nothing? Any suggestions

[tempestuous]

You could try the manual setup explained here http://dotpups.de/dotpups/Wifi/wireless ... README.txt
or wait for others to report their results with the new wizard. There might be some bugs still to be fixed.

[shockwave]

Thanks. I will look over the manual and see if that helps. I will keep checking back for help. I am really impressed and excited about linux and how far it is coming. This is a huge step forward. Its the furthest I have ever gotten with this machine.

[tempestuous]

EDIT: May 2nd 2007.
Ralink-patched version of wpa_supplicant seems not to work with Ralink wifi devices.
Puppy 2.14 has the latest version 0.5.7 of wpa_supplicant.
For earlier Puppies, it's available as a dotpup here -
http://puppyfiles.org/dotpupsde/dotpups ... utilities/

I just recompiled wpa_supplicant with Ralink support.
Unfortunately this support appears to be only for Ralink rt73 (USB) and rt61 (PCI/PCMCIA) drivers. It appears that rt2500 (PCI/PCMCIA) and rt2570 (USB) miss out.
I used the patch from the rt73 source code, which is slightly different to the patch from the rt61 source code, so it's possible that only the rt73 is supported with the new package. I now wonder whether this effort was worthwhile.

Anyway, we now have 1 new driver name and 2 new interface names to deal with:

-D ralink
-i rausb0 ## for rt73
-i ra0 ## for rt61

The good thing about the new package is that I compiled it against the same version of Linux Wireless Tools that Barry will be using in Puppy 2.14: version 29pre10 (libiw.so.29). So we should have good compatibility with Puppy 2.14.

[barriew]

Rarsa,

Still trying to test - had other commitments last night!

I have got WEP to work, but that's not what this is about! Still can't get WPA to work. To make sure it wasn't a hardware problem I tried it in XP and had no problems.

Hereis the log from my last attempt

sh-3.00# net-setup.sh
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWMODE]: Invalid argument
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -

Just to confirm that I am running a hard disk Puppy 2.12 and using a zd1211b USB adapter to a Netgear DG834G wireless router.

Barrie

[tempestuous]

barriew, it might be a problem of associated encryption modules not being loaded. Before running the wizard, try this -

modprobe michael_mic
modprobe aes
modprobe arc4
modprobe libcrc32c
modprobe crc32c
modprobe ieee80211_crypt
modprobe ieee80211_crypt_ccmp
modprobe ieee80211_crypt_tkip

EDIT: Question marks after commands now removed because they were confusing.

[tempestuous]

EDIT: May 2nd 2007.
Removed.

[barriew]

it might be a problem of associated encryption modules not being loaded. Before running the wizard, try this -

This is the result!

sh-3.00# modprobe ieee80211_crypt
sh-3.00# modprobe ieee80211_crypt_ccmp
sh-3.00# modprobe ieee80211_crypt_tkip
sh-3.00# modprobe michael_mic
sh-3.00# modprobe aes ## ?
sh-3.00# modprobe arc4 ## ?
sh-3.00# modprobe crc32c ## ?
sh-3.00# net_setup.sh
sh: net_setup.sh: command not found
sh-3.00# net-setup.sh
killall: wpa_supplicant: no process killed
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success

Just to remind you that I don't particularly need this facility - I was just trying to help Rarsa by testing.

Barrie

[rarsa]

Just to remind you that I don't particularly need this facility - I was just trying to help Rarsa by testing.

And all the users that will need the functionallity really appreciate your testing (even if they don't realize they do)

I myself don't even need the wizard

[shockwave]

I still haven't got it working. I know for sure I can connect on an open connection. Does the wizard support wpa-psk or do I need to set it as regular wpa? thanks

[shockwave]

Ok i tried it in wpa tsk and still nothing. Any ideas. Also if it doesn't now, will this eventually work with psk?

[rarsa]

Ok i tried it in wpa tsk and still nothing. Any ideas. Also if it doesn't now, will this eventually work with psk?

Actually the current version of the wizard should work with WPA-PSK/TKIP.

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.

[tempestuous]

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.

[barriew]

Just to remind you that I don't particularly need this facility - I was just trying to help Rarsa by testing.

And all the users that will need the functionallity really appreciate your testing (even if they don't realize they do)

I myself don't even need the wizard

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.

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

[rarsa]

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.

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.

So, in working with you to solve the problem you report you are helping others and that's how I see it.

[PaulBx1]

Been out for a bit, see there is new progress. I will respond to your comments a couple pages back.

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.

Yes, I agree with breaking it down between basic and advanced. Most will be served by the basic screen.

In the advanced screen, you can enter "channel" or "frequency" IIRC. Of course those two are connected

I didn't know! can you tell me more?

Look at this page, which has a setup program for WPA:
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.

I debated for a moment with my self, Should I use "human" labels or the actual driver name "madwifi", "hostap", "wext".

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.

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?

[PaulBx1]

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...

[shockwave]

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.

[rarsa]

IIRC part of my problem was that everything in the wizard referred to drivers or modules

Well, it refers to drivers or modules when I am talking about drivers 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.

Another difficulty I had was that you have things like "pci:" in the front of each name

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.

I guess my preference would be for chipset names, with a flyover containing the driver name.

Ejem ejem... I guess that I haven't been clear enough on the limitations of the UI toolset.

FYI here (starting about in the middle of the page) are the common different ways the .conf file can be set up using WPA

Yes, I know that WPA does many things. But I'm implementing and testing one at a time.

One thing I was curious about. I wanted to look at what the output of the wizard was

Are you pulling my leg? I gave you that information in this post

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.