vpnc connection terminates the first time
Hi, I think I've fixed this in CVS, oddly enough, by adding a sleep(1); before trying to read the vpnc pidfile. It seems that 0.3.3 doesn't write the pid file as early as 0.3.2 did. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM scanning policy
On Wed, 2005-05-25 at 10:19 -0400, Bill Moss wrote: Proposed change to NM scanning policy. Context menu scan item: three states -- On, Auto, Off On: NM's current policy which is to always scan but adjust the time between scans. Auto (default): When a wired connection has been established, stop scanning (also consider powering down radio). As soon as a wired connection is not available, begin scanning. After a wireless connection has been made, stop scanning but start again if the signal strength falls below a threshold. Off: Do not scan or stop all wireless devices and power down radios. Justification: Scanning powers up the radio. When operationg on battery and connected by wire, scanning wastes power. Scans that take a long time can be disruptive. I think this is a good idea and I'll do it, if nobody submits a patch for it first. I'm thinking of adding a menu to the applet's right-click menu called Wireless Scanning, which would have the items On, Auto, Off. This would be a preference stored in GConf and would persist across reboots and logins. The Wireless Scanning submenu would replace the existing Pause Wireless Scanning item. Unfortunately at the moment, I'm not sure we can power down the card, NM kind of assumes that devices are always going to be up. But we can certainly do that a bit later. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Atheros abg / madwifi + wep / dropouts due to scanning
On Wed, 2005-05-25 at 00:11 -0400, Derek Atkins wrote: Dan, On 31 Jan 2005 you said: I think we can address your problem by having the card scan less often (and even less often if its an a/b/g card). (see : http://www.mail-archive.com/networkmanager-list@gnome.org/msg00090.html ) I'm definitely seeing this myself now that I'm home. I wasn't really noticing it at the office (which didn't use WEP) but I definitely see it at home (where I DO use WEP). In particular I'm seeing a 9 second dropout every minute. This makes many network connections REALLY HARD to use. Personally, I'd rather NM not scan at all if it's connected to an AP unless I signal a sleep/wakeup manually, or if the AP goes away. Why scan if it's happily connected? Especially when it introduces network dropouts like this? Is there some configuration I can make to turn off scanning, or make it scan every 15 minutes or something that wont hit me constantly? I'm using STABLE_0_3 as of a few days ago. Derek, See Bill's post on wireless scanning policy and my reply to it. That should fix most of your issues. I'll do the patch for both 0.3 and 0.4. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
