One should use ap_scan=1 for networks that broadcast the SSID and ap_scan=2 for networks with a hidden SSID.

I "half-knew" this, but thanks for spelling it out.
I think rarsa has already dealt with this situation in the Network Wizard - the default value in /etc/wpa_supplicant.conf is "ap_scan=2" and the gui shows the "AP Scan:" selection as "Hidden" - refer attached image.
When "Hidden" is deselected, the other two values become available - "Supplic." and "Driver". I assume that "Supplic." sets "ap_scan=1" and "Driver" sets "ap_scan=0".

I'm thinking that it would be more clear for users if "Supplic." was re-labelled "SSID broadcast" and "Hidden" was re-labelled "SSID hidden".

I realise you probably can't test whether the Wizard sets the correct values because of the various other bugs with the Wizard under Puppy4.x, but it appears that Barry has now sorted these bugs and hopefully you will be able to check the Wizard when Puppy 4.1 is released.

I thought that crypto_blkcipher was related to WEP encryption, but I see from JustGreg's results in Puppy4.01alpha2 that the crypto_blkcipher module is loaded after a WPA connection ... so maybe it's necessary for both WEP and WPA.

astrogreek wrote:

When I tried to load I got a message saying "driver not found"

astrogreek it's really important to reveal the exact Puppy version you are using when asking for help. It's also useful to reveal the device and the driver (module) in question.
The crypto_blkcipher module definitely exists in the experimental Puppy4-k2.6.25, and Puppy4.1 alpha1 and alpha2.
The crypto_blkcipher does not exist in earlier Puppy versions.

Generally, wifi in Puppy4.x is still under development and testing.
Wifi under Puppy3.x is quite solid.

Well, I have tried Puppy 3.01, Puppy-4.00-k2.6.21.7, puppy-4.00-with-2.6.25-kernel. By device, do you mean my wireless card? It's an Intel PRO Wireless 2200 BG. Reveal the driver module; I don't understand.. As far as I can tell, the modules you listed are loaded, except the crypto_blkcipher module (I used the 2.6.21.7 kernel when I tried loading that module). My connection uses WEP. The modem does not belong to me; it's nextdoor in my landlord's flat, so I cannot mess with its settings. Please bear in mind I am (almost) new to Linux.

Yes, yes. That means that your wifi driver should be the ipw2200.
But there are so many questions still remaining about your circumstances.
This forum thread is, after all, not about wifi connectivity in general. It was created specifically to deal with encryption-related connectivity problems.
We don't know whether you can establish a wifi connection with encryption (WEP/WPA) turned off. This is an important diagnostic step, and if your landlord won't temporarily disable encryption for you to test, you should probably borrow a different wifi router specifically to test with.

Yes, yes. That means that your wifi driver should be the ipw2200.
But there are so many questions still remaining about your circumstances.
This forum thread is, after all, not about wifi connectivity in general. It was created specifically to deal with encryption-related connectivity problems.
We don't know whether you can establish a wifi connection with encryption (WEP/WPA) turned off. This is an important diagnostic step, and if your landlord won't temporarily disable encryption for you to test, you should probably borrow a different wifi router specifically to test with.

SOLVED! I noticed in my wireless setup in Xubuntu the mention of ascii key; I did some Googling and found that I had to add s: before my key to make it work, like this:
iwconfig [interface] s:mykey (set key as an ASCII string)
I followed the guide from the Wifi HOWTO (which I have done many times in the past without success), with the only difference the addition of the "s:" before my key.

There seems to be no option in the network wizard to select hex or ascii, or any mention anywhere that this might be an issue. No Linux newbie should have to struggle like this to get on the internet.

SOLVED! I noticed in my wireless setup in Xubuntu the mention of ascii key; I did some Googling and found that I had to add s: before my key to make it work, like this:
iwconfig [interface] s:mykey (set key as an ASCII string)
I followed the guide from the Wifi HOWTO (which I have done many times in the past without success), with the only difference the addition of the "s:" before my key.

There seems to be no option in the network wizard to select hex or ascii, or any mention anywhere that this might be an issue. No Linux newbie should have to struggle like this to get on the internet.

I recall raising the matter of the "s:" option some time ago, but it was decided it is unnecessary... I think the wizard converts ascii keys to hex, then uses the hex._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

I recall raising the matter of the "s:" option some time ago, but it was decided it is unnecessary... I think the wizard converts ascii keys to hex, then uses the hex.

This would be true from what I have seen. After entering the ascii WPA passphrase(key?) into the Network Wizard, and after connection, I have found the hex version of the key is in the wpa_supplicant.conf file as psk=xxxxxxxxxxxx.

It actually replaced the ascii key that I originally had typed into the wpa_supplicant file.

Hey!
Finally I booted up Puppy 3.01 and connected to a WPA encrypted wireless network without any problem.

I've tried connecting to this network with Puppy 4.00 (and the newest 4.1 alpha as well) without success. The closest I've come using dingo, was 5 or 6 seconds internet connection. After each reboot it is possible to do that with the network wizard, but only once. Obviously (beeing a linux newbie) I don't know what is wrong. But I find it very interesting that puppy 3 doesn't have any trouble connecting. I've also tried Linux Mint and xubuntu on this Dell Inspiron 510m, and they connect without any trouble.

If anyone has any interest in exploring this issue furthermore, please let me know, and I will gladly assist.

I have been able to use WEP 64 for many months, using versions2.15CE, 3.01, 4.0, 4.11 and 4.12. My computer has IPW2200B/G. When I started having problems with 4.12, I tried my old USB drives with the older versions, and they no longer work.
I have used a 10 digit (phone) number as Key which I enter into the router as hex. At times in the past I needed to hyphenate the number when entering it into the network wizard:
1234-5678-90
which it apparently converted to something.

I read this thread with only slight understanding. I did the lsmod |grep crypto
and did have 2 with WEP in their name. Any suggestions???

FWIW, WinXP connects automatically, but does not have near the range that I get with Linux.

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