nm-tool showing default route
Hi Dan,
below is a patch that shows the default route in nm-tool. Feel free to
modify it.
Markus
Index: test/nm-tool.c
===
--- test/nm-tool.c (revision 3715)
+++ test/nm-tool.c (working copy)
@@ -198,11 +198,14 @@
detail_device (gpointer data, gpointer user_data)
{
NMDevice *device = NM_DEVICE (data);
+ NMClient *client = NM_CLIENT (user_data);
char *tmp;
NMDeviceState state;
guint32 caps;
guint32 speed;
const GArray *array;
+ const GPtrArray *connections;
+ int j;
state = nm_device_get_state (device);
@@ -223,6 +226,21 @@
print_string ("State", get_dev_state_string (state));
+ connections = nm_client_get_active_connections (client);
+ for (j = 0; connections && (j < connections->len); j++) {
+ NMActiveConnection *candidate = g_ptr_array_index (connections,
j);
+ const GPtrArray *devices = nm_active_connection_get_devices
(candidate);
+ NMDevice *candidate_dev;
+
+ if (!devices || !devices->len)
+ continue;
+ candidate_dev = g_ptr_array_index (devices, 0);
+
+ if ( candidate_dev == device &&
+nm_active_connection_get_default(candidate))
+ print_string ("Route", "IPv4 Default Route");
+ }
+
tmp = NULL;
if (NM_IS_DEVICE_802_3_ETHERNET (device))
tmp = g_strdup (nm_device_802_3_ethernet_get_hw_address
(NM_DEVICE_802_3_ETHERNET (device)));
@@ -362,7 +380,7 @@
}
devices = nm_client_get_devices (client);
- g_ptr_array_foreach ((GPtrArray *) devices, detail_device, NULL);
+ g_ptr_array_foreach ((GPtrArray *) devices, detail_device, client);
g_object_unref (client);
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Auto-activate
Am Mo 02 Jun 2008 17:00:24 CEST schrieb Dan Williams <[EMAIL PROTECTED]>: > On Sun, 2008-06-01 at 21:34 +0200, Will Stephenson wrote: >> What needs to be done to get NM to autoconnect a wireless connection on >> UserSettingsService startup? I can see KNM responding to GetSettings with >> autoconnect=true, but NM then seems to ignore the connection. I am going to >> put some debug in NetworkManagerPolicy.c but could someone (Dan hopefully) >> elaborate the way it should work, from a client's point of view? > > For wifi, look in nm-device-802-11-wireless.c, > real_get_best_auto_connection(). That loops through all connections, > and will match connections based on: > > a) if it's a wireless connection > b) if it's autoconnect > c) if it's got a wireless setting > d) if it has a MAC address, if that MAC matches the device's MAC > e) if there's a compatible AP in the device's scan list > > I'd suspect (e) first here actually. There may be a bug in the AP > matching code, or the connection may just be wrong for the AP you're > trying to connect to. If the call to nm_ap_check_compatible() for your > AP is returning FALSE, get the iwlist output for the AP and then drill > down into that function and see why it's returning FALSE. It's probably > in the security stuff. The issue is related to (e). It's the same issue as in the mail I've send you some days ago regarding "cipher preselection". NM will refuse to autoconnect to a wireless connection if no ciphers are specified. I just worked around this issue by specifying default ciphers in KNM. Helmut ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Adding a signal for a connection removed
What do you all think of having a signal on the service org.freedesktop.NetworkManagerSettings when a connection is removed instead of just added. If the keeping the current naming convention is desired, the new signal could be called RemovedConnection. If not, then ConnectionAdded and ConnectionRemoved sound more natural. Chris ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Lots of segfaults in nm-system-settings
Hello sorry for the delayed response. On Tue, 2008-05-20 at 10:08 +0100, The Holy ettlz wrote: > An excerpt from dmesg: > > nm-system-setti[14680]: segfault at ccbe5004 eip 00d01d78 esp bfbcba3c > error 5 > nm-system-setti[15193]: segfault at cb3e5004 eip 00d01d78 esp bf93279c > error 5 > nm-system-setti[15706]: segfault at b70e5004 eip 00d01d78 esp bf8e9f5c > error 4 > nm-system-setti[16222]: segfault at a79e5004 eip 00d01d78 esp bf909f7c > error 4 > nm-system-setti[16732]: segfault at 092e5004 eip 00d01d78 esp bff51dcc > error 4 > nm-system-setti[17246]: segfault at d9ce5004 eip 00d01d78 esp bfcba32c > error 5 > > There are loads of other similar messages. This is with > NetworkManager-0.7.0-0.6.8.svn3669.fc8 --- let me know if you need any > more information. One would need a backtrace to deal with issue, install debuginfo and enable coredumps $ debuginfo-install NetworkManager To enable coredumps, please refer - http://kbase.redhat.com/faq/FAQ_85_9691.shtm One a coredump has been generated, to obtain backtrace $ gdb --core=/path/to/coredump /usr/sbin/nm-system-setting ... (gdb) thread apply all bt < a long output which would be of interest to developers. > > James > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Ritesh Khadgaray Ph: +919970164885 Desktop LinuX N Stuff, RHCE Software Maintenance Engineer, Pune, Red Hat ॐ मणि पद्मे हूँ Eat Right, Exercise, Die Anyway. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [ubuntu/debian] monitoring woes of /etc/network/interfaces...
Dan Williams wrote: The downsides of course are that (a) you have to teach your GUI tools that might modify the config files about NetworkManager, and (b) you have to create a wrapper around dbus-send for CLI sysadmins so they don't have to type the entire dbus-send command. The init script could have "reload" action, which does just that: Reload the whole configuration. Cheers, 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: [ubuntu/debian] monitoring woes of /etc/network/interfaces...
On Mon, Jun 02, 2008 at 05:40:04PM -0400, Dan Williams wrote: > On Mon, 2008-06-02 at 23:32 +0200, Alexander Sack wrote: > > On Mon, Jun 02, 2008 at 10:04:11PM +0100, Daniel J Blueman wrote: > > > Network Manager 0.6.6 (in eg Ubuntu 8.04) monitors the > > > /etc/network/interfaces for changes and acts upon them as soon as the > > > file is modified. > > > > > > This can be seen as a good feature in certain ways, but had two > > > significant drawbacks I find: > > > > > > - in Linux/unix philosiphy (thus expected usage), editing > > > configuration files can be safely done (multiple times) until some > > > subsystem is restarted/notified > > > > > > - if you're logged in, and (eg) /home is NFS-mounted, you get a > > > consequent system hang > > > > > > Is there a strong case for this behaviour, or something else that > > > depends on this? > > > > This is an ubuntu specific patch. The reason for this patch is that we > > have other desktop components that change that file. > > > > However, I can see your point. Maybe implementing a dbus "reconfigure" > > instead of auto reconfiguring when config files change would be a > > good alternative? > > Yeah, was just discussing this with some people here in office. It > might be worthwhile to implement the dbus interface to re-read specific > classes of configuration rather than inotify monitoring them. This is > also an issue in 0.7 with the system settings service and system config > plugins. So you want a dbus API that allows more fine grained config reloading than just "reload everything possible"? > > The downsides of course are that (a) you have to teach your GUI tools > that might modify the config files about NetworkManager, and (b) you > have to create a wrapper around dbus-send for CLI sysadmins so they > don't have to type the entire dbus-send command. > a) I dont think this is something that should block this; distros probably have to maintain such "distro specific" admin tools anyway; adding a dbus-send after updating any config file should be acceptable imo. b) ack - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [ubuntu/debian] monitoring woes of /etc/network/interfaces...
On Mon, 2008-06-02 at 23:32 +0200, Alexander Sack wrote: > On Mon, Jun 02, 2008 at 10:04:11PM +0100, Daniel J Blueman wrote: > > Network Manager 0.6.6 (in eg Ubuntu 8.04) monitors the > > /etc/network/interfaces for changes and acts upon them as soon as the > > file is modified. > > > > This can be seen as a good feature in certain ways, but had two > > significant drawbacks I find: > > > > - in Linux/unix philosiphy (thus expected usage), editing > > configuration files can be safely done (multiple times) until some > > subsystem is restarted/notified > > > > - if you're logged in, and (eg) /home is NFS-mounted, you get a > > consequent system hang > > > > Is there a strong case for this behaviour, or something else that > > depends on this? > > This is an ubuntu specific patch. The reason for this patch is that we > have other desktop components that change that file. > > However, I can see your point. Maybe implementing a dbus "reconfigure" > instead of auto reconfiguring when config files change would be a > good alternative? Yeah, was just discussing this with some people here in office. It might be worthwhile to implement the dbus interface to re-read specific classes of configuration rather than inotify monitoring them. This is also an issue in 0.7 with the system settings service and system config plugins. The downsides of course are that (a) you have to teach your GUI tools that might modify the config files about NetworkManager, and (b) you have to create a wrapper around dbus-send for CLI sysadmins so they don't have to type the entire dbus-send command. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [ubuntu/debian] monitoring woes of /etc/network/interfaces...
On Mon, Jun 02, 2008 at 10:04:11PM +0100, Daniel J Blueman wrote: > Network Manager 0.6.6 (in eg Ubuntu 8.04) monitors the > /etc/network/interfaces for changes and acts upon them as soon as the > file is modified. > > This can be seen as a good feature in certain ways, but had two > significant drawbacks I find: > > - in Linux/unix philosiphy (thus expected usage), editing > configuration files can be safely done (multiple times) until some > subsystem is restarted/notified > > - if you're logged in, and (eg) /home is NFS-mounted, you get a > consequent system hang > > Is there a strong case for this behaviour, or something else that > depends on this? This is an ubuntu specific patch. The reason for this patch is that we have other desktop components that change that file. However, I can see your point. Maybe implementing a dbus "reconfigure" instead of auto reconfiguring when config files change would be a good alternative? - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [ubuntu/debian] monitoring woes of /etc/network/interfaces...
On Mon, 2008-06-02 at 22:04 +0100, Daniel J Blueman wrote: > Network Manager 0.6.6 (in eg Ubuntu 8.04) monitors the > /etc/network/interfaces for changes and acts upon them as soon as the > file is modified. > > This can be seen as a good feature in certain ways, but had two > significant drawbacks I find: > > - in Linux/unix philosiphy (thus expected usage), editing > configuration files can be safely done (multiple times) until some > subsystem is restarted/notified > > - if you're logged in, and (eg) /home is NFS-mounted, you get a > consequent system hang > > Is there a strong case for this behaviour, or something else that > depends on this? People seem to have quite different opinions about this sort of behavior. On the other side, SIGHUP isn't the right solution because it's only _one_ signal. In NM we could potentially monitor a few different things, and we don't want to have to re-read the VPN service .name files just because somebody sent a SIGHUP becuase they changed /etc/network/interfaces. I don't have a particular feeling either way, but I'd like to hear other people's thoughts on the subject too. dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[ubuntu/debian] monitoring woes of /etc/network/interfaces...
Network Manager 0.6.6 (in eg Ubuntu 8.04) monitors the /etc/network/interfaces for changes and acts upon them as soon as the file is modified. This can be seen as a good feature in certain ways, but had two significant drawbacks I find: - in Linux/unix philosiphy (thus expected usage), editing configuration files can be safely done (multiple times) until some subsystem is restarted/notified - if you're logged in, and (eg) /home is NFS-mounted, you get a consequent system hang Is there a strong case for this behaviour, or something else that depends on this? Many thanks, Daniel -- Daniel J Blueman ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Delay full modem initialization until SIM is unlocked
Dan Williams schreef: > On Sat, 2008-05-24 at 22:02 +0200, Dennis Noordsij wrote: > >> Hi, >> >> Some modems return ERROR to most AT commands when the SIM is still locked, >> specifically the "ATZ E0" in the initialization. >> > > BTW, which modem models do this? We're trying to get some hard data on > how often this happens. > > Dan AT+CGMI Novatel Wireless Incorporated AT+CGMM Expedite EU870D MiniCard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: > Hello, > > one part of my project is to create and specify a database for service > provider specific settings. I've created an example page in > live.gnome.org[1]. Please, comment if you find something missing or you > disagree. I will begin with the implementation next week. > > Br, > Antti > > > PS. > Is there someone on this list who can shed some light on PHS[2]? Is it > something that could be used with GNU/Linux and does it require service > provider specific configuration? I guess we'd better at least allow for PHS to be added when the users show up, even if we don't put them in now. Should probably just be another attribute on the provider like GSM or CDMA. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
On Mon, 2008-06-02 at 12:48 +0100, Bastien Nocera wrote: > On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: > > Hello, > > > > one part of my project is to create and specify a database for service > > provider specific settings. I've created an example page in > > live.gnome.org[1]. Please, comment if you find something missing or you > > disagree. I will begin with the implementation next week. > > Will you be using the XML file I sent as an example? > > Also, I don't think that the and tags are really that > useful, they could be properties of the provider instead (or do we have > any providers that do both?). Verizon's stated forward path is CDMA + LTE, so yeah, we'll have them in a year or two if we don't already. And some operators have converted from IS-95 to GSM (Vivo in Brazil for example). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: openvpn and network manager
On Mon, 2008-06-02 at 10:34 +0300, Dimitris Zilaskos wrote: > > > > Yeah, I poked at this some ago. The issue here is that since TAP looks > > like an ethernet device, it doesn't have the same IP configuration > > characteristics as TUN devices do. In the TAP case, you can also do > > DHCP over the TAP interface and get an IP that way too, or you can use > > static IP, or you can have the server push the IP down I think. > > > > There was also a lot of stuff about bridging in some of the HOWTOs that > > I read about TAP-mode. Do you have to set up bridging to use openvpn > > TAP mode on the client? It wasn't clear to me if that was required or > > not. > > I do not think so. I use tap and I have not setup a bridge. Ok, good :) Do you use DHCP on the tap interface? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Support for L2TP/IPsec
On Mon, 2008-06-02 at 10:57 +0900, David Smith wrote: > Dan Williams <[EMAIL PROTECTED]> writes: > > > On Sun, 2008-05-25 at 20:19 +0900, David Smith wrote: > >> Vincent Bernat <[EMAIL PROTECTED]> writes: > >> > >> > OoO En cette aube naissante du dimanche 25 mai 2008, vers 07:10, David > >> > Smith <[EMAIL PROTECTED]> disait: > >> > > >> >> Vincent, in your setup is there a strong reason you are using openswan > >> >> instead of strongswan? Please share. > >> > > >> > Hi David! > >> > > >> > I have not tried StrongSWAN, so I have no reason to use OpenSWAN instead > >> > of StrongSWAN. > >> > >> OK, could you please double-check that your configuration works with > >> strongswan as well as openswan? I want to propose that we focus on one > >> IKE implementation and considering the features available in strongswan, > >> that it works with the most server implementations especially Windows > >> 2003 and 2008 Server and that it supports smartcards the best make it a > >> lead contender. Dan, what do you think of deciding on an IKE? Something > >> like a bake-off? > > > > It mostly depends on what the various distros will be willing to > > package. I don't have a strong preference since I know next to nothing > > about either of them. But if we "bless" one then we have to have a > > pretty convincing story as to why we chose one over the other, so that > > we can tell that story to distros when they start asking why they need > > to package something else that has roughly the same functionality as > > something they already have. > > > > Is strongswan a fork of openswan? If so, was openswan upstream > > reluctant to take certain patches and thus the strongswan fork? > > There is a lot of material about strongswan and openswan's development > history in http://www.strongswan.org/docs/LinuxTag2008-strongSwan.pdf > . Even a nice tree of the forks. > > It seems that strongswan and openswan both split away from frees/wan for > different reasons: openswan was the branch that Xelerance developed for > their commercial network services and strongswan was community developed > to keep making a better linux IKEv1 and then v2 implementation. > > > Is there an intention to merge strongswan back into openswan in the > > future? That sort of thing. Unfortunately the politics matter to > > distros... > > Nobody on either list has hinted at anything like that, though > anything's possible. If they can co-exist then we're probably OK, I guess. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: announcing cnetworkmanager
On Fri, 2008-05-30 at 16:40 +0200, Martin Vidner wrote: > Hi, > > [10]cnetworkmanager is a command line interface for [11]Network > Manager. It is still lacking many features but I decided to announce > it now, when it can: > > 1. connect to WiFi networks > 2. read the configuration file of [12]KNetworkManager > > It is working for me on RC1 of openSUSE-11.0, which has > NetworkManager-0.7.0.r3685-3. It is my first project in Python, so > the code is somewhat cumbersome. Thanks to [13]Miso for getting me > started ([14]idea.o.o, [15]abclinuxu.cz), and [16]Bille for the API > docs. Pretty cool! we do need a CLI client. Let me know if you need anything explained. Dan > Regarding related projects, I have seen [17]network-manager-cli, but > it is for 0.6 only and the developers were only active last August, > so I decided that I should first write some working code for 0.7. > > I am interested in comments, bugs, feature requests, patches, any > feedback. > > Here are some screenshots ;-) > > $ cnetworkmanager -h > cnetworkmanager 0.3 - Command Line Interface for NetworkManager > Options: > -d, --dev list devices > -c, --actcon list active connections > -s, --syscon list system connection settings > -u, --usrcon list user connection settings (can CRASH nm-applet) > -a, --ap list found access points > -n, --netslist found wireless networks > -C, --connect= connect to a wireless network (using > knetworkmanagerrc) > -m, --monitor loop to show dbus signals > > Listing the networks: > $ cnetworkmanager -n > cnetworkmanager 0.3 - Command Line Interface for NetworkManager > Wifi Networks: > 49: onenet (54Mb, protected) > 46: IT (54Mb, protected) > 48: TiborBrunclik (11Mb, protected) > 46: linksys (54Mb) > 46: IT (54Mb, protected) > 46: 23 (54Mb) > > Links: > 10. http://vidner.net/martin/software/cnetworkmanager/ > 11. http://www.gnome.org/projects/NetworkManager/ > 12. http://en.opensuse.org/Projects/KNetworkManager > 13. http://en.opensuse.org/User:Mzugec > 14. http://idea.opensuse.org/content/ideas/control-networkmanager-from-cli > 15. > http://www.abclinuxu.cz/blog/iSCSI_initiator_howto/2008/2/networkmanager-d-bus-python > 16. http://www.kdedevelopers.org/blog/77 > 17. http://code.google.com/p/network-manager-cli/ > $self. http://mvidner.blogspot.com/2008/05/try-cnetworkmanager-03.html > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet suddenly stopped connecting to some networks
On Mon, 2008-06-02 at 11:31 -0700, Joshua Spodek wrote: > The context > > I am running nm-applet 0.6.5 on Ubuntu 7.10 on a Lenovo X61. It's > worked great for a few months. Suddenly it partly stopped networking > with my home wireless. Do you know what kind of wireless card you have in your laptop? I'm guessing its an Intel PRO/Wireless 3945. What's the output of the command "/sbin/lsmod" when you enter that into a terminal and hit return? > When I first start nm-applet it shows the two-computer icon with an x > on it in the panel. After about one second the x goes away, but I > don't have a connection. > > The problem > > If I left-click the two-computer icon, the list of networks shows up > with signal strength and the two-computer icon switches to the bars > with all the bars empty and I don't connect. Could you attach some logs from /var/log/daemon.log ? That will tell us what's going on when you try to connect. Dan > If I click my network, nothing happens except that the next time I > left click the icon, the radiobutton for my network is selected. What > used to happen was the nm-applet icon would switch to the > trying-to-connect icon (two dots with moving arrows between them). > > Possibly related behavior > > If I go to the library across the street (where I am posting now), it > connects, but it still never shows the trying-to-connect icon. The > bars just fill up. > > If I connect on ethernet, it switches and works automatically. > > I don't know what caused the problem. It's possible using the library > connection caused a problem. On this network Evolution can't send > emails (but can receive them) and it occasionally blocks a site. > > Can anyone help? Should I provide more information? > > ___ > 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
nm-applet suddenly stopped connecting to some networks
The context I am running nm-applet 0.6.5 on Ubuntu 7.10 on a Lenovo X61. It's worked great for a few months. Suddenly it partly stopped networking with my home wireless. When I first start nm-applet it shows the two-computer icon with an x on it in the panel. After about one second the x goes away, but I don't have a connection. The problem If I left-click the two-computer icon, the list of networks shows up with signal strength and the two-computer icon switches to the bars with all the bars empty and I don't connect. If I click my network, nothing happens except that the next time I left click the icon, the radiobutton for my network is selected. What used to happen was the nm-applet icon would switch to the trying-to-connect icon (two dots with moving arrows between them). Possibly related behavior If I go to the library across the street (where I am posting now), it connects, but it still never shows the trying-to-connect icon. The bars just fill up. If I connect on ethernet, it switches and works automatically. I don't know what caused the problem. It's possible using the library connection caused a problem. On this network Evolution can't send emails (but can receive them) and it occasionally blocks a site. Can anyone help? Should I provide more information? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
On Mon, 02 Jun 2008 14:39:51 +0300 Antti Kaijanmäki <[EMAIL PROTECTED]> wrote: > Is there someone on this list who can shed some light on PHS[2]? It is a Japanese market DECT-like system allowing some usage outside the home via a subscription service. It's pretty old now, developed in the 1993-1995 timescale, and I don't know how much of it is still extant. I doubt it used any kind of SIM card, it was more likely to be based on a MAC address type pairing with a base station in the home and use the same mechanism to associate with a public base station and account when outside. -- Brian Morrison bdm at fenrir dot org dot uk "Arguing with an engineer is like wrestling with a pig in the mud; after a while you realize you are muddy and the pig is enjoying it." GnuPG key ID DE32E5C5 - http://wwwkeys.uk.pgp.net/pgpnet/wwwkeys.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Auto-activate
On Sun, 2008-06-01 at 21:34 +0200, Will Stephenson wrote: > What needs to be done to get NM to autoconnect a wireless connection on > UserSettingsService startup? I can see KNM responding to GetSettings with > autoconnect=true, but NM then seems to ignore the connection. I am going to > put some debug in NetworkManagerPolicy.c but could someone (Dan hopefully) > elaborate the way it should work, from a client's point of view? For wifi, look in nm-device-802-11-wireless.c, real_get_best_auto_connection(). That loops through all connections, and will match connections based on: a) if it's a wireless connection b) if it's autoconnect c) if it's got a wireless setting d) if it has a MAC address, if that MAC matches the device's MAC e) if there's a compatible AP in the device's scan list I'd suspect (e) first here actually. There may be a bug in the AP matching code, or the connection may just be wrong for the AP you're trying to connect to. If the call to nm_ap_check_compatible() for your AP is returning FALSE, get the iwlist output for the AP and then drill down into that function and see why it's returning FALSE. It's probably in the security stuff. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: API break / so versioning
On Mon, 2008-06-02 at 09:44 +0300, Tambet Ingo wrote: > On Fri, May 30, 2008 at 9:31 PM, Dan Williams <[EMAIL PROTECTED]> wrote: > > On Fri, 2008-05-30 at 20:13 +0200, Michael Biebl wrote: > >> What you can easily notice (by running a diff), ist that not only a lot > >> of symbols were added, but also quite a few were removed, which could > >> result in application crashes. In case of an API break, you usually bump > >> the SOVERSION, which leads to the more general question, if NM shouldn't > >> start using proper soversioning [1]. > > > > Yes, it probably should. One thing that we've tried to do is keep the > > old libnm_glib symbols around though, which is why we kept the > > libnm_glib name instead or renaming it to libnm-glib instead. So that > > at least apps that used the old basic 0.6 API bits would still work. > > There's probably no point in keeping that anymore. The basic API is > kept, but some of the basic defined variables have changed > (NMDeviceState), so even if something might still compile, it probably > doesn't work anymore. I think some apps still use it (evolution maybe?), though that may be a custom Fedora patch. We could build the old bits into the .so.0 and all the new bits into the .so.1 perhaps? Dan > > If we're willing to ditch that assumption, then I'm all for removing > > that code and bumping the soname. > > > >> I also wondered, if the separate library libnm_glib_vpn.so.0 is really > >> necessary or should be folded into libnm_glib.so.0. > > > > This is used by the VPN services and isn't really part of the same bits > > that should be used by clients of NM. I tend to think we should keep > > them separate, since if you're writing a client like nm-applet you > > shouldn't care about anything that's in libnm_glib_vpn. Maybe Tambet > > has more thoughts? > > Yes, these should be separate. One (libnm-glib) is part of the client, > the other (libnm-glib-vpn) part of the daemon. > > Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: I probably have the wrong idea for NetworkManager...
Hi Dan... On Sun, Jun 1, 2008 at 10:11 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > On Fri, 2008-05-30 at 16:19 -0400, Rick Beldin wrote: >> Ubuntu 8.04 > > Ok; that means NM 0.6.6 which is somewhat limited in it's capability to > control more complex connections. 0.7 is better here but Ubuntu isn't > shipping it since it's not entirely released yet. We've gotten pretty > good results so far with 0.7 prerelease versions in Fedora 8 and Fedora > 9 over the past 9 months though. > Exactly... dpkg -l network-manager Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii network-manage 0.6.6-0ubuntu5 network management framework daemon [EMAIL PROTECTED]:~/Linux/XenServer/2008-05-22-09-16-49-1-bugtool-wpg-xen-01/bu >> I'll have to admit that I am rather old school when it comes to administering >> my machines. I usually like to take a more active approach than >> letting a daemon make decisions for me. I used to hack on >> /etc/network/interfaces and /etc/resolv.conf to get what I wanted >> done, and in some ways I am missing that level of control... >> >> I have an HP laptop with a wired and a wireless interface. My >> network usage falls into three models: >> >> - wireless, no VPN, roaming >> - wired, no wireless (in the office) DHCP on wired >> - wireless, VPN, dhcp, no wired (tun0 interface created) >> >> I run into several issues with NetworkManager: >> >> - if I have been working at home, (wireless, WEP, VPN) and transition to >> the office, I have to manually enable the wired interface. > > In the Ubuntu network control panel, have you made the wired device > "roaming" or "manual" mode? When it's in Manual mode, it's hidden from > NM due to custom Ubuntu patches. > > What _should_ happen is that when you plug the wired cable into your > laptop, NM will tear down the wireless connection and bring up the wired > connection using DHCP as you've specified. But if you've put your > device in "manual" mode in ubuntu, then that's not to happen because > you've chosen to control the device manually. > I ended up putting it in 'manual' mode because the periodic dhcp timeout (my assumption here) on the wired interface would cause my vpn to drop if I was using the wireless interface. I ended up assigning a static IP just to get it out of the way for now. I would assume that nm looks at the link-state before kicking things off again, but a flaky card could do something. >> - if I have been working in the office (wired, no VPN) and come home, >> I generally have to fiddle with enabling/disabling wireless and wired >> interfaces until I get a DHCP address from the wireless router. I >> sometimes have to kill dhclient and clear out /var/lib/dhcp3 in order >> for NetworkManager to realize it has to go get a new ip. The >> interface will be 'up' but no. No errors from dhcp on router. > > Sounds like a flaky driver isn't associating to the AP. What wireless > card do you have? Can you post some logs from /var/log/daemons to show > what NM is doing during this time? What sort of wifi configuration do > you have at home? > This is an Intel card using the ipw2200 driver. From lspci: 02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) I'll dig up some logs after I come back home this afternoon. The wired interface is: 10:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11) dmesg shows *[ 52.757661] eth0: Tigon3 [partno(BCM95751M) rev 4101 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:15:60:b1:92:68 In the current state, eth0 (wireless) up and eth1 (wired) inactive, mii-tool shows: # sudo ethtool eth0 Settings for eth0: Link detected: yes # sudo ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (65535) Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: g Current message level: 0x00ff (255) Link detected: no >> - if am working with the VPN (tun0) wireless and the little checkbox >> is ON next to the wired interface, I am *assured* that my connection >> will drop periodically. Usual
Re: Service Provider Database
On Mon, 2008-06-02 at 15:12 +0300, Antti Kaijanmäki wrote: > ma, 2008-06-02 kello 12:48 +0100, Bastien Nocera kirjoitti: > > On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: > > > Hello, > > > > > > one part of my project is to create and specify a database for service > > > provider specific settings. I've created an example page in > > > live.gnome.org[1]. Please, comment if you find something missing or you > > > disagree. I will begin with the implementation next week. > > > > Will you be using the XML file I sent as an example? > > I could use it, but I would have to write a conversion script from your > XML format to the format we decide to use. I rather modify my existing > python script instead and make direct conversion from the last GPRS EC > database. I believe I've also posted the Perl script that generated the output, which does the country code conversion, and tags the providers properly. > > Also, I don't think that the and tags are really that > > useful, they could be properties of the provider instead (or do we have > > any providers that do both?). > > with properties you mean attributes? If so then w3school says[1]: > "There are no rules about when to use attributes and when to use > elements. Attributes are handy in HTML. In XML my advice is to avoid > them. Use elements instead." > And I prefer elements :) > > If a service provider offers different types of subscriptions then there > would be provider element for every different type and the name element > would distinguish the types from each other. > > >Service Provider - CDMA > > > >Service Provider - GSM > > internet > > > >Service Provider - GSM prepaid > > prepaid.provider > > I'd rather have: Service Provider - GSM prepaid prepaid.provider Or at least: Service Provider - GSM prepaid prepaid.provider Whether they're GSM or CDMA is a property of the provider. > The user would see a drop-down menu with items: > Service Provider - CDMA > Service Provider - GSM > Service Provider - GSM prepaid Cheers ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
I forgot the link.. [1] http://www.w3schools.com/xml/xml_attributes.asp ma, 2008-06-02 kello 15:12 +0300, Antti Kaijanmäki kirjoitti: > ma, 2008-06-02 kello 12:48 +0100, Bastien Nocera kirjoitti: > > On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: > > > Hello, > > > > > > one part of my project is to create and specify a database for service > > > provider specific settings. I've created an example page in > > > live.gnome.org[1]. Please, comment if you find something missing or you > > > disagree. I will begin with the implementation next week. > > > > Will you be using the XML file I sent as an example? > > I could use it, but I would have to write a conversion script from your > XML format to the format we decide to use. I rather modify my existing > python script instead and make direct conversion from the last GPRS EC > database. > > > > Also, I don't think that the and tags are really that > > useful, they could be properties of the provider instead (or do we have > > any providers that do both?). > > with properties you mean attributes? If so then w3school says[1]: > "There are no rules about when to use attributes and when to use > elements. Attributes are handy in HTML. In XML my advice is to avoid > them. Use elements instead." > And I prefer elements :) > > If a service provider offers different types of subscriptions then there > would be provider element for every different type and the name element > would distinguish the types from each other. > > >Service Provider - CDMA > > > >Service Provider - GSM > > internet > > > >Service Provider - GSM prepaid > > prepaid.provider > > > > The user would see a drop-down menu with items: > Service Provider - CDMA > Service Provider - GSM > Service Provider - GSM prepaid > > -- Antti > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
ma, 2008-06-02 kello 12:48 +0100, Bastien Nocera kirjoitti: > On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: > > Hello, > > > > one part of my project is to create and specify a database for service > > provider specific settings. I've created an example page in > > live.gnome.org[1]. Please, comment if you find something missing or you > > disagree. I will begin with the implementation next week. > > Will you be using the XML file I sent as an example? I could use it, but I would have to write a conversion script from your XML format to the format we decide to use. I rather modify my existing python script instead and make direct conversion from the last GPRS EC database. > Also, I don't think that the and tags are really that > useful, they could be properties of the provider instead (or do we have > any providers that do both?). with properties you mean attributes? If so then w3school says[1]: "There are no rules about when to use attributes and when to use elements. Attributes are handy in HTML. In XML my advice is to avoid them. Use elements instead." And I prefer elements :) If a service provider offers different types of subscriptions then there would be provider element for every different type and the name element would distinguish the types from each other. Service Provider - CDMA Service Provider - GSM internet Service Provider - GSM prepaid prepaid.provider The user would see a drop-down menu with items: Service Provider - CDMA Service Provider - GSM Service Provider - GSM prepaid -- Antti signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Service Provider Database
On Mon, 2008-06-02 at 14:39 +0300, Antti Kaijanmäki wrote: > Hello, > > one part of my project is to create and specify a database for service > provider specific settings. I've created an example page in > live.gnome.org[1]. Please, comment if you find something missing or you > disagree. I will begin with the implementation next week. Will you be using the XML file I sent as an example? Also, I don't think that the and tags are really that useful, they could be properties of the provider instead (or do we have any providers that do both?). Cheers ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Service Provider Database
Hello, one part of my project is to create and specify a database for service provider specific settings. I've created an example page in live.gnome.org[1]. Please, comment if you find something missing or you disagree. I will begin with the implementation next week. Br, Antti PS. Is there someone on this list who can shed some light on PHS[2]? Is it something that could be used with GNU/Linux and does it require service provider specific configuration? [1]http://live.gnome.org/NetworkManager/MobileBroadband/ServiceProviders [2]http://en.wikipedia.org/wiki/Personal_Handy-phone_System signature.asc Description: Digitaalisesti allekirjoitettu viestin osa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: openvpn and network manager
> > Yeah, I poked at this some ago. The issue here is that since TAP looks > like an ethernet device, it doesn't have the same IP configuration > characteristics as TUN devices do. In the TAP case, you can also do > DHCP over the TAP interface and get an IP that way too, or you can use > static IP, or you can have the server push the IP down I think. > > There was also a lot of stuff about bridging in some of the HOWTOs that > I read about TAP-mode. Do you have to set up bridging to use openvpn > TAP mode on the client? It wasn't clear to me if that was required or > not. I do not think so. I use tap and I have not setup a bridge. Regards, -- Dimitris Zilaskos Department of Physics @ Aristotle University of Thessaloniki , Greece PGP key : http://tassadar.physics.auth.gr/~dzila/pgp_public_key.asc http://egnatia.ee.auth.gr/~dzila/pgp_public_key.asc MD5sum : de2bd8f73d545f0e4caf3096894ad83f pgp_public_key.asc ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
