Re: Merge network manager with network monitor
On Wed, 2007-10-31 at 12:34 +0100, Filip Sedivy wrote: Hello all. I am sorry to post question this way. I was wondering if it is possible to merge somehow functionality of network monitor to network manager. It would be nice to see network traffic visually by flashing of the icon with 2 computers. I know that you can install the network monitor applet but I think this is something that network manager should do by itself. I am using Gnome on Ubuntu 7.10. I'd second that request. Not so much interested in watching traffic, but more the connection status. I've got a wireless connection which drops out from time to time, but often recovering before NM notices. Obviously I'd rather that didn't happen at all, but when it does, the network monitor applet shows pretty much instantly when the connection is out, and when it comes back. So I keep both of them on the panel. Having just one would be nice... Simon. signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BUG: NM only connects the third time
Hi Eric, Am Donnerstag, 1. November 2007 11:16:12 schrieb [EMAIL PROTECTED]: Hi, On my laptop, when I boot and login, I have no connection. I click on knetworkmanager's icon to select my wifi access point, I have the progress bar going up to 100% and the signal strength staircase icon appears. Looks good, but I don't actually have a connexion: after 4 or 5 seconds the icon updates back to no connexion. I click again on knetworkmanager's icon, and this time it works properly and I have my connexion. snip It looks that NM is able to communicate with knetworkmanager on boot, since it retrieves the correct AP name, but requesting the key makes an error. However, on the second try, it already has the key and doesn't issue a request, as if it managed to get it on the first try anyway. Weird. Why it fails on the second try is also mysterious. The dhcp server gives a lease of -1, meaning infinity. Maybe NM takes it litteraly, establishes the connection, realizes it is expired one second ago, and shut it down ? I don't know. Two other random pieces of information: knetworkmanager is configured to store the keys unencrypted in the config file rather than in kwallet. My log is full of the following message: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported which appears, approximatively, every 6 seconds. That's NetworkManager itself. Dan, Tambet? I have found on http://websvn.kde.org/branches/extragear/kde3/network/knetworkmanager that there exists a version 0.2.1 of knetworkmanager with, in the changelog: KNM 0.2.1 is not yet officially released. Avoid a race on the DBus which sometimes prevents connection to wireless networks but, I haven't been able to find a .rpm or a .tar.gz of that version. Should I try to install, understand and use the svn tools to recover that version ? Would it fix one or both of my problems ? Your connection-problem will be most likely fixed in KNM 0.2.1. Regards, Helmut ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BUG: NM only connects the third time
On Thu, Nov 01, 2007 at 11:51:55AM +0100, Helmut Schaa wrote: Hi Eric, Am Donnerstag, 1. November 2007 11:16:12 schrieb [EMAIL PROTECTED]: Hi, On my laptop, when I boot and login, I have no connection. I click on knetworkmanager's icon to select my wifi access point, I have the progress bar going up to 100% and the signal strength staircase icon appears. Looks good, but I don't actually have a connexion: after 4 or 5 seconds the icon updates back to no connexion. I click again on knetworkmanager's icon, and this time it works properly and I have my connexion. info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported which appears, approximatively, every 6 seconds. KNM 0.2.1 is not yet officially released. Your connection-problem will be most likely fixed in KNM 0.2.1. Hi ! Your message motivated me to try to compile knetworkmanager from svn. As you predicted, it solved my problem. Thanks a lot ! I wonder why fedora didn't push an update to fix that annoying bug. Quite unimportant, but by curiosity, what is the meaning of this message I get every 6 seconds that I was talking about, and is there a way to fix it ? 13:54:25 NetworkManager: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported 13:55:01 last message repeated 6 times 13:56:02 last message repeated 10 times 13:57:08 last message repeated 11 times 13:58:14 last message repeated 11 times 13:59:20 last message repeated 11 times 14:00:26 last message repeated 11 times 14:01:32 last message repeated 11 times 14:02:38 last message repeated 11 times 14:03:39 last message repeated 10 times 14:04:45 last message repeated 11 times 14:05:51 last message repeated 11 times 14:06:57 last message repeated 11 times 14:08:03 last message repeated 11 times 14:09:09 last message repeated 11 times 14:10:15 last message repeated 11 times Thanks again; Éric ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Merge network manager with network monitor
On Nov 1, 2007 12:13 PM, Simon Geard [EMAIL PROTECTED] wrote: I've got a wireless connection which drops out from time to time, but often recovering before NM notices. Obviously I'd rather that didn't happen at all, but when it does, the network monitor applet shows pretty much instantly when the connection is out, and when it comes back. So I keep both of them on the panel. Having just one would be nice... 0.6 branch is declared stable so it's unlikely it'll get new features. In 0.7 branch NM notifies the applet when anything changes (instead of applet polling NM in every X seconds), so there's no chance the applet would not notice it. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless DHCP overwrites DNS settings
On Wed, 2007-10-31 at 15:34 -0700, Sourav K. Mandal wrote: On Wed, 2007-10-31 at 17:07 -0500, Jason Martens wrote: On Wed, 2007-10-31 at 11:55 -0700, Sourav K. Mandal wrote: Perhaps this will help: http://gentoo-wiki.com/NetworkManager#Gnome_Specifics Was there something specific in there? I don't see anything on that page related to this problem. It describe a configuration file for dhclient so that NetworkManager doesn't change your hostname and break GNOME. Furthermore, if you read the manpage for dhclient.conf, you'll see ways to fix problems with the assignment of DNS servers. Ah, ok. My problem is that the DNS servers are overwritten, not that the hostname is changed. I don't think modifying dhclient.conf will help, because I *want* it to change my dns settings, except when I already have a VPN tunnel set up. Jason ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless DHCP overwrites DNS settings
On Wed, 2007-10-31 at 20:22 -0400, Darren Albers wrote: On 10/31/07, Jason Martens [EMAIL PROTECTED] wrote: I'm still having the problem where my DNS settings are overwritten by the wireless connection, even though I am still connected to the VPN. Attached is the syslog output. Note, I'm on Ubuntu Gutsy now, but I had the same problem on Debian Lenny about 2 weeks ago. Jason As Sourav pointed out setting your nameservers via the NetworkSettings tab will be overwritten by NM since the applications are not aware of each other. If you want to hardcode a DNS server you should do it in dhclient.conf I didn't change my nameservers. *Something* is changing them while I'm still connected to my VPN, which means that I can't access anything via DNS after about 15 minutes of being connected. I either have to disconnect the VPN, or manually change the resolv.conf back to the proper settings for my VPN connection (which will get overwritten again in 15 minutes). Annoying, to say the least. Jason ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BUG: NM only connects the third time
On Thu, 2007-11-01 at 14:12 +0100, [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 11:51:55AM +0100, Helmut Schaa wrote: Hi Eric, Am Donnerstag, 1. November 2007 11:16:12 schrieb [EMAIL PROTECTED]: Hi, On my laptop, when I boot and login, I have no connection. I click on knetworkmanager's icon to select my wifi access point, I have the progress bar going up to 100% and the signal strength staircase icon appears. Looks good, but I don't actually have a connexion: after 4 or 5 seconds the icon updates back to no connexion. I click again on knetworkmanager's icon, and this time it works properly and I have my connexion. info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported which appears, approximatively, every 6 seconds. KNM 0.2.1 is not yet officially released. Your connection-problem will be most likely fixed in KNM 0.2.1. Hi ! Your message motivated me to try to compile knetworkmanager from svn. As you predicted, it solved my problem. Thanks a lot ! I wonder why fedora didn't push an update to fix that annoying bug. Which Fedora version? F7 or F8? Quite unimportant, but by curiosity, what is the meaning of this message I get every 6 seconds that I was talking about, and is there a way to fix it ? What hardware do you have? You may need to ensure that the dcdbas kernel module is installed for Dell laptops, and that you have dellWirelessCtl. This message means that HAL has an rfkill item for your laptop, but the error says that something is going wrong when querying that killswitch. What version (and RPM release #) of HAL do you have? Dan 13:54:25 NetworkManager: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported 13:55:01 last message repeated 6 times 13:56:02 last message repeated 10 times 13:57:08 last message repeated 11 times 13:58:14 last message repeated 11 times 13:59:20 last message repeated 11 times 14:00:26 last message repeated 11 times 14:01:32 last message repeated 11 times 14:02:38 last message repeated 11 times 14:03:39 last message repeated 10 times 14:04:45 last message repeated 11 times 14:05:51 last message repeated 11 times 14:06:57 last message repeated 11 times 14:08:03 last message repeated 11 times 14:09:09 last message repeated 11 times 14:10:15 last message repeated 11 times Thanks again; Éric ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BUG: NM only connects the third time
On Thu, Nov 01, 2007 at 04:16:16PM -0400, Dan Williams wrote: Your message motivated me to try to compile knetworkmanager from svn. As you predicted, it solved my problem. Thanks a lot ! I wonder why fedora didn't push an update to fix that annoying bug. Which Fedora version? F7 or F8? That's a Fedora 7, with a knetworkmanager from svn20070815, while the bug has been fixed (I think) on 20070827: 2007-08-27 07:30 Helmut Schaa [EMAIL PROTECTED] * src/knetworkmanager-nminfo.cpp: Avoid a race on the DBus which sometimes prevents connection to wireless networks What hardware do you have? You may need to ensure that the dcdbas kernel module is installed for Dell laptops, and that you have dellWirelessCtl. This message means that HAL has an rfkill item for your laptop, but the error says that something is going wrong when querying that killswitch. What version (and RPM release #) of HAL do you have? That was it; I have a dell, but didn't know about dcdbas or libsmbiosi (and the error message didn't help...) Thanks for the info ! Éric ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BUG: NM only connects the third time
On Thu, 2007-11-01 at 21:59 +0100, [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 04:16:16PM -0400, Dan Williams wrote: Your message motivated me to try to compile knetworkmanager from svn. As you predicted, it solved my problem. Thanks a lot ! I wonder why fedora didn't push an update to fix that annoying bug. Which Fedora version? F7 or F8? That's a Fedora 7, with a knetworkmanager from svn20070815, while the bug has been fixed (I think) on 20070827: 2007-08-27 07:30 Helmut Schaa [EMAIL PROTECTED] * src/knetworkmanager-nminfo.cpp: Avoid a race on the DBus which sometimes prevents connection to wireless networks You might want to file a bug against knetworkmanager in Fedora bugzilla to alert the maintainer to the fix so that he/she can package it up and push it out. What hardware do you have? You may need to ensure that the dcdbas kernel module is installed for Dell laptops, and that you have dellWirelessCtl. This message means that HAL has an rfkill item for your laptop, but the error says that something is going wrong when querying that killswitch. What version (and RPM release #) of HAL do you have? That was it; I have a dell, but didn't know about dcdbas or libsmbiosi (and the error message didn't help...) Thanks for the info ! Upstream libsmbios just figured out how to get the module to autoload, so hopefully that will get pushed into a new Fedora kernel at some point and obsolete any hacks people have. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
cannot connect to VPN through wireless
Hello everyone, I recently installed Ubuntu 7.10 which comes with network-manager. As I had done before in Ubuntu 7.04, I went ahead and set up a VPN connection to Relakks.com. Now I have noticed that when I am connected through wireless on my laptop, I cannot connect to the VPN connection, I get a message that the VPN connection failed. I can connect to VPN fine in wired mode however. I launched NM through the terminal, but found no error messages. From /var/log/syslog: Oct 31 22:46:58 ubuntu NetworkManager: nm_vpn_service_process_signal(): VPN failed for service 'org.freedesktop.NetworkManager.ppp_starter', signal 'ConnectFailed', with message 'VPN Connection failed'. Oct 31 22:46:58 ubuntu NetworkManager: VPN service 'org.freedesktop.NetworkManager.ppp_starter' signaled state change 3 - 5. Oct 31 22:46:58 ubuntu NetworkManager: VPN service 'org.freedesktop.NetworkManager.ppp_starter' signaled state change 5 - 6. Oct 31 22:46:58 ubuntu NetworkManager: nm_vpn_service_stop_connection(): (VPN Service org.freedesktop.NetworkManager.ppp_starter): could not stop connection 'Relakks' because service was 6. Oct 31 22:46:58 ubuntu pptp[6190]: anon log[callmgr_main:pptp_callmgr.c:255]: Closing connection (shutdown) Oct 31 22:46:58 ubuntu pptp[6190]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Oct 31 22:46:58 ubuntu pptp[6190]: anon log[call_callback:pptp_callmgr.c:78]: Closing connection (call state) Oct 31 22:46:59 ubuntu pppd[6185]: Modem hangup Oct 31 22:46:59 ubuntu pppd[6185]: Connection terminated. Oct 31 22:46:59 ubuntu pppd[6185]: Child process /usr/sbin/pptp 83.233.183.2 –nolaunchpppd (pid 6186) terminated with signal 15 Oct 31 22:46:59 ubuntu pppd[6185]: Exit. Has anyone experienced this? Any ideas? Thank you. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: has anyone had a chance to look at my nm-applet patch?
On Thu, 2007-11-01 at 23:17 +1300, Simon Geard wrote: On Wed, 2007-10-31 at 10:59 -0400, Katelin Ganzer wrote: On 10/31/07, Simon Geard [EMAIL PROTECTED] wrote: Good idea, but it doesn't compile on my system, unable to find the function gtk_widget_set_tooltip_markup(). I think that's something new to gtk+ 2.12? I'm running 2.10.14... Oh. How do I make it work with gtk 2.10? It seems that all of the tooltip APIs are from 2.12? No idea, sorry - I'm not a gtk+ coder. I understand a lot of work was done on providing good tooltip APIs in 2.12 - I assume the same effect could be done on previous versions, but might not be quite so easy. It's not anywhere near as elegant - see http://library.gnome.org/devel/gtk/2.10/GtkTooltips.html for the older API. btw, looking at the patch, the markup_encode function is unnecessary, just use g_markup_escape_text(): http://library.gnome.org/devel/glib/stable/glib-Simple-XML-Subset-Parser.html#id2955983 Ed ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: has anyone had a chance to look at my nm-applet patch?
On 10/28/07, Darren Albers [EMAIL PROTECTED] wrote: I am not a dev but my first thought was Great idea but then I realized that it is probably way too much info for the user. In /most/ cases the user will see a large number of AP's and will pick the one with the best signal and this is what NM does now automatically. I think it only confuses the issue for the user to see all the different channels. I quickly am tiring of this attitude, as it finds expression in the gnome desktop. Far too much is assumed, far too little is tested (ie usability and user reaction) and the default impulse seems always to be limit choice. In /MOST/ situations, I want and need to see what wireless networks are around and available. /occasionally/ there might be /too many/ for the interface. So, it would be good to: 1)offer the choice/ability to see all and 2)offer the ability to scroll the presentation to show more than a page-view snip Maybe it would be better to make this an option that can be enabled by changing a gconf value for advanced users who want to see this information but otherwise leave it disabled? Out of curiosity how do other OS's deal with this? no maybe about it. But -- the choice should be in the NM interface itself. Choice must be a/the priority. Always. I love the idea of the patch and I always like seeing more information so if I had an option I would personally enable this feature but I don't think it should be the default. To gnome devs, from a fan: Please do not assume the average or default user is dumb, or somehow less capable than you. Please do assume that there are a range of abilities, and try to design an interface that meets the needs of the broadest range possible. Peter -- Those who can make you believe absurdities can make you commit atrocities -- Voltaire www.the-brights.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: has anyone had a chance to look at my nm-applet patch?
On 11/1/07, Peter Van Lone [EMAIL PROTECTED] wrote: On 10/28/07, Darren Albers [EMAIL PROTECTED] wrote: I am not a dev but my first thought was Great idea but then I realized that it is probably way too much info for the user. In /most/ cases the user will see a large number of AP's and will pick the one with the best signal and this is what NM does now automatically. I think it only confuses the issue for the user to see all the different channels. I quickly am tiring of this attitude, as it finds expression in the gnome desktop. Far too much is assumed, far too little is tested (ie usability and user reaction) and the default impulse seems always to be limit choice. In /MOST/ situations, I want and need to see what wireless networks are around and available. /occasionally/ there might be /too many/ for the interface. So, it would be good to: 1)offer the choice/ability to see all and 2)offer the ability to scroll the presentation to show more than a page-view snip Maybe it would be better to make this an option that can be enabled by changing a gconf value for advanced users who want to see this information but otherwise leave it disabled? Out of curiosity how do other OS's deal with this? no maybe about it. But -- the choice should be in the NM interface itself. Choice must be a/the priority. Always. I love the idea of the patch and I always like seeing more information so if I had an option I would personally enable this feature but I don't think it should be the default. To gnome devs, from a fan: Please do not assume the average or default user is dumb, or somehow less capable than you. Please do assume that there are a range of abilities, and try to design an interface that meets the needs of the broadest range possible. First of all I am not a Dev so if you are upset at my comment do not reference the devs but to me. I don't want their hard work being diminished by me ;-). I don't think you read what I wrote other than the first part. I did not just say The user is dumb so we should hide this I setup use cases and evaluated the possible options for this. I appreciate where you are coming from but this was not the situation here, my statement was not that the patch wasn't needed but that it shouldn't be the default view. It seems like we agree on this and even for the same reason Katelin's tooltip solution is a great way to handle it since (imo) exposing the channel information in the first view for every AP is just unnecessary. In /most/ cases the channel is unnecessary so it should be available but not the default view. If I used this patch at work without the tooltip option I would see 18 SSID's plus all the busted windows machines that broadcast out the last SSID they connected to! (We usually have 3 AP's for full coverage in every area with 6 SSID's each for various purposes.) My argument was not against the feature but that it should be implemented sanely. This is not a knock on Katelin in any way, people like this who see a problem and provide a solution are the ones who make the open-source movement great. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM looses connection and/or doesn't use dhcp
I have started to have some problems with networkmanager lately. I am running version 0.6.5_p20070823. First thing: when I come home from work where I was connected using a static IP (at work I stop NM, set the static IP, then on reboot the PC goes back to it's dhcp settings) for some odd reason NM keeps setting my work IP and doesn't renew the IP for my home network. This is a recent occurrence and I can't figure out why it started doing it. Secondly, at random times I will loose my connection. The IP is still there but I think NM messes up the default route info. Restarting NM fixes it or simply setting the default route manually does it. Why is it doing this? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM looses connection and/or doesn't use dhcp
On Thu, 2007-11-01 at 18:58 -0700, Xamindar wrote: I have started to have some problems with networkmanager lately. I am running version 0.6.5_p20070823. From the version number it looks like you are running Gentoo. Have you updated baselayout recently? If so, perhaps you overwrote your /etc/conf.d/rc, which has to have net scripts disabled so as not to conflict with NM. Look here: http://gentoo-wiki.com/NetworkManager#Clean_up_your_old_network_settings First thing: when I come home from work where I was connected using a static IP (at work I stop NM, set the static IP, then on reboot the PC goes back to it's dhcp settings) for some odd reason NM keeps setting my work IP and doesn't renew the IP for my home network. This is a recent occurrence and I can't figure out why it started doing it. WLAN devices store the last IP address. Indeed, NM is supposed to overwrite it when you select your home AP. Secondly, at random times I will loose my connection. The IP is still there but I think NM messes up the default route info. Restarting NM fixes it or simply setting the default route manually does it. Why is it doing this? This is why I think it may be a Gentoo problem -- RC service plugging may be undoing what NM's setting. Sourav ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
