(old)Puppy Linux Discussion Forum

Weird, I don't know then. The only other difference is my custom kernel. No one else has complained so far. I'll investigate when I get a chance.

jemimah wrote

Did you get it working Dave?

Sorry for the delay in replying. Yes I did get it running after I extracted
libQtGui.so.4.3.2 and libQtCore.so.4.3.2 from the pet you supplied.
Many thanks
Dave

Puppy's network manager works fine for me but this tool has some good features.
It is nice to have quick access to networks via taskbar icon.
It is also nice to be able to toggle the network on and off quickly.

I needed to install the full qt package to get it working properly and delete profiles in NetworkManager.
It works fine with a Wep network. I am curious to see how it handles Wpa but it will be some time before I can test.

This was in 4.3.1 and Thuxxx's 4.3

Good job and much appreciated!

I think I've discovered a working gtk-based alternative to wpa_gui, that also uses wpa_supplicant as the backend. It's part of the dhcpcd project. Screenshots are here: http://roy.marples.name/projects/dhcpcd-ui/screenshots

The interface is simpler, less confusing, and integrates dhcp setup. It requires dbus, and libnotify, but I think I can make it use yaf-splash instead so libnotify and notification daemon are not required.

I am testing it in Puppeee right now so we'll see how it goes. So far, wpa-gui seems to confuse a lot of people, so hopefully this small and simple alternative will work out. I'll post a pet shortly.

the only extra dependencies I see are dbus and dhcpd-dbus (aside from wpa-supplicant)

Hmmm, actual field testing shows it to be rather unstable. I was really hoping it would work. I'll keep poking at it, but I can't recommend it at this point.

EDIT: perhaps I figured out the problem... we'll see. This is why I hate programs that need multiple daemons. Way too many moving parts!

EDIT2: okay so I forgot to copy some files for dhcpcd, now it's much happier. Also it was putting quote marks around the key, causing wpa_supplicant to misidentify the type of encryption. That's fixed, at least for WEP. I don't have a wpa network to test on. This tool lacks a way to disconnect, and reconnect without re-entering your key. That's probably easy enough to add.

I've been thinking about this and doing some more research. Wpa_supplicant also comes with a wpa_cli utility that seems completely full featured. I think it would not be hard to modify Pwireless to be a usable wpa_supplicant front-end. I may attempt this if I get a free weekend. It would probably also be trivial to create a monitoring script that throws up a yaf-splash whenever your network status changes, making an applet unnecessary.

Well the yaf-splash notifications are done. The new version of dhcpcd has event-hooks that will run whatever scripts you want whenever network changes happen. Very cool!

I had a free weekend and Pwireless2 is now almost complete.

It supports open,wep,and wpa-personal networks. It's a lot faster than the original Pwireless and it's completely event-driven, so it never needs to reload itself. It requires wpa_supplicant and dhcpcd to be running in the background, just like wpa_gui.

I was even able to create a simple applet for it that allows you to connect and disconnect with an icon that changes depending on network status. Dhcpcd takes care of notifications, so the applet is optional.

n/t

You can use fltk schemes with it to make it look a little different. http://www.murga-linux.com/puppy/viewto ... 666#347666 It also looks a lot better with the antialiased font patch.

I plan to release a new flwm package when things with puppeee slow down. Likely real soon now.

Hopefully I'll have time to make a pwireless2 pet tomorrow.

Are you using fluid (fltk) or gtkdialog (gtk) for your wireless gui? The flwm window just made me wonder

Is Pwireless2 available to download as a PET file?

TIA

Technosaurus, it's gtkdialog.


I'm working on the Pet today. I'll let you know when I post it.

Thanks

The pwireless2 pet has been posted http://www.murga-linux.com/puppy/viewtopic.php?t=48816

Thanks guys for these network managers. I didn't think I was ever going to get the wifi on my HP laptop to work with Puppy. Network wizard could see my wireless router on a scan but when it tried to assign an IP address it would either come up with something completely eroneous or a message saying unable to establish WPA connection. However I tried WPA_GUI and Pwireless2 and either one works great.

Cheers

hello
so to conclude, which one is recommended ?
smaller the better, I'm having great difficulty connecting wirelessly on an eeepc 1001ha which uses a ralink rt3090 card on any flava of linux.
I might well try both and see how it goes

puppy's the business

I doubt this wpa-gui will work since it assumes your interface is named wlan0. Pwireless2 is smarter and better.

Hmm, I didn't know about that rt3090 card previously. I will add the driver to Puppeee which uses a newer kernel that has a lot of the bugs with the ralink cards fixed. The proprietary staging drivers from Ralink are really bad, especially for wpa. The newer kernels have native drivers.

I just checked and it says that the rt2860 driver can handle the rt3090 card, so you should be good to go with Puppeee which already includes Pwireless2. http://www.murga-linux.com/puppy/viewtopic.php?t=48288

Let me know if you have problems.