Posted: Thu 05 Jun 2014, 20:44
Hi David Andrew,
Did you have the same problems with the included (older) frisbee in DebianDog?
Fred
Did you have the same problems with the included (older) frisbee in DebianDog?
Fred
READ-ONLY Archive
https://oldforum.puppylinux.com/
Yeah. I started off with the default Frisbee that came with Debiandog, then I installed the 1.2 tarball update but the same problem persisted, and then I finally tried the .deb package, also no change.fredx181 wrote:Hi David Andrew,
Did you have the same problems with the included (older) frisbee in DebianDog?
Fred
Code: Select all
<label>$(gettext 'BSSID |Freq |Strength|Encryption |SSID')</label>
Code: Select all
<label>$(gettext 'BSSID |Freq |Strength|SSID |Encryption')</label>
Code: Select all
wpa_cli scan_results -i $INTERFACE |grep ^..:..: |sed 's/ /|/g'
Code: Select all
wpa_cli scan_results -i $INTERFACE |grep ^..:..:| awk '{print $1"|"$2"|"$3"|"$5"|"$4}'
Code: Select all
killall wait-disconnect
Code: Select all
if (if_type_icon_data[wifi].if_type_status == connected) \
menuitem = gtk_menu_item_new_with_label(_("Disable wireless network"));
else menuitem = gtk_menu_item_new_with_label(_("Enable wireless network"));
g_signal_connect(menuitem, "activate", (GCallback) view_popup_menu_onDisconnect, status_icon);
Code: Select all
if (if_type_icon_data[wifi].if_type_status == connected) {
menuitem = gtk_menu_item_new_with_label(_("Disable wireless network"));
g_signal_connect(menuitem, "activate", (GCallback) view_popup_menu_onDisconnect, status_icon);
}
else {
menuitem = gtk_menu_item_new_with_label(_("Enable wireless network"));
g_signal_connect(menuitem, "activate", (GCallback) view_popup_menu_onReconnect, status_icon);
}
Scooby, The inconsistency is between the version of "dropwait" and the version of the dhcpcd patch you used. The released version of the modified dhcpcd returns this for the --help option:Scooby wrote:However it doesnt use the dropwait feature and when I looked at script
/usr/bin/dhcpcd_dropwait_option I think I found a inconsistency.
The diffs I found at http://www.murga-linux.com/puppy/viewtopic.php?p=662522
( a bit far down )
are from Sun 04 Nov 2012, 22:55 so maybe this are not the latest ones?
Anyway in script there is check for --dropwaitbut in the diffs I found there is onlyCode: Select all
DWOPTION="$(dhcpcd --help | grep -o '\--dropwait' | cut -f 1 -d ' ')"
That means --dropwait would never be found.Code: Select all
+ " [-r ipaddr] [-s ipaddr] [-t timeout] [-j dropwait]"
Code: Select all
usage: dhcpcd [-ABbDdEGgHJKkLnpqTVw]
[-C, --nohook hook] [-c, --script script]
[-e, --env value] [-F, --fqdn FQDN] [-f, --config file]
[-h, --hostname hostname] [-I, --clientid clientid]
[-i, --vendorclassid vendorclassid]
[-j, --dropwait seconds] [-l, --leasetime seconds]
[-m, --metric metric] [-O, --nooption option]
[-o, --option option] [-Q, --require option]
[-r, --request address] [-S, --static value]
[-s, --inform address[/cidr]] [-t, --timeout seconds]
[-u, --userclass class] [-v, --vendor code, value]
[-W, --whitelist address[/cidr]] [-y, --reboot seconds]
[-X, --blacklist address[/cidr]] [-Z, --denyinterfaces pattern]
[-z, --allowinterfaces pattern] [interface] [...]
dhcpcd -k, --release [interface]
dhcpcd -U, --dumplease interface
dhcpcd --version
dhcpcd -x, --exit [interface]
Ok I checked it out, its just the argument handling that has changed not the active code.rerwin wrote: I have dug around the PC I developed dropwait on and found the source for dhcpcd 5.6.4, which is what is in precise and woof. I made a difference/patch file, which is attached. Please try that with your newer version(s) of dhcpcd. It is for the same source package as posted here:
http://www.murga-linux.com/puppy/viewto ... 311#678311
Code: Select all
else if (carrier == LINK_DOWN || (ifp->flags & IFF_UP) == 0) {
if (ifp->carrier != LINK_DOWN) {
//JEMIMAH START
if (ifp->wireless) {
ts.tv_sec = ifp->options->dropwait;
ts.tv_nsec = 0;
nanosleep(&ts, NULL);
carrier = carrier_status(ifp);
if (carrier == 1) return;
}
//JEMIMAH END
if (ifp->carrier == LINK_UP)
syslog(LOG_INFO, "%s: carrier lost", ifp->name);
ifp->carrier = LINK_DOWN;
Code: Select all
terminal=rxvt #terminal emulator that takes the "-e" (execute/command) option
editor=defaulttexteditor
Code: Select all
[ "$(pidof wait-disconnect)" ] && killall wait-disconnect #140607
I'm not sure were to post about issues with 01mickos network_tray 2.7.2? here?01micko wrote:Here is the source code and package of the network_tray with icons on rightclick menu and the IP address shown in the tooltip.
Note the source is just the C code, You can use rerwin's original compile script to compile and generate .pot file.
Code: Select all
fgets(ipa,sizeof ipa,fp);
Code: Select all
if( fgets(ipa,sizeof ipa,fp)==NULL ) ipa[0]='\0';
Code: Select all
if (ipa==NULL) return 1;
Code: Select all
if (ipa!=NULL) {
strcat(infomsg,_("\nIP address: "));
strcat(infomsg,ipa);
}
Code: Select all
strcat(infomsg,_("\nIP address: "));
strcat(infomsg,ipa);
I was just curiuos what wait-disconnect were for, I agree it doesn't hurt to leave it butrerwin wrote: wait-disconnect issue I handle by changing the line, killall wait-disconnect, to avoid the warning message:I leave in the procedure itself in case anyone in the future needs it. It does not hurt to just leave it there.Code: Select all
[ "$(pidof wait-disconnect)" ] && killall wait-disconnect #140607
Hmmm maybe this is different in gtk2 and gtk3.rerwin wrote: -- I am concerned that the SSID field is now too narrow; please suggest how wide it should be, considering the longest SSID you have seen.
I just now tried slacko 5.7.0 and also see that the notifications are absent. The hook file, 99-notify, is not being executed. That is because it is not where slacko keeps its hook scripts. Move /lib/dhcpcd/dhcpcd-hooks/99-notify to /usr/libexec/dhcpcd-hooks/ or make a link to it there.peebee wrote:Status notifications seem to have stopped working with Frisbee as installed in Slacko5.7 (and now in Slacko6Beta)
Running frisbee from a terminal does not give any clues why.
Any ideas on how to investigate further please?
Thanks Richard - I'll make this change in my next LxPup version (14.07 maybe) unless Mick sees this and is able to make it at the Slacko6 level.rerwin wrote:I just now tried slacko 5.7.0 and also see that the notifications are absent. The hook file, 99-notify, is not being executed. That is because it is not where slacko keeps its hook scripts. Move /lib/dhcpcd/dhcpcd-hooks/99-notify to /usr/libexec/dhcpcd-hooks/ or make a link to it there.peebee wrote:Status notifications seem to have stopped working with Frisbee as installed in Slacko5.7 (and now in Slacko6Beta)
Running frisbee from a terminal does not give any clues why.
Any ideas on how to investigate further please?
R
Scooby and I have been working this issue over the past month. He is using dhcpcd version 6.3.2 with adapted dropwait modifications. There has been significant development of dhcpcd between 5.6.4 and 6.3.2, and now 6.4.0. For the 6.x series, timeout protection was added such that the delay performed to implement the dropwait function exceeds the timeout period when a connection is intentionally closed (wireless disabled). There does not appear to be a practical way around the 10-second timeout.Scooby wrote:If I had dropwait set to 0 and select right click menu of network_tray
"Disable wireless network" everything seems ok and I get no IP adress
with ifconfig
but
If I had dropwait set to 15 and select right click menu of network_tray
"Disable wireless network" IP adress does not disappear from
ifconfig output. But I cannot connect to internet via browser.
I tried with dhcpcd version 5.6.4 and it behaved correctly in both instances.
Code: Select all
grep 'lost temporarily' /var/log/messages
Maybe it could be upped to 20s so that dropwait can be 15s?There does not appear to be a practical way around the 10-second timeout.
Code: Select all
syslog(LOG_DEBUG, "%s: carrier briefly lost for %d seconds", ifname, i);
Code: Select all
#ifdef O_CLOEXEC
ctx.pid_fd = open(pidfile,
O_WRONLY | O_CREAT | O_CLOEXEC | O_NONBLOCK,
0664);
#else
ctx.pid_fd = open(pidfile,
O_WRONLY | O_CREAT | O_NONBLOCK,
0664);
#endif
I discovered that misbehavior, too, as I was experimenting. I will fix that in frisbee. Remember, I trusted that Jemimah knew what she was doing, so did not look for problems, but fixed issues that I or someone else found during usage of frisbee.But when I wanted to checkout dropwait setting
and then hit cancel the value returned to 0 (was 5)
In my head I was just cancelling wanting to change dropwait at all
so is this intended?
Yeah I think Jemimah was a great coder. If I sounded critical it was not my intentionrerwin wrote:Remember, I trusted that Jemimah knew what she was doing, so did not look for problems, but fixed issues that I or someone else found during usage of frisbee.