(old)Puppy Linux Discussion Forum

The networking script makes the assumption that driver for your wireless card loads automatically on boot. If that is not the case, and you are loading it manually with Network Wizard, you need to use the bootconfig tool to force it to load during bootup.

It's 11.30 pm local time and I'm probably not thinking too well, but I was getting a situation where Pwireless2 was showing several networks, including mine, and my profile was loaded, but although the banner came up to announce that an ip address had been obtained I couldn't connect to the web. I uninstalled Pwireless - also removed the original using Petbegone - and things are back to normal i.e. connection up and running through Network manager. I'll try some more tomorrow, when i can get a few more grey cells firing!

Usually, if you get an IP, and still can't connect, the problem is with /etc/resolv.conf. If it happens again, can you check and make sure that file is not empty?

This is interesting, though I don't fully understand what it means. In /etc/resolv.conf nameserver is shown as 10.0.0.2, whereas the IP obtained when connecting is regularly 10.0.0.4. I'm running at the moment without Pwireless, Network wizard settings saved, and my wireless came up at boot. With Pwireless there was some activity during boot, but it ceased before x-window started, which suggests that a hand-over isn't going properly? When I've got an hour or so today I'll check the other areas you mentioned and see if I can spot anything.

I'm going to try to merge in parts of the network wizard to Pwireless2 to make it work on less generic setups. Do any other developers want to help on this project? Making Puppy's wireless more friendly to laptop users is pretty important.

I've uploaded a new version with a bugfix for interfaces not named wlan0. I had hard-coded it and I meant to go back and fix it, but forgot.

Hi jemimah

This is my first test of this and my wireless interface is wlan0.

Nothing shows in the guis.[ ]

Using dpup beta 4 with rt87usb module (TP link B/G usb adapter.. cheapo) which normally works ok in all puppies any kernel. If you need more info I'll be happy to oblige.

Cheers

(below may be a clue )

When you say nothing shows, does nothing show under status? or no networks show up? or both?

Nothing in any of the notebook tabs.. BTW, edited post with screeny while you were posting

can you try running the /root/Startup/networking script from the command line and see what the error is? You're supposed to get a dialog if wpa_supplicant fails to start.

ok... brb

H there

Interestingly the yafs show up now that i had to reconnect through the network wizard..

Here's the out put.. Hope this helps

Does the file /var/run/wpa_supplicant exist? It seems wpa_supplicant started, but some file is missing.

EDIT: I guess /var/run/wpa_supplicant should be a directory. Maybe I need to add that to the pet.

EDIT:hmm it doesn't exist by default in standard Puppy either, so that's probably not it.

jemimah wrote:Does the file /var/run/wpa_supplicant exist? It seems wpa_supplicant started, but some file is missing.

EDIT: I guess /var/run/wpa_supplicant should be a directory. Maybe I need to add that to the pet.

EDIT:hmm it doesn't exist by default in standard Puppy either, so that's probably not it.

1.. no

2 I don't know

3 don't know either.

But I did have to stuff around to get back online..

Please, do NOT be discouraged. I'll help when I can. I know what these problems are like!

Cheers

Would you be so kind as to create the /var/run/wpa_supplicant directory, and then restart?

If that doesn't work, can you try the attached updated version of wpa_cli?

Forget all that BS I posted earlier! While I disabled the network wizard i did not delete the profile (fine print... do please make it larger for idiots... er .. like.. no..)

It is working now.. Sorry to cause you grief.

I owe you one

Well see that's the problem and where I need the most help. It would be nice to figure out how to integrate it, or at least make it play nice with network wizard. But figuring out other people's gtkdialog code is headache-inducing to say the least! (and I thought Perl was the only write-only language)

You'll get there. There's a couple of Bash/gtkdialog gurus around here... just shoot them a PM if you get stuck, I've only been coding in bash for less than 12 months and that's what I do.

Testers are the hard ones to snag!

Cheers and thanks.

I've tried it on 3 Puppies. Using full installs.
4.1.1 and 4.1.2 with the 2.6.25.16 kernel and 4.3.1 with 2.6.30.5
kernel.
Tried with both Atheros cards in my signature and a Belkin
f5d7050 with zd1211rw module.
The Atheros cards use ath5k in the latest kernel and have a
difficult time with wpa in the network wizard, but connect
easily with Pwireless2. Belkin works fine also.
It worked with 4.1.2 and 4.3.1 but not with 4.1.1.
When I deleted it from 4.1.1 it seems to have taken some
necessary wpa files from the standard wizard along with it.
I restored the files with a live 4.1.1 cd and the wizard works
again.
I could only get the gtray icon to show up on 4.3.1.

Pwireless2 can make connection much easier for new
Puppy users. I like it a lot.

rjbrewer, thanks for testing! Which files did you need to restore to fix 4.1.1? I suspect the libgio dependency is why the applet doesn't show up on earlier versions. Maybe I'll add a link to it in the original post.