Puppy Linux Discussion Forum

[mavrothal]

[rerwin]

Peebee & mavrothal,
Thanks for your further comments. They are not being ignored.

In the pdiag file I see that the entire kit was not installed. The tray icon update logic is moved to the woof_updates package. Please install it. It is separate so that it can be available even if frisbee is omitted; developers or users could set its flag to enable notification with the other network managers. Although the dhcpcd package appears to be optional, but why use only part of the complete frisbee solution!

I am working to reconcile your comments with my concept for frisbee. I probably need to treat the installation experience separately from the experience of initial boot-up after installing a new distro containing frisbee. I want the default states (whatever they turn out to be) to occur at initial boot-up if none of the flags are set, so that a remaster does not need to copy any flags. The flags should represent the exceptions and can be set during package installation or be built into a new distro (so would be copied in a remaster). Developers would then be allowed to pre-set any flag if they want an exception at initial boot-up of their distro/remaster. That is the beauty of using flags for control rather than hard-codded logic.
Richard

[peebee]

[rerwin]

[mavrothal]

Looks like that when X is restarted network_tray is not properly informed of the net state.
Starting a latter instance behaves as expected (see picture).
That is on precise 5.5 with frisbee 0314 and woof-additions 0314.

[jackwise]

Hi,
I'm a newbie using linux but I had no problem until last weekend.
Frisbee stops to work ( don't detect wireless connections) and I want to uninstall it, but with no success.
I uninstalled it from setup/installed packages but it still working.
I stop it from start-up boot but it still working.

How can I get rid of it ??

I'm using Puppy Linux Slacko last version.

I'd appreciate any help.

JW

[rerwin]

[jackwise]

[ASRI éducation]

[rerwin]

peebee, mavrothal and others,
Here is another shot at reconciling your reports and preferences. Frisbee is the only package that changed in the attached kit. Highlights:

- Installation defaults to a compatible puppy-type network manager configuration with all wireless options off except for pop-up notifications.
- If the "frisbee as default network manager" option is chosen during installation, all options are "on", wifi enabled and connected at startup (similar to the "beta" way).
- Most of the flags are replaced by a configuration file, frisbee.conf, because the flags became unwieldy.
- The "restart X" problem is managed; to restore normal network_tray function after an X restart, go into frisbee and click on either "Restart Networks" or "Restart DHCP".
- The "Enable WiFi" and "Connect Automatically" checkboxes are now separate checkboxes; previously one did both.
- "Enable WiFi" now greys-out the wireless fields if it is not checked (off), as would be expected of such an option; when not checked, wireless activity should be prevented, although I may have missed a place (so please report any inconsistency).
- Debugged the "Change Interface" button logic, using an added USB WiFi stick; did not test actual operations with two WiFis, so we may find issues to work -- I think frisbee uses only one at a time.
- Modified the pop-up notification feature so that it can be used with other network managers without conflict from frisbee; frisbee should control it independently but restore it upon exit (but not actually tested).

Richard

UPDATE 3/20/2013: Uploaded version 20130320 to correct the network_tray_modeset startup script to use the new configuration file instead of the old frisbee_mode flag file, an inadvertent omission. This should result in the correct setup of frisbee after a reboot.

UPDATE 3/22/2013: Oops! I inadvertently included the tarball inside the tarball, instead of the frisbee package. I have now re-uploaded the kit containing an updated version of the package that may address the issue with openvpn. (Sorry to be so slow, but real-life distractions occurred.)

UPDATE 3/24/2013: Re-uploaded to enable wifi and autoconnect for all frisbee installations, omit "Scanning..." pop-up if wifi or autoconnect are disabled and to update network_tray icons for better visibility in the dark blue tray area of precise pup 5.5.

UPDATE 3/25/2013: Re-uploaded to improve the logic for avoiding automatic wireless connection at boot-up and to ensure frisbee mode is set at boot-up, when appropriate, so that the frisbee network icons are used.

UPDATE 4/1/2013: Re-uploaded the kit, as 20130331, to restore the "scanning" message when automatic connection is deselected and to restore the functioning of the "dropwait" feature. The released version of the interface to it does not detect correctly the presence of the dropwait feature, so does not use it. Also split the 99-notify code file into 2, adding 99-frisbee, to separate out the frisbee-network_tray-specific logic. (Eventually, the network_tray logic will be removed from 99-frisbee.) The updated packages are frisbee and woof_updates.

UPDATE 4/20/2013: Note that a better version of the kit, frisbee-1.1/network_tray-2.7, is available on page 17:
http://www.murga-linux.com/puppy/viewtopic.php?p=698497#698497
with an improved tray icon and continued functioning after an X restart.

[mavrothal]

[rerwin]

[Atle]

Frisbee also let you use a Android phone as a router, connecting using USB.

In the Andriod menu, you need to be there and ready to press the icon where as USB connection is set, within a second or two, if you got a storage device in your phone. This as you insert the USB cable to the PC or Android.

Otherwise the storage device will snag the USB connection. Androids WITHOUT a storage device can take their time and press the check box for USB connection in what i call a normal pace...

Your android will route a Wlan connection or a Mobile internet connection trough the USB cable.

The big benefit of course is that there is no such thing as running out of battery:-)

[mavrothal]

[mavrothal]

Tried 0314 frisbee on precise 5.5 with ubuntu openvpn and was poor.
ie as soon as it connected to tun0 dropped the wlan0 connection and then was trying to reconnect to tun0 instead of wlan0.
Maybe was a "misbehaving" open AP, but did anyone tried openvpn with frisbee-1.0-<date> on precise OK?
(Precise 5.4.3 with Fribee-beta2 was OK with openvpn)