Argolance & other testers,
Note that I uploaded another version of the network_tray package on page 11. It has "integrated" icons and a script to switch between analog and wireless dialup icons.
Richard

Argolance & other testers,
Note that I uploaded another version of the network_tray package on page 11. It has "integrated" icons and a script to switch between analog and wireless dialup icons.
Richard

In a previous post, I asked you if it would be possible to give the preference to a wireless network when several available?

Quote:

The preference seems like something I can try to add to frisbee.

As simple user, I really think it is important: every time I start my laptop (this may happen several times a day, because of tests I am doing with!) Frisbee automatically connect to an available public network. The tray icon let me think all is ok but while running "Seamonkey", for example, I am immediately redirected to an inscription web page to create an account to use this public network (... and some Windoze user at home to promptly say "aahhh, LINUX is crappy"!)! Then I close Seamonkey, run Frisbee to get a connection to my private network, and so on...
Frisbee is a little bit more convenient for setting/configuring a wireless network than the Dougal's GUI, but this one has not this inconvenience...

Argolance,
I have been researching this and now understand (I think) how the choice is made about connecting to a network. When there are no network profiles saved, the networks found are given priority 0. When a profile is saved, it is given a priority greater than zero and greater than any already saved. Only when multiple networks of the same (0) priority are discovered are the strength values considered -- but only for those of the same priority. So there are several ways to control the automatic choice of network.

1. Save profiles for only those networks you want to connect to, leaving the others at priority 0.

2. If the less desired network is already in a saved profile, delete that profile.

3. If you sometimes need the "stronger" public network, save its profile before saving the preferred network's profile.

4. Adjust the relative priorities of the profiles so that the preferred networks have a higher (greater value) priority than the competitors in the same geographic area.

If none of these work for you, please PM me a pdiag file from frisbee's Diagnose dialog. If they work, maybe we should mention the priority scheme in a tool-tip or elsewhere. Thanks for your concern about this issue.
Richard

Yes, but I have already found a bug, common to rerwin's version and my fork. The icon for ethernet via frisbee doesn't "blink", that is it doesn't reflect tx and rx status. Consequently, tx and rx stats are not recorded.

The icon for mobile-dialup does blink, but it doesn't record the tx/rx/stats.

I'll post source for mine shortly in the linked thread by peebee. By shortly, I mean when I fix the bug! I do have the IP address working for LAN and PPP now. (Reflected in pop up message with the rx/tx stats).

EDIT:

Richard,

About the above bug report, there is misinformation.

The bug is in frisbee code itself, not the tray. icon.What happens is that I have 2 ethernet interfaces (yes I know this isn't common but it's still a bug). When I connect with SNS or Network Wizard on the seconf interface (eth1) all works as expected and I get blinking icons.

In frisbee, if I connect to eth1 then my icon fails to blink. eth0 is reported by the splash messages as "down" but if you do cat /sys/class/net/eth0/dormant it returns 0 indicating it is still up. The icon is then getting it's values from /sys/class/net/eth0 for eth1, but they don't change meaning that the icon fails to blink and the rx/tx values are wrong.

Yes, the Huawei E3131 is switched by usbmodeswitch into a NIC -- VendorID=12d1 ProductID=14db KERNEL-MODULE=cdc_ether. Both SNS and Frisbee say it is of type 'wired'! It also worked in the previous release of PP. Apparently it can be switched to a dial-up modem instead but then you have the usual blanks to fill -- APN, init and dial strings etc.

I was too hasty. Interface swapping is fixed in PP5.4.92. While flayling around I blocked UDP on my firewall. It is broken in the previous PP.

Breaking the click action of the tray applet occured in the previous PP after using Dougle's NetWiz.

Suggestion: If Frisbee is installed then the event manager splash needs to be changed or removed.

The network menu now has only 2 items 'setup networking' and 'network status information'.

The icon for ethernet via frisbee doesn't "blink", that is it doesn't reflect tx and rx status. Consequently, tx and rx stats are not recorded.

The icon for mobile-dialup does blink, but it doesn't record the tx/rx/stats.

The bug is in frisbee code itself, not the tray. icon.What happens is that I have 2 ethernet interfaces (yes I know this isn't common but it's still a bug). When I connect with SNS or Network Wizard on the seconf interface (eth1) all works as expected and I get blinking icons.

In frisbee, if I connect to eth1 then my icon fails to blink. eth0 is reported by the splash messages as "down" but if you do cat /sys/class/net/eth0/dormant it returns 0 indicating it is still up. The icon is then getting it's values from /sys/class/net/eth0 for eth1, but they don't change meaning that the icon fails to blink and the rx/tx values are wrong.

Thanks for pursuing these issues.

I have seen similar misbehavior on my PC with a NIC and wifi connection. With no networks to connect to, the wifi (wlan0) is declared "down" and the ethernet icon does not blink. After examining the network_tray code (as part of integrating the frisbee part), I concluded that it was written on the assumption that there is only one active networking connection. Therefore, the last interface found (eth0, wlan0, ppp0) is what is used to determine the byte traffic. Assuming that my eth0 is detected before wlan0 (alphabetically), only the traffic info for the "down" wlan0 is used to select the icon. The eth0 info got processed, but was overlaid by the wlan0 traffic info. At least, that is how I explained it to myself.

I tried to live with that constraint, but am sure there is inaccuracy introduced by the above behavior. Reworking network_tray to correctly handle multiple active connections is much more complicated than I was ready to tackle, in the interest of getting frisbee, such as it is, integrated. Now that that is done, we can focus on making it and network_tray work better. I do intend to get back to them, but first things first.

About the traffic measurements: There is only one accumulator for the monthly totals, so that it is not clear, to me, what that total includes -- the traffic on all connections? Just one of several?

I think the intent for the monthly value is for connections with a monthly limit on byte traffic. It seems to me that that would most likely apply to wireless dialup accounts, but maybe there are other cases. When Barry added that feature, I mimicked it for dialup accounts but did not attempt to add that to network_tray (way beyond me, at that time). As we tighten up network_tray, we can add that. The monthly totals for dialup are kept in /var/local/pupdial/isp, which is a link to one of the two possible dialup accounts. Those totals should be used for dialup, instead if those in /var/local/sns. But that implementation does not take into account connections made through "Wireless GPRS modem" connections.

Regarding the up/down splashes: they are probably produced when dhcpcd starts or stops for a particular link. The up/down states are signaled to network_tray for wireless and ethernet and are completely independent of the device status as indicated by /sys/class/net/... Multiple wireless or ethernet interfaces will confuse network_tray because only a single indicator is kept for each interface type. I am considering using the /sys/class/net/... information for up/down state, similar to how the dialup is handled and using the presence of a /sys/class/net/*/wireless directory as the indicator of a wireless (wifi) link. Then, I need to rethink how to use the dhcpcd up/down indications.

I am very interested in your effort to correct the stats and icon blinking, but suspect you will find it more complicated than you expected. I think this would be a significant task.

On another subject: irishrm and I are seeing timeout disconnects not seen in the older Frisbees. I expect they are related to the "beta4" change in how frisbee connects through wpa_supplicant. I think Jemimah's intent was to improve handling of multiple access points for the same network. But maybe wpa_supplicant is not handling everything correctly. I am hoping that the 1.0 version you use will correct the problem. Is there any reason why we should not request that 1.0 or even 1.1 be added to the puppy repo as an alternative, other that that they are huge compared to the 0.7.3 version in puppy?
Richard

EDIT a few minutes later: Irishrm informs me that running frisbee on the slacko beta (with wpa_supplicant-1.0) does not solve the problem. I wonder if the replacement for the deprecated wext driver (nl80211?) would fix it. That is a whole new world to get into -- not something I could handle. Oh my.

zygo wrote:

Breaking the click action of the tray applet occured in the previous PP after using Dougle's NetWiz.

Suggestion: If Frisbee is installed then the event manager splash needs to be changed or removed.

The network menu now has only 2 items 'setup networking' and 'network status information'.

... is that I have 2 ethernet interfaces (yes I know this isn't common but it's still a bug). When I connect with SNS or Network Wizard on the seconf interface (eth1) all works as expected and I get blinking icons. ...

I have similar configuration issue as reported by 01Micko. Seem confused in understanding that there are occasion when a user would have 2 LAN cards for any various reasons. It seems to surface when eth1 is the primary (LAN) connection when either eth0 is unplugged or the router/switch is turned off.

Kirk fixed/addressed this issue in FATDOG5.1 but ever so often he forgets and has to go back to resolve when moving from release to release. This suggest that the approach requires momentary thought.

Here to help._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Of course this only works on X-restart/reboot but like I said, for the sake of getting it working.

Also, I'm sure you are aware I have to adjust frisbee each time for slacko as the dhcpcd hooks are in a different path. (/usr/libexec/dhcpcd-hooks). This is a slackware anomaly which I believe will be adjusted in the future as 64 bit slackware uses the same dhcpcd-hooks path as debian/ubuntu.

Of course this only works on X-restart/reboot but like I said, for the sake of getting it working.

The signal_mode flag is set by initialization script 'frisbee' before it does anything else. That should occur even before network_tray_modeset runs. The flag is set if a particular icon is present that appears only in network_tray-2.6. The telltale icon is networkdead-eth.xpm. You probably changed its name to end in .svg, so it looks like network_tray cannot handle signals. I have changed the test to be for networkdead-eth*.*, so it will work with any flavor of icon (or link) of that name. It is in version 20130227, here:
http://murga-linux.com/puppy/viewtopic.php?p=684092#684092

However, that logic was added only because of the possibility that network_tray-2.5 would remain the official version while 2.6 (by some name/version) would be a user/developer option. If 2.6 continues to be the official version after release of precise 5.5, we might consider removing that flag altogether, if we don't need to consider n_t-2.5.

The signal_mode flag is set by initialization script 'frisbee' before it does anything else. That should occur even before network_tray_modeset runs. The flag is set if a particular icon is present that appears only in network_tray-2.6. The telltale icon is networkdead-eth.xpm. You probably changed its name to end in .svg, so it looks like network_tray cannot handle signals. I have changed the test to be for networkdead-eth*.*, so it will work with any flavor of icon (or link) of that name. It is in version 20130227, here:
http://murga-linux.com/puppy/viewtopic.php?p=684092#684092

However, that logic was added only because of the possibility that network_tray-2.5 would remain the official version while 2.6 (by some name/version) would be a user/developer option. If 2.6 continues to be the official version after release of precise 5.5, we might consider removing that flag altogether, if we don't need to consider n_t-2.5.

My bad

To address the other concern what about this mod to the pinstall.sh? (the path to hooks for slacko)

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