Frisbee is a Wpa Roaming frontend inspired by Wpa Gui. It is also a frontend for Dhcpcd.

Frisbee supports Open, WEP, and WPA Personal wireless networks as well as Ethernet. Support for AdHoc networks is still mostly untested.

Frisbee scans constantly for changes to your networking environment so you won't be dropped. Frisbee can roam between wireless networks automatically. It can also detect any time you plug in your ethernet cable and connect automatically.

Frisbee_tray knows if you're connected by wired, wireless, or modem and the icon changes to indicate which it is.

---

I've tested it briefly on Lupu, Wary, and Puppy 4.2.

To install, first get the correct wpa_supplicant pet. Wpa_supplicant is picky about openssl so it needs to be compiled on the target platform. The pet for Lupu only contains symlinks, but the wpa_supplicant in other puppy versions will not work with Frisbee. (Wpa supplicant needs to support the '-f' option for logging).

Then download and install my patched dhcpcd. The patch makes dhcpcd wait 6 seconds before disconnecting you when your connection drops. This is needed for a smooth experience in cases when you have a weak wireless connection.

Then install the xpupsay pet. I use xpupsay for notifications. Frisbee could be modified to use the splash program of choice, but xpupsay is the least work for me since that's what I use in Fluppy.

Then install the Frisbee pet. It'll probably work with out a reboot now.

If you'd like to report a bug, go into Wireless Diagnostics and generate the diagnostic data. You can then attach the tarball it creates to your post.

Beta 2 Changes:

The dhcpcd patch has been improved. Now you can configure the drop timeout from the GUI. Drop timeout now only affects wireless networks, ethernet should respond to changes instantly.
Bugfix for the tray applet not working right when you're using a static IP.

To upgrade from Beta 1 to Beta 2 you must update both the Frisbee pet and the dhcpcd pet. The other pets are unchanged.

Wireless working OK on the Asus Eeepc 701 with Puppy 5.2.
I noticed two neighbours networks, one using WPA
and one using BTOpenzone (Frisbee may have connected to this? Would that be expected behaviour?) The signal was weak and it went off again
The WPA is private
Is the BTOpenzone private too?
BTOpenzone seems to have no encryption methodology . . .

Be interested how this compares with existing Puppy scripts and
whether it is smaller. Certainly seems very easy to set up following Jemimah's instructions _________________Puppy WIKI

The main difference between Frisbee and other scripts is that I offload all the heavy lifting to wpa_supplicant and dhcpcd. All Frisbee does is start wpa_supplicant and dhcpcd and help you configure them. The point of Frisbee is to be as simple as possible and easy to maintain.

Now for the (minor) downsides. There seems to be an issue holding the connection to the internet. In my house, if using the eeepc at the opposite end of the house from the router, the internet drops out much more frequently than with the previous puppeee with pwireless. Strangely, the connection doesn't drop out as often when connected to the LAN to access movies or such. I don't know if you've ever experienced that kind of behaviour, or if its just my network.

Anyway, in a situation such as this where it drops out, the network still shows up in the networks found box, but doesn't connect automatically. Perhaps a "connect" button could be added to do this. I can press the reset dhcp button, but that seems to take a lot longer than necessary(?).

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