Page 2 of 13

Posted: Mon 16 Nov 2009, 00:25
by jemimah
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.

Posted: Mon 16 Nov 2009, 05:47
by 01micko
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 :? )

Posted: Mon 16 Nov 2009, 06:24
by jemimah
When you say nothing shows, does nothing show under status? or no networks show up? or both?

Posted: Mon 16 Nov 2009, 06:28
by 01micko
Nothing in any of the notebook tabs.. BTW, edited post with screeny while you were posting

Posted: Mon 16 Nov 2009, 06:32
by jemimah
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.

Posted: Mon 16 Nov 2009, 06:35
by 01micko
ok... brb

Posted: Mon 16 Nov 2009, 06:41
by 01micko
H there

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

Here's the out put..

Code: Select all

# ./networking
dhcpcd: version 5.1.3 starting
# killall: yaf-splash: no process killed
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory
killall: yaf-splash: no process killed
dhcpcd: eth0: broadcasting for a lease
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
dhcpcd: allowing 8 seconds for IPv4LL timeout
dhcpcd: eth0: probing for an IPv4LL address
dhcpcd: eth0: checking for 169.254.19.42
dhcpcd: eth0: using IPv4LL address 169.254.19.42
killall: yaf-splash: no process killed
dhcpcd: forking to background
Hope this helps :)

Posted: Mon 16 Nov 2009, 06:50
by jemimah
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.

Posted: Mon 16 Nov 2009, 07:10
by 01micko
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

Posted: Mon 16 Nov 2009, 07:16
by jemimah
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?

Posted: Mon 16 Nov 2009, 07:25
by 01micko
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 :wink:

Posted: Mon 16 Nov 2009, 07:30
by jemimah
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) ;)

Posted: Mon 16 Nov 2009, 07:36
by 01micko
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.

Posted: Mon 16 Nov 2009, 08:26
by rjbrewer
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.

Posted: Mon 16 Nov 2009, 15:40
by jemimah
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.

Posted: Mon 16 Nov 2009, 17:37
by rjbrewer
jemimah wrote:rjbrewer, thanks for testing! Which files did you need to restore to fix 4.1.1?
Looks like I removed more than profiles when I initially tried it.
Did the pwireless2 install again, deleted it from package manager
and ran netwizard and it worked okay. False alarm.
With 4.1.1, pwireless2 window doesn't show a scan.
There were a lot of changes to wireless in the 4.xx series development,
some having to do with wpa. Mostly fixed by 4.1.2.

Am I missing something?

Posted: Mon 16 Nov 2009, 19:06
by technowomble
jemimah. 01micko mentioned disabling the network manager, maybe that's why I've had problems with pwireless2. I'd removed the profiles from /etc/network-wizard/profiles and wpa_profiles but couldn't see how to disable network manager.
BTW for information, my wireless is Edimax EW7608Pg, pcmcia using the rt61pci driver and I'm using it in Puppy 4.2.1 with 2.6.25.16 kernel.

Posted: Tue 17 Nov 2009, 04:27
by jemimah
To make sure it's absolutely and completely disabled, you can move or rename the file /etc/rc.d/rc.network and reboot.

Posted: Tue 17 Nov 2009, 20:08
by hayagix
Pwireless2 is a tremendous tool! Love the quick connect/disconnect and readout at top of screen. This certainly rivals gnome network manager and wicd which seem to be the best tools for managing wireless in linux.
I use network wizard to setup the card. I've switched back to ndiswrapper from the included rt2500usb linux drivers. Ndiswrapper is much, much faster darn it. Set ndiswrapper to load at boot time with the boot manager. Do not create any profiles with network wizard and rename it in rc.d to prevent a conflict. Exit to a prompt seemed to do the trick to get pwireless2 to detect the network card for those of us running live.
Thanks again for developing this.

Posted: Tue 17 Nov 2009, 21:08
by DapperMe17
Hello,

Sounds like a nice tool!

Does anyone know if it will work with the Broadcom BCM4306 chip? The PC uses WPA encryption. (HP laptops)

Neither stock wireless managers pick up my network in Puppy. Wireless connectivity is the only thing preventing use of Puppy.

In Ubuntu, it's runs as WLAN0...