(old)Puppy Linux Discussion Forum

divisionmd,
Since frisbee is designed to run in a graphical environment, it depends on X being active.

However, once you have used it to set up a connection, maybe its setup would persist across a reboot where you could try the "pfix=nox" boot option. Maybe the connection would be made. But you could not change anything about it without frisbee in an X environment. I have never attempted that, although you might. But it would run into trouble if it needed to issue a graphical message/popup.
Richard

I have wary 5.5. I was able to install xpupsay, but the frisbee for wary 5.3 won't install.

The download link for Frisbee+xpupsay-beta2-0912.pet version 1 isn't working for me. Is it available now somewhere else?

Or is there a Frisbee that will install in wary 5.5? thanks

rbrehton wrote:I have wary 5.5. I was able to install xpupsay, but the frisbee for wary 5.3 won't install.

The download link for Frisbee+xpupsay-beta2-0912.pet version 1 isn't working for me. Is it available now somewhere else?

Or is there a Frisbee that will install in wary 5.5? thanks

This is a forum issue - all attachments greater than 256kb became unavailable some time ago without notice.

I don't think I have that pet any longer - but if I do locate it I'll post a link here.

Ok, thanks

You're lucky that I never throw anything away.....

https://e-nautia.com/peebee/disk/share/ ... 2-0912.pet

peebee wrote:You're lucky that I never throw anything away.....

https://e-nautia.com/peebee/disk/share/ ... 2-0912.pet

I appreciate it very much , thanks.

UPDATE: Installed and worked without a problem, thanks again.

I have used it with Slacko Pup 5.7.0, so I was wondering if I could find a source tarball someplace so I could try running it on my slackware distro?

Let me know if you know, and where I could find it, please?

Thanks

I'm thinking maybe I'm wasting time messing with it and I'd be better off spending the same effort tweaking Slacko Pup 5.7.0 because it already does most things I'm asking for.

Hey Bob, you're aware of this, right?

My reworked version of pgprs-1.5 has a bug that impacts anyone attempting to use it where a username and password are not expected to be included. Earlier versions required all fields to contain something so required dummy entries for username, password and PIN code (gprsuser, gprspassword, 1234) even if they were not valid for the modem.

Version 1.5 avoids the need for those dummy values but incorrectly retains logic to require the username and password. The replacement, 1.5.1, changes that requirement to allow both or neither. If anyone knows of a case where only a username or password is appropriate, please tell me.
http://www.murga-linux.com/puppy/viewto ... 398#757398
Richard

I just now discovered and fixed a typo that prevented the "Restart Networks" and "Restart DHCP" buttons from performing their restarts. Frisbee-1.3.2 is with the earlier 1.3.x frisbees at:

http://www.murga-linux.com/puppy/viewto ... 962#780962

However, the fix can be made manually to versions 1.3 and 1.3.1 by editing the file:

/usr/local/frisbee/frisbee-wifi-disconnect

line 5 (changing the "-" to "_") to read:

reset_dhcp&

This does not affect versions of frisbee before 1.3.
Richard

How do you remove builtin Pwireless as Frisbee goes well ?
I trashed what i found with Pfind, but it's not a clean way.

I have built new frisbee and dhcp packages for Tahrpup, Precise and Slacko. I have tested wireless only on tahrpup, but verified that the others support ethernet. Although the Precise version appears to run on Tahrpup, the Tahrpup version will not run on Precise nor Slacko.

The main improvement to the frisbee-1.3.3 package is that the user's existing wireless and frisbee setups are retained during installation, thanks to 666philb's calling my attention to that issue. The configuration files, dhcpcd.conf, frisbee.conf and wpa_supplicant.conf, are not replaced if present. Frisbee.conf gets updated, if necessary, to append new statements. Other than the settings issue, the functionality remains the same as in 1.3.2.

The dhcpcd-dropwait-6.7.1 is the current release at this time and includes a wait of up to 3 seconds for a lost carrier (connection) to get re-detected. This occurs for all network managers, not just frisbee. The old "dropwait" value option has been removed in the 1.3 frisbees -- one less variable to attend to.

Besides the puppy-specific "dropwait" versions of the dhcpcd packages, I include an "original" version of dhcpcd without the dropwait patch -- for tahrpup and later, only -- in case a developer prefers to omit the dropwait feature. I also include the source packages, which contain README-* files that explain how to build the pets.

