newbie question on svn release version
Hi All, I am using NetworkManager version - svnr2984-r8. Could anybody please tell me which official version can it be mapped to? I mean is it 0.6.* or is it a 0.7.* release. I could not find the release notes for the NM releases - like 0.6, 0.7 etc. Thanks Regards, Saurav ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
remove gnome-keyring
Hi all, I want to remove the gnome-keyring. A little annoying when connect WIFI. Except hack in NetworkManager. Have any other methods? Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
using nm-system-settings for the user settings
Hi, in NM clients, such as the GUI applets and the CLI of yours truly, a fair amount of code deals with the connection settings. I got the idea that the current nm-system-settings service could be generalized to deal with the *user* settings too, so that one program could run as two processes serving the two services. That way the client code would be factored out in the separate settings service. One could then even use the same connections from different applets, unlike now when they are stored in KDE and GNOME specific stores. I started coding it, registering nm-system-settings at NetworkManagerUserSettings, wanting to continue with the config file location and PolicyKit restrictions. Dan, Tambet told me that you intend to merge nm-system-settings into NM itself. I am afraid that it goes in pretty much the opposite direction than I would need. Could you share some details and reasons for the merge so that we can try to make the ideas work out together? -- Martin Vidner http://vidner.net/martin/software/cnetworkmanager/ Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Trouble waking from sleep
On Monday 11 May 2009, Dan Williams wrote: On Fri, 2009-05-08 at 18:47 -0400, Neal Becker wrote: NetworkManager-0.7.0.99-5.git20090326.fc10.x86_64 After being connected to wired enet, going to sleep, and waking without wired enet, results are random. Sometimes wlan is connected seemlessly, other times not. What wifi? After resume, are there APs in the menu? Dan In those cases restarting NetworkManager does not fix anything. Logging out/in always fixes it. Actually, it doesn't work correctly even on wired lan. I just tried with NetworkManager-0.7.1-1.fc10.x86_64 kde-plasma-networkmanagement-0.1-0.11.20090504svn.fc10.x86_64 When it woke, only loopback IF was configured. In this case, restarting NM did fix it. Looking at log, it is clear what the problem is. There are no messages from NM from the time of wakeup until I restarted it! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
VPN connections in NetworkManager have strange behaviour
Hello I have a problem when using NetworkManager to connect to VPN connections, on an up to date fedora 11 system. Packages versions are : NetworkManager-gnome-0.7.1-4.git20090414.fc11.i586 NetworkManager-vpnc-0.7.0.99-1.fc11.i586 NetworkManager-0.7.1-4.git20090414.fc11.i586 NetworkManager-openvpn-0.7.0.99-1.fc11.i586 NetworkManager-pptp-0.7.0.99-1.fc11.i586 NetworkManager-glib-0.7.1-4.git20090414.fc11.i586 NetworkManager-glib-devel-0.7.1-4.git20090414.fc11.i586 NetworkManager-devel-0.7.1-4.git20090414.fc11.i586 I previously (ubuntu gutsy) used to connect to a vpnc (VPN Compatible Cisco) server with the command line tool. Using the command line still works with Fedora 11. When I try to switch to the NetworkManager builtin VPN manager, I manage to connect to the remote VPN server, but no network activity can be made. It s maybe a problem with the routes. When connecting to the VPN with the vpnc command line tool, no specific configuration (but the group user login/password) is defined. No specific routing configuration has been made. 192.168.246.254 is the gateway of the LAN. 62.39.X.X is the remote VPN server. [r...@axel-asus axel]# LANG=C netstat -ren Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 62.39.X.X 192.168.246.254 255.255.255.255 UGH 0 00 eth0 192.168.246.0 0.0.0.0 255.255.255.0 U 1 00 eth0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 00 virbr0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tun0 The tun0 adapter address becomes 10.240.200.10/255.255.255.255 I manage to access to remote hosts (10.240.0.0/16 range). In other words, out-of-the-box vpnc tool works well. When connecting with the NetworkManager, the routing table is different : [r...@axel-asus axel]# LANG=C netstat -ren Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 62.39.X.X 192.168.246.254 255.255.255.255 UGH 0 00 eth0 192.168.246.0 0.0.0.0 255.255.255.0 U 1 00 eth0 10.240.200.00.0.0.0 255.255.255.0 U 0 00 tun0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 00 virbr0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 tun0 And the netmask of the tun0 adapter is different too : 10.240.200.10/255.255.255.0 And I cannot access 10.240.0.0/16 hosts. ignore the routes option is unchecked, only use the connection for same network resource option is unchecked, both in IPv4 Settings tab, Routes button. I tried to check them, both, and only one, without successful result, though the routing table is different for each setting. So is there something wrong in my NetworkManager settings ? I d like to track down this problem, but I don't know from where to start. Thanks for your help. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm 0.7.1 3g regression
Gour == Gour ggd...@gmail.com writes: Dan == Dan Williams d...@redhat.com writes: Dan HAL property. You have two options: Dan 2) Or, install the attached file to Dan /usr/share/hal/fdi/information/10freedesktop/01-deprecated-keys.fdi Gour For now, I went with the 2nd one... Dan That should make things work again. Gour It seems there is some progress, but I'm still writing this post Gour using hsoconnect :-/ Just to inform the list that I solved my problem... Browsing the forums at http://pharscape.org/ led me to the following link: https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/368325/ where the workaround for my 3g modem is mentioned, i.e. since there is no use of username and password (only PIN APN) with my mobile ISP, after putting some dummy values in, NM is connecting nicely now - I'm writing this reply via NM-manged connection :-D However, it would be nice if NM could manage it without dummy values as well. ;) Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgpT6aXb377dP.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How do I setup a gsm internet connection in Network Manager using a mobile phone (via USB Data Cable or Bluetooth) ?
Hi all, I would like to know how do I setup an internet connection in Network Manager via a GSM/CDMA mobile phone connected to the system via a USB Data Cable ot bluetooth. Thanks, Regards, rtnpro | Ratnadeep Debnath ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Trouble waking from sleep
On Thu, 2009-05-14 at 16:25 +0200, Christopher Lang wrote: Hi, I am seeing a similar behavior with NM (or dbus) in general, regardless of the type of network being used: Under Ubuntu 8.10: In the file: /usr/lib/pm-utils/sleep.d/10NetworkManager a signal is sent to NM via dbus when the PC wants to go to sleep. I can see, that this signal is properly delivered to NM, when going to suspend. However, when coming back from suspend, although the log in /var/log/pm-suspend.log clearly shows that the 10NM... script was executed properly no wake signal is delivered to NM via dbus (at least not always). This is strange, because one would assume that after comming back from suspend dbus is up and operational immediately; here in this case it looks that the dbus-send in 10NM... is not always going through to NM in the case of resume. I belive in these cases when NM is not waking up properly it is necessary to debug signal delivery to NM from the 10NetworkManager script via dbus-send. Guys, do some searching on the list. This problem has been covered over and over again. The problem is a bug in dbus where the bus ignores messages from very short-lived processes. If the process (liek dbus-send) exits before dbus has had a chance to process the message, there's a chance the message gets dropped. That's why --print-reply works; it forces the dbus-send to stick around longer, and the sleep/wake to NM doesn't get dropped. NM prints out messages when it gets sleep/wake calls, and it will dump them to syslog. If you don't see waking up... from NM, then NM didn't get the signal. Dan Does NM provide some log where we can see the delivery of sleep and wake (or Sleep(s) with new API) as debug output from NM? That would come in handy. thanks Chris http://www.acurana.de/ On Thursday 14 May 2009 15:28:01 Neal Becker wrote: On Monday 11 May 2009, Dan Williams wrote: On Fri, 2009-05-08 at 18:47 -0400, Neal Becker wrote: NetworkManager-0.7.0.99-5.git20090326.fc10.x86_64 After being connected to wired enet, going to sleep, and waking without wired enet, results are random. Sometimes wlan is connected seemlessly, other times not. What wifi? After resume, are there APs in the menu? Dan In those cases restarting NetworkManager does not fix anything. Logging out/in always fixes it. Actually, it doesn't work correctly even on wired lan. I just tried with NetworkManager-0.7.1-1.fc10.x86_64 kde-plasma-networkmanagement-0.1-0.11.20090504svn.fc10.x86_64 When it woke, only loopback IF was configured. In this case, restarting NM did fix it. Looking at log, it is clear what the problem is. There are no messages from NM from the time of wakeup until I restarted it! ___ 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Trouble waking from sleep
On Thu, 2009-05-14 at 15:01 -0400, Dan Williams wrote: On Thu, 2009-05-14 at 16:25 +0200, Christopher Lang wrote: Hi, I am seeing a similar behavior with NM (or dbus) in general, regardless of the type of network being used: Under Ubuntu 8.10: In the file: /usr/lib/pm-utils/sleep.d/10NetworkManager a signal is sent to NM via dbus when the PC wants to go to sleep. I can see, that this signal is properly delivered to NM, when going to suspend. However, when coming back from suspend, although the log in /var/log/pm-suspend.log clearly shows that the 10NM... script was executed properly no wake signal is delivered to NM via dbus (at least not always). This is strange, because one would assume that after comming back from suspend dbus is up and operational immediately; here in this case it looks that the dbus-send in 10NM... is not always going through to NM in the case of resume. I belive in these cases when NM is not waking up properly it is necessary to debug signal delivery to NM from the 10NetworkManager script via dbus-send. Guys, do some searching on the list. This problem has been covered over and over again. As in: Wireless is disabled message (May 11 2009) nm-applet loosing state (May 8 2009) Network disabled after suspend/resume - sometimes (Jan 7 2009) https://bugzilla.redhat.com/show_bug.cgi?id=477964 The problem is a bug in dbus where the bus ignores messages from very short-lived processes. If the process (liek dbus-send) exits before dbus has had a chance to process the message, there's a chance the message gets dropped. That's why --print-reply works; it forces the dbus-send to stick around longer, and the sleep/wake to NM doesn't get dropped. NM prints out messages when it gets sleep/wake calls, and it will dump them to syslog. If you don't see waking up... from NM, then NM didn't get the signal. Dan Does NM provide some log where we can see the delivery of sleep and wake (or Sleep(s) with new API) as debug output from NM? That would come in handy. thanks Chris http://www.acurana.de/ On Thursday 14 May 2009 15:28:01 Neal Becker wrote: On Monday 11 May 2009, Dan Williams wrote: On Fri, 2009-05-08 at 18:47 -0400, Neal Becker wrote: NetworkManager-0.7.0.99-5.git20090326.fc10.x86_64 After being connected to wired enet, going to sleep, and waking without wired enet, results are random. Sometimes wlan is connected seemlessly, other times not. What wifi? After resume, are there APs in the menu? Dan In those cases restarting NetworkManager does not fix anything. Logging out/in always fixes it. Actually, it doesn't work correctly even on wired lan. I just tried with NetworkManager-0.7.1-1.fc10.x86_64 kde-plasma-networkmanagement-0.1-0.11.20090504svn.fc10.x86_64 When it woke, only loopback IF was configured. In this case, restarting NM did fix it. Looking at log, it is clear what the problem is. There are no messages from NM from the time of wakeup until I restarted it! ___ 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 ___ 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: remove gnome-keyring
On Thu, 2009-05-14 at 16:49 +0800, 代尔欣 wrote: Hi all, I want to remove the gnome-keyring. A little annoying when connect WIFI. Except hack in NetworkManager. Have any other methods? The gnome applet uses the keyring pretty extensively. There's nothing in NetworkManager itself that uses the keyring. If not the keyring, something else needs to store the wifi secrets and passwords securely. To me, the best approach is to ensure the keyring is working properly (ie, unlocked at login and unlocked on resume from suspend) instead of disabling it entirely. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: newbie question on svn release version
On Thu, 2009-05-14 at 12:46 +0530, saurav barik wrote: Hi All, I am using NetworkManager version - svnr2984-r8. Could anybody please tell me which official version can it be mapped to? I mean is it 0.6.* or is it a 0.7.* release. That appears to correspond to a date of 2007-10-18. That's really, really old :) It looks like a very early cut of something off the trunk 0.7 development branch. It's definitely not an actual release of anything. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM before login?
On Wed, 2009-05-13 at 23:20 +0200, eric.bru...@lps.ens.fr wrote: Dans son message du mercredi 13/05/09 à 10:08, Dan Williams a écrit: Are you running with SELinux in enforcing mode, /etc/sysconfig/selinux contains the line SELINUX=disabled (I can only guess that this conf file is actually read and acted upon at boot time; I don't know how to ask the kernel what is the actual current selinux mode. There's probably a file in /sysfs, but I don't know which) and what is the version of your selinux-policy-targeted package? selinux-policy-targeted-3.5.13-58.fc10.noarch Second, do you see org.freedesktop.network-manager-settings.system.modify in the output of polkit-auth --show-obtainable ? Yes I do. What's in your /etc/NetworkManager/nm-system-settings.conf file? dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How do I setup a gsm internet connection in Network Manager using a mobile phone (via USB Data Cable or Bluetooth) ?
On Thu, 2009-05-14 at 20:56 +0530, Ratnadeep Debnath wrote: Hi all, I would like to know how do I setup an internet connection in Network Manager via a GSM/CDMA mobile phone connected to the system via a USB Data Cable ot bluetooth. Data cable will likely work. NM does not yet support Bluetooth, though Bastien and I have been adding that support to master since yesterday. Right-click on the applet in your panel, then choose Edit Connections. Click the Mobile Broadband tab, and click the New button. You'll need to select the actual type of connection (CDMA *or* GSM, make sure you pick the one your provider uses). Then fill in the APN (for GSM) and possibly also a username/password which some modems require, even though they can be random characters. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How do I setup a gsm internet connection in Network Manager using a mobile phone (via USB Data Cable or Bluetooth) ?
Ratnadeep Debnath schrieb: Hi all, I would like to know how do I setup an internet connection in Network Manager via a GSM/CDMA mobile phone connected to the system via a USB Data Cable ot bluetooth. Thanks, Regards, rtnpro | Ratnadeep Debnath ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list For bluetooth, if you're running NetworkManager 0.7.x, you can try blueman http://www.blueman-project.org Christian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: VPN connections in NetworkManager have strange behaviour
On Thu, 2009-05-14 at 16:08 +0200, Axel wrote: Hello I have a problem when using NetworkManager to connect to VPN connections, on an up to date fedora 11 system. Packages versions are : NetworkManager-gnome-0.7.1-4.git20090414.fc11.i586 NetworkManager-vpnc-0.7.0.99-1.fc11.i586 NetworkManager-0.7.1-4.git20090414.fc11.i586 NetworkManager-openvpn-0.7.0.99-1.fc11.i586 NetworkManager-pptp-0.7.0.99-1.fc11.i586 NetworkManager-glib-0.7.1-4.git20090414.fc11.i586 NetworkManager-glib-devel-0.7.1-4.git20090414.fc11.i586 NetworkManager-devel-0.7.1-4.git20090414.fc11.i586 I previously (ubuntu gutsy) used to connect to a vpnc (VPN Compatible Cisco) server with the command line tool. Using the command line still works with Fedora 11. When I try to switch to the NetworkManager builtin VPN manager, I manage to connect to the remote VPN server, but no network activity can be made. It s maybe a problem with the routes. When connecting to the VPN with the vpnc command line tool, no specific configuration (but the group user login/password) is defined. No specific routing configuration has been made. 192.168.246.254 is the gateway of the LAN. 62.39.X.X is the remote VPN server. Is the remote VPN server passing the netmask down to the client? vpnc should export the netmask in the environment of the handler it runs after connecting, in the INTERNAL_IP4_NETMASK variable. NetworkManager-vpnc looks for that, and if its found, it will use that value. So it could be a misconfiguration of your vpn concentrator. If that value is *not* present, NM will default to a /24, which could be what's happening here. That may be wrong, yes. But first lets verify what the VPN client is returning. One way to do this is to move /usr/libexec/nm-vpnc-service-vpnc-helper to /usr/libexec/nm-vpnc-service-vpnc-helper.ORIG, then put a small wrapper script at /usr/libexec/nm-vpnc-service-vpnc-helper that contains something like: #!/bin/sh env /tmp/vpn-env /usr/libexec/nm-vpnc-service-vpnc-helper.ORIG $@ and make that script executable, then connect. That should dump the environment to the file /tmp/vpn-env which will allow us to figure this out. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Auto Connect through NetworkManager
On Thu, 2009-05-14 at 09:31 +0800, 代尔欣 wrote: Hi sanjeev, Change g_signal_emit_by_name (device, state-changed, state, old_state, 0); to g_signal_emit_by_name (device, state-changed, state, old_state, reason); in function src/nm-device.c nm_device_state_changed(). This is why you always receive reason 0. After change, you should receive the correct reason. Hi Dan, If user want to GSM auto connect, but not always want to auto connect e.g. user disconnect manually, The current networkmanager do not act like this. Now when click the disconnect , the device will reconnect again. This behavior is a little strange I think. It is better if the auto connect occur when system up, network not available(e.g. unplug the net plug). But when user disconnect manually, do not auto connect. What I'm afraid of here is user confusion. You have to remember that now, after you've clicked disconnect, the device needs to be *manually* reactivated, even though your connections have a Connect automatically checkbox. The behavior is now inconsistent. Automatic no longer means automatic. So now you suspend the laptop and resume later, and you're not reconnected to anything. I'm not opposed to this sort of disconnected device property, but it's a larger job than just an attribute in NetworkManager. It also involves figuring out how the UI should handle it, how users should be alerted that their networks won't be automatically reconnected. The user is more apt to blame the computer or NetworkManager when it doesn't do what they expect, rather than blame themselves for something they did an hour ago which they've already forgotten. Dan Thank! Dan __ _ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list 2009/5/13 Dan Williams d...@redhat.com On Wed, 2009-05-13 at 10:20 +0530, sanjeev sharma wrote: Hi All, Is there any possibility to Disable Auto Connect through NetworkManager Code. in my Scenario If Auto Connect Is enabled In GSM Profile and User Click on Disconnect button then I wanted to Set Auto Connect flag disabled so networkManager won't retry to Start Connection again. That would imply you want to uncheck Connect automatically, because you don't actually want the connection to be automatically activated when its available. I don't want to change Auto Connect manually through Connection editior because during resume my System has been checking mail and its will start Connection if only Auto Connect is set. Instead, on resume you want NM to re-activate connections that were active when the system went to sleep (as long as that connection is available). Does that sound right? Dan ___ 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: using nm-system-settings for the user settings
On Thu, 2009-05-14 at 14:54 +0200, Martin Vidner wrote: Hi, in NM clients, such as the GUI applets and the CLI of yours truly, a fair amount of code deals with the connection settings. I got the idea that the current nm-system-settings service could be generalized to deal with the *user* settings too, so that one program could run as two processes serving the two services. That way the client code would be factored out in the separate settings service. One could then even use the same connections from different applets, unlike now when they are stored in KDE and GNOME specific stores. You can already use the same connections from different applets if you want to, anything can ask the user session applet for the list of connections, and then it can tell NM to activate that connection. I can use dbus-send to activate a user connection if I want to, as long as that dbus-send call is done as the same user the applet runs as. I started coding it, registering nm-system-settings at NetworkManagerUserSettings, wanting to continue with the config file location and PolicyKit restrictions. Dan, Tambet told me that you intend to merge nm-system-settings into NM itself. I am afraid that it goes in pretty much the opposite direction than I would need. Could you share some details and reasons for the merge so that we can try to make the ideas work out together? Reasons for the merge are: (a) elimination of a running process (b) reduce latency of unmanaged device discovery (c) code reduction in NM because IPC between NM and the system settings service would no longer be required (d) ability to store more things like persistent Wireless Enabled, Network Enabled, and device states in system config files Basically, I didn't see a compelling case for it to still be separate from NetworkManager. Obviously the org.freedesktop.NetworkManagerSystemSettings service would continue to be provided. I still don't see a very compelling reason to factor the user settings code out of the applet; it was stuck back into the applet (remember NetworkManagerInfo anyone?) a long time ago because having it separate was architecturally messy and had no benefit at the time. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: using nm-system-settings for the user settings
Dan Williams wrote: On Thu, 2009-05-14 at 14:54 +0200, Martin Vidner wrote: Dan, Tambet told me that you intend to merge nm-system-settings into NM itself. I am afraid that it goes in pretty much the opposite direction than I would need. Could you share some details and reasons for the merge so that we can try to make the ideas work out together? Reasons for the merge are: (a) elimination of a running process (b) reduce latency of unmanaged device discovery (c) code reduction in NM because IPC between NM and the system settings service would no longer be required (d) ability to store more things like persistent Wireless Enabled, Network Enabled, and device states in system config files Basically, I didn't see a compelling case for it to still be separate from NetworkManager. Obviously the There is one reason I can think of, why it still makes sense to keep nm-system-settings in a separate process: You can easily restart nm-system-settings after changing it's configuration, without losing internet connection. If NM could be fixed to not teardown an active connection on reload/restart, it would of course be even better. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: using nm-system-settings for the user settings
On Fri, 2009-05-15 at 00:09 +0200, Michael Biebl wrote: Dan Williams wrote: On Thu, 2009-05-14 at 14:54 +0200, Martin Vidner wrote: Dan, Tambet told me that you intend to merge nm-system-settings into NM itself. I am afraid that it goes in pretty much the opposite direction than I would need. Could you share some details and reasons for the merge so that we can try to make the ideas work out together? Reasons for the merge are: (a) elimination of a running process (b) reduce latency of unmanaged device discovery (c) code reduction in NM because IPC between NM and the system settings service would no longer be required (d) ability to store more things like persistent Wireless Enabled, Network Enabled, and device states in system config files Basically, I didn't see a compelling case for it to still be separate from NetworkManager. Obviously the There is one reason I can think of, why it still makes sense to keep nm-system-settings in a separate process: You can easily restart nm-system-settings after changing it's configuration, without losing internet connection. If NM could be fixed to not teardown an active connection on reload/restart, it would of course be even better. I'll be doing that for non-802.1x/non-PPPoE ethernet connections in NM 0.8. That is the only case for which this will be supported, because all other connection types have entirely too much state. Furthermore, there must be an existing stored connection config that exactly matches the existing device configuration when NM starts, otherwise the device will be reconfigured to the best connection at that time. The target use-cases are seamless restart of NetworkManager on an ethernet connected server, and assumption of existing IP configuration from an iSCSI configured by the initrd so that your rootfs doesn't go poof on boot. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
multiple active interfaces/connections in NM
hi, Would like to know if NM is meant to cover use cases where mutiple active interfaces are used with some custom routing... For e.g., I sit in my client's place connected to their internal network (ethernet). I can access my client's servers there but I can't get on the net. I have a 3G modem that I can plugin to access internet. Problem is, my routes and DNS settings seem to be controlled by either one of connections only. I'd like to use both of them at the same time; i.e. both interfaces active, and together with a few custom routes that ensures intranet traffic goes out the ethernet port and everything else goes into ppp. I can manually add routes right now, but the problem with 3G is that dropouts are pretty frequent and every time my connection gets reset, NM will reset my entire routing table. That sucks 'cos it basically means my SSH sessions to my servers in the intranet will be reset. I'm pretty sure part of the issue is whether my NM front-end (currently using NM KDE 4 plasmoid) is capable of handling this or not but i'm willing to forget abt the front end if I can pull together a bunch of bash scripts to do what I need. thanks Wong ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: multiple active interfaces/connections in NM
I think you mean this http://www.nabble.com/Default-Routing-problems-tt22514630.html#a22545427. I am not sure what version of NM you are running though and this is relatively now. -- John On Thu, May 14, 2009 at 11:53 PM, CS Wong lilw...@gmail.com wrote: hi, Would like to know if NM is meant to cover use cases where mutiple active interfaces are used with some custom routing... For e.g., I sit in my client's place connected to their internal network (ethernet). I can access my client's servers there but I can't get on the net. I have a 3G modem that I can plugin to access internet. Problem is, my routes and DNS settings seem to be controlled by either one of connections only. I'd like to use both of them at the same time; i.e. both interfaces active, and together with a few custom routes that ensures intranet traffic goes out the ethernet port and everything else goes into ppp. I can manually add routes right now, but the problem with 3G is that dropouts are pretty frequent and every time my connection gets reset, NM will reset my entire routing table. That sucks 'cos it basically means my SSH sessions to my servers in the intranet will be reset. I'm pretty sure part of the issue is whether my NM front-end (currently using NM KDE 4 plasmoid) is capable of handling this or not but i'm willing to forget abt the front end if I can pull together a bunch of bash scripts to do what I need. thanks Wong ___ 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