The previously offered workaround for the automatic "hot plug" start up of wpa_supplicant for added USB wifi devices is no longer needed. Because puppy's network managers were designed without that automatic starting of wpa_supplicant, I have removed the new "hook" file, 10-wpa_supplicant, from the dhcpcd packages. To test any network manager that might be modified to handle the new dhcpcd feature, that file can be obtained from the source package's dhcpcd-hooks directory.

As always, please report any misbehavior of frisbee or dhcpcd so that I might address it.
Richard

UPDATE 4/10/2015: Uploaded frisbee-1.3.4 to incorporate recommendation by rcrsn51 to prevent shutdown hang when frisbee and samba used concurrently.

UPDATE 4/26/2015: Re-uploaded frisbee-1.3.4, after download number 20, to correct the version number displayed in its window title. As there is no functional change, individuals need not replace the original "1.3.4" -- but distro developers should take it for the next update of their distros.

hamoudoudou wrote:How do you remove builtin Pwireless as Frisbee goes well ?
I trashed what i found with Pfind, but it's not a clean way.

hamoudoudou,
Your screeny tells me your are using Pwireless2. I found the thread for that here:
http://www.murga-linux.com/puppy/viewto ... 371#360694

I downloaded the pet package and listed its files.

To answer your question: If you have installed either pwireless or Pwireless2, then uninstall them. But I assume it is more complex than that. Since my copy of Puppy 4.3.1 does not contain Pwireless2, my guess is that you are using a remastered version that has Pwireless added.

Here is an edited list of the files I found, which would be candidates for removal -- but only if they are not needed by Frisbee. Instead of deleting the files, you can remove "execute" permissions or rename files or directories as indicated in the statements bounded by "[" and "]".

You should probably experiment with a separate pupsave file where you first delete the Pwireless2 files in the list, then install the Frisbee beta package that seems to work for you.

Please be aware, though, that Pwireless and the Frisbee beta packages are beyond what I take responsibility for -- I maintain only frisbee-1.0 and later. HTH
Richard

it's the french Puppy named 'Toutou'with pwireless included. Desactivate pwireless instead of removing is the idea. Ok i will do as you suggest.
The icons were still in the tool bar because i did'nt scratch everything.
Remove builtin apps is not in the menu of this Puppy. (or i did'nt see it)
Thanks rerwin.

Used Frisbee-1.3.1 in 666philb's new vividpup.....

Pleased to see that the long delay between finishing the connection and getting the confirm default screen seems to have gone.

Had a problem in that a connection was established but neither the tray icon nor the tray popup message reflected this....

Cheers
peebee

peebee wrote:Used Frisbee-1.3.1 in 666philb's new vividpup.....

Pleased to see that the long delay between finishing the connection and getting the confirm default screen seems to have gone.

Had a problem in that a connection was established but neither the tray icon nor the tray popup message reflected this....

Peebee,
Thanks for your report. Please be sure that file /usr/local/frisbee/frisbee-wifi-disconnect is edited to correct the line, "reset-dhcp&" to "reset_dhcp&", or use frisbee-1.3.3, instead (which corrects that problem).

Maybe that will also fix the connection-feedback issue. If not, please send me a pdiag.
R

peebee wrote:Used Frisbee-1.3.1 in 666philb's new vividpup.....

Had a problem in that a connection was established but neither the tray icon nor the tray popup message reflected this....

After exploring this issue with Peebee by PM, I concluded that a bug in network_tray can make the icon program fail to cycle to obtain changes in the traffic and connectivity! The cycling is controlled by a value set by the cyclic function each time it completes a cycle (every half second) -- except that it never sets a value (TRUE)! The value is whatever happens to be there when the program is running; if it is zero, the cycling fails to occur. The solution is for the function to "return TRUE".

I have updated the 2.7.x version of network_tray and attach it, along with the source tarball and a difference listing that can be converted into a patch file for application to other versions of network_tray.
Richard

@rerwin: You may be interested in the discussion here. I can confirm the bug and the fix at Line 66.

hi, not sure if this is the right place to post this, but can no longer connect to wifi on a stock Tahrpup.

the frisbee interface loads, and i can see all hotspots in my vicinity. if i try to connect on one, frisbee asks for the password. I enter the correct password, and i see 'wlan0 is down'. Doesn't connect.

i see a wl module already blacklisted.

i'm about to just reinstall puppy to get around this, but would be cool to find a fix.

thx!