Re: Segfault
On Sun, 2010-04-04 at 09:03 +0200, David Richfield wrote: Hi, I'm running NetworkManager Applet 0.7.996 (stock standard Ubuntu Karmic version). I've got a new USB wifi dongle that I'm using to connect my laptop to my ADSL router. Today it went down for no apparent reason, and when I looked in /var/log/syslog, I found this line: Apr 4 08:05:15 davelaptop kernel: [ 757.375313] nm-applet[2022]: segfault at 64 ip 0806d850 sp bfbaa3d0 error 4 in nm-applet[8048000+53000] What can I do to give a good bug report? If you can possibly reproduce the issue and get the set of steps that reproduce it, that's good. Otherwise, looking in ~/.xsession-errors can sometimes give more info about why the applet died. That's where any applet output goes, and it may contain logging of critical errors from right before the applet went away. Dan Another thing: how do I interpret the log messages? I can't find a man page or any useful documentation in /usr/share/doc/network-manager. I keep seeing things like: Apr 4 08:05:15 davelaptop NetworkManager: info (wlan12): device state change: 8 - 3 (reason 38) or Apr 4 08:05:15 davelaptop NetworkManager: info (00:23:B4:25:E4:39): device state change: 3 - 1 (reason 36) Where is a list of what the different states are, and what the reasons mean? Regards, ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager Trunk and Fedora 12
On Thu, 2010-04-01 at 08:55 -0400, Darren Albers wrote: On Wed, Mar 31, 2010 at 10:02 AM, Colin Walters walt...@redhat.com wrote: - Dan Williams d...@redhat.com wrote: /var/log/messages: Mar 25 19:51:58 localhost dbus-daemon: Rejected send message, 2 matched rules; type=method_return, sender=:1.12 (uid=0 pid=1424 comm=/usr/sbin/bluetoothd) interface=(unset) member=(unset) error name=(unset) requested_reply=0 destination=:1.10 (uid=0 pid=1414 comm=NetworkManager)) At what point does that failure come? This could be caused by recent (well, year-old) dbus policy changes for unrequested reply messages which I'm not 100% sure how to get fixed... walters; what could be the cause of this sort of thing again? The operative component here is requested_reply=0, and the policy is to reject unrequested replies. Often this is harmless because if a message wasn't expecting a reply, denying a reply shouldn't matter. If however the binding/code was setting no_reply AND actually expecting to process the reply, that's a bug in the calling code. I ran modem-manager with debug and here is the output: ** Message: (rfcomm0) opening serial device... ** (modem-manager:2090): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'ATICR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'Research In Motion BlackBerry IP ModemCRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+CPIN: READYCRLFCRLFOKCRLF' ** Message: (rfcomm0) closing serial device... ** Message: Generic: (tty/rfcomm0) WARNING: missing udev 'device' file ** Message: (rfcomm0) opening serial device... ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 claimed port rfcomm0 ** (modem-manager:2090): DEBUG: Added modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+CPIN: READYCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'CRLFOKCRLF' ** Message: (rfcomm0) closing serial device... ** (modem-manager:2090): DEBUG: Exported modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 as /org/freedesktop/ModemManager/Modems/0 ** Message: (rfcomm0) opening serial device... ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'ATZ E0 V1 +CMEE=1CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'CRLFERRORCRLF' ** (modem-manager:2090): DEBUG: Got failure code 100: Unknown error ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - disabled) ** Message: (rfcomm0) closing serial device... ** (modem-manager:2090): DEBUG: Removed modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 Looks like there is something else going on and the Blackberry rejected the connection? Like you found, it probably doesn't like +CMEE=1... guess we'll have to handle that somewhat differently in the generic plugin. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: default value for autoconnect
On Thu, 2010-04-01 at 14:31 +0200, Marcin Klekot wrote: The NM spec on http://projects.gnome.org/NetworkManager/developers/settings-spec-08.html says that the default value for autoconnect in the connection setting is FALSE. But testing it with dbus-monitor --system it looks like TRUE is the default value. If I change some connection settings with nm-applet (or my own Application) and disable the autoconnect checkbox the resulting Updated signal from NM looks as follows: dict entry( string connection array [ dict entry( string uuid variant string 600d780d-d2ff-4221-b6ed-7f67f5ee24af ) dict entry( string autoconnect variant boolean false ) dict entry( string id variant string foo ) dict entry( string type variant string 802-11-wireless ) ] ) But if I enable the autoconnect checkbox in nm-applet the resulting Updated signal does not contain the autoconnect entry: dict entry( string connection array [ dict entry( string uuid variant string 600d780d-d2ff-4221-b6ed-7f67f5ee24af ) dict entry( string id variant string foo ) dict entry( string type variant string 802-11-wireless ) ] ) So my question is, is that a mistake in the NM spec and TRUE is the default value for autoconnect and for that reason NM skips that entry, or did i misunderstood something? I'm using NM Ver. 0.8 on ubuntu 9.10. You are correct; the default should be TRUE. This was due to an error in the spec generator, now fixed and pushed to git and the website. Thanks! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot see the D-BUS for WIFI device when NM is running
On Wed, 2010-03-31 at 10:31 -0700, Bluesky_greenleaf wrote: Dear Dan, I don't start the D-Bus for WIFI when am running the NM in my embedded device. I don't know if there is the problem for NM or device driver. But I can use iwconfig and dhclient to set wifi to connect to Internet. I also know the device driver may be the problem for iwioctl since there are some warning as shown in /var/log/message, I also have checked NM is always calling sys/ioctl.h. My questions, if I don't fix the device driver, Is there a way to fix this problem through change some codes in NM?, or there is no way in the NM side. The wifi device is Atheros AR6000,Thanks for your suggestion. The errors are coming from iwconfig and/or wpa_supplicant and should be harmless actually. Can you grab your /etc/network/interfaces file for me? Dan Wei The information from /var/log/messages: [42949383.22] ar6000_init() Got WMI @ 0xccc41c00. [42949383.47] mac address = 00:21:e8:70:c8:bc [42949383.47] ar6000_init() WMI is ready [42949383.49] wmi_control_rx() : Unknown id 0x101e [42949383.50] AR6000 Reg Code = 0x8348 [42949397.41] ADDRCONF(NETDEV_UP): wlan0: link is not ready [42949403.94] iwioctl: cmd=0x8b03 not allowed in this mode [42949403.95] iwioctl: cmd=0x8b1d not allowed in this mode [42949403.96] iwioctl: cmd=0x8b23 not allowed in this mode [42949403.97] iwioctl: cmd=0x8b25 not allowed in this mode [42949404.02] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949404.25] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949406.05] iwioctl: cmd=0x8b03 not allowed in this mode [42949406.07] iwioctl: cmd=0x8b1d not allowed in this mode [42949406.08] iwioctl: cmd=0x8b23 not allowed in this mode [42949406.09] iwioctl: cmd=0x8b25 not allowed in this mode [42949407.31] ADDRCONF(NETDEV_UP): wlan0: link is not ready [42949408.54] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949410.13] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949414.77] keyboard.c: can't emulate rawmode for keycode 0 [42949419.57] keyboard.c: can't emulate rawmode for keycode 0 [42949420.84] eth2: no IPv6 routers present [42949590.19] iwioctl: cmd=0x8b03 not allowed in this mode [42949590.20] iwioctl: cmd=0x8b1d not allowed in this mode [42949590.21] iwioctl: cmd=0x8b23 not allowed in this mode [42949590.22] iwioctl: cmd=0x8b25 not allowed in this mode [42949591.54] ADDRCONF(NETDEV_UP): wlan0: link is not ready [42949592.99] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949597.36] iwioctl: cmd=0x8b03 not allowed in this mode [42949597.38] iwioctl: cmd=0x8b1d not allowed in this mode [42949597.39] iwioctl: cmd=0x8b23 not allowed in this mode [42949597.40] iwioctl: cmd=0x8b25 not allowed in this mode [42949597.92] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949599.05] ADDRCONF(NETDEV_UP): wlan0: link is not ready [42949600.50] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1 [42949610.99] eth2: no IPv6 routers present # iwconfig lono wireless extensions[ 93.67] iwioctl: cmd=0x8b03 not allowed in this mode . sit0 no wireless exten[ 93.69] iwioctl: cmd=0x8b1d not allowed in this mode sions. eth2 no wireless [ 93.70] iwioctl: cmd=0x8b23 not allowed in this mode extensions. [ 93.72] iwioctl: cmd=0x8b25 not allowed in this mode wlan0 AR6000 802.11g Mode:Managed Bit Rate=1 Mb/s Tx-Power=0 dBm Sensitivity=0/3 Retry:on Encryption key:off Power Management:off Link Quality:255/94 Signal level:-96 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 According to the documents and your notes, I have setup /etc/NetworkManager/nm-system-setting.conf in the embedded device This is as follows $cat nm-system-setting.conf [main] plugins=ifupdown,keyfile [keyfile] unmanaged-device=mac:00:21:e8:70:c8:bc [ifupdown] managed=false Then I check the D-BUS for wifi, but the the D-bus for wifi is still not coming out, which still has informations as follows: device list is /org/freedesktop/NetworkManager/Devices/0 Device eth2 is activate No device list is /org/freedesktop/NetworkManager/Devices/1 Device wlan0 is activate On Tue, Mar 23, 2010 at 3:17 AM, Dan Williams d...@redhat.com wrote: On Mon, 2010-03-22 at 09:25 -0700, Bluesky_greenleaf wrote: Dear Dan, There are an Ethernet(eth2) and a wifi(wlan0) in an embedded device, Ethernet and Wifi are both set to connect Internet successful by using the manually Linux commands such as iwconfig wlan0 After NM is running in the
Re: NM repeatedly asking for WEP key
On Wed, 2010-03-31 at 15:26 +0100, Timothy Murphy wrote: On Tuesday 30 March 2010 08:28:46 pm you wrote: As I said, NM keeps asking for the WEP key. What kind of WEP key is it? There are 3 types; hexadecimal, ASCII, and passphrase. It could be that you're choosing the wrong type in NM. How long is the WEP key you're using, and does it have any non-hexadecimal characters in it (ie anything not [A-F] or [0-9]) ? Thank you for your response. It is a 10-digit hexadecimal WEP key, which works perfectly on 4 other laptops, 2 Fedora-12 Linux (with NM) and 2 Windows XP. I'm running Fedora-12/KDE on this machine, with an old Avaya PCI-to-PCMCIA WiFi card, which works fine using the network service in place of NM, as also under Windows XP. Ok, so we know the WEP key is right, that leaves just the wifi card as the culprit. So I'm going to go out on a limb and say that orinoco doesn't play well with wpa_supplicant these days, which is what I found last time I tried to use my Orinoco cards with NM and older kernels. If you can, try to make a plain wpa_supplicant config file for the network (check out /usr/share/doc/wpa_supplicant-0.6.8/wpa_supplicant.conf or whatever the path is on your machine) and then: service NetworkManager stop killall -TERM wpa_supplicant wpa_supplicant -dddt -i your interface name -c /path/to/your/config/file -D wext and we'll see what we get. If that fails to eventually connect (you'll see it enter the CONNECTED state) then we know we've got a driver problem. The fact that iwconfig and service 'network' work is a good baseline, but we need wpa_supplicant to work instead. Dan I give below the relevant /var/log/messages from an attempt I just made to use NM, as also /etc/sysconfig/network-scripts/ifcfg-eth1, /var/log/wpa_supplicant.log and the output of sudo iwlist scan: --- Mar 31 14:13:13 harriet NetworkManager: info starting... Mar 31 14:13:13 harriet NetworkManager: info Trying to start the modem- manager... Mar 31 14:13:13 harriet NetworkManager: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Mar 31 14:13:13 harriet NetworkManager: info Found wlan radio killswitch rfkill0 (at /sys/devices/pci:00/:00:0d.0/0.0/ieee80211/phy0/rfkill0) (driver unknown) Mar 31 14:13:13 harriet NetworkManager: info WiFi enabled by radio killswitch; enabled by state file Mar 31 14:13:13 harriet NetworkManager: info WWAN enabled by radio killswitch; enabled by state file Mar 31 14:13:13 harriet NetworkManager:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ... Mar 31 14:13:13 harriet NetworkManager:ifcfg-rh: read connection 'System dd-wrt (eth1)' Mar 31 14:13:13 harriet NetworkManager: info (eth1): driver supports SSID scans (scan_capa 0x01). Mar 31 14:13:13 harriet NetworkManager: info (eth1): new 802.11 WiFi device (driver: 'orinoco_cs') Mar 31 14:13:13 harriet NetworkManager: info (eth1): exported as /org/freedesktop/NetworkManager/Devices/0 Mar 31 14:13:13 harriet NetworkManager: info (eth1): now managed Mar 31 14:13:13 harriet NetworkManager: info (eth1): device state change: 1 - 2 (reason 2) Mar 31 14:13:13 harriet NetworkManager: info (eth1): bringing up device. Mar 31 14:13:13 harriet NetworkManager: info (eth1): preparing device. Mar 31 14:13:13 harriet NetworkManager: info (eth1): deactivating device (reason: 2). Mar 31 14:13:13 harriet NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed ... Mar 31 14:13:13 harriet NetworkManager: info modem-manager is now available Mar 31 14:13:13 harriet NetworkManager: info Trying to start the supplicant... Mar 31 14:13:13 harriet avahi-daemon[1237]: Network interface enumeration completed. Mar 31 14:13:13 harriet NetworkManager: info (eth1): supplicant manager state: down - idle Mar 31 14:13:13 harriet NetworkManager: info (eth1): device state change: 2 - 3 (reason 0) Mar 31 14:13:13 harriet NetworkManager: info (eth1): supplicant interface state: starting - ready Mar 31 14:13:13 harriet NetworkManager: info Activation (eth1) starting connection 'System dd-wrt (eth1)' Mar 31 14:13:13 harriet NetworkManager: info (eth1): device state change: 3 - 4 (reason 0) Mar 31 14:13:13 harriet NetworkManager: info Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 14:13:13 harriet NetworkManager: info Activation (eth1) Stage 1 of 5 (Device Prepare) started... Mar 31 14:13:13 harriet NetworkManager: info Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Mar 31 14:13:13 harriet NetworkManager: info Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Mar 31 14:13:13 harriet NetworkManager: info Activation (eth1) Stage 2 of 5 (Device Configure) starting... Mar 31 14:13:13
Re: Fedora Marketing
On Wed, 2010-03-31 at 02:08 +0100, Nelson Marques wrote: Dear Network Manager developers, My name is Nelson and I'm a contributor to the Fedora Marketing Team. Currently we (Fedora Marketing Team) is working on the Feature Profiles for Fedora 13 Goddard. I'm currently assigned to work on an article regarding NetworkManager. Recognizing that I am not an engineer, but instead a Marketing Professional, I would like to know if the possible could be achieved: * Have a small interview with NetworkManager developers. Sure, that would more or less be me as Tambet is off doing other things these days. Note that I did fill out F13 feature pages for the major highlights of new NM stuff for F13. Would any of those work for the items below? * Get hold of a small list of NetworkManager highlights for the following: ** Standard user ** Advanced user * Any features that the developers of NetworkManager would like to highlight. * A message for our users regarding NetworkManager from the developing team. * The major advancements you would like to promote accomplished on the last 6 months. I think most of this should be covered in the F13 feature pages, though perhaps there are other bits that you have questions about or need more clarification on? Dan Regarding the interviews, I'm free to fix a good schedule that fits your time. I understand that developers are usually busy and I will try to make it last 10/15 minutes tops (if we accomplish this by IRC); I'm also available to send the questionnaire by email if required, or arrange any method that suits you. Any questions please don't hesitate in contacting me. I can be contacted off-list through: nmarq...@fedoraproject.org 07...@ipam.pt Many thanks in advance, Nelson Marques. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Make NM respect manual setting in ifupdown
On Sun, 2010-04-04 at 17:36 +0200, Okkel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody,
Since I'm on Debian, I'm using /etc/network/interfaces to bring up my
wireless network connection. According to the wpa-supplicant docs at
/usr/share/doc/wpasupplicant/README.modes.gz one of the ways to do so is
by using wpa-supplicant scripts. Here's the corresponding part of my
/etc/network/interfaces:
Hmm, though this is usually done by setting:
managed=false
in /etc/NetworkManager/nm-system-settings.conf
or /etc/NetworkManager/NetworkManager.conf instead, which causes NM to
ignore devices that are listed in your /e/n/i file.
I suppose this enhancement would allow 'managed=true' and let the user
make individual devices unmanaged, which is nice.
The patch isn't quite what we'd need though, since what you really want
to do is to make the device 'unmanaged' if it's marked as 'manual'
in /e/n/i. Unfortunately the ifupdown plugin isn't well set up to
unmanage individual interfaces right now... any chance you'd be willing
to work on a patch for that?
asac/tony, any comments here?
Dan
auto wlan0
iface wlan0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
The ifupdown plugin ignores the 'manual' setting and tries to read the
wireless config since it sees wpa-* lines. This results in an error and
causes NM to take control over the interface.
The attached patch fixes this behaviour by giving interfaces configured
as 'manual' the NM_SETTING_MANUAL_SETTING_NAME type.
Thanks in advance,
Okkel Klaver
i...@vanhetland.nl
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAku4sgYACgkQQxTA2p4ePKfS1QCghaDQMzycIN8FlnO+s7i4+qbW
7xQAn3ClUTOc4YD822npR4lidhu6CPaI
=vCDR
-END PGP SIGNATURE-
differences between files attachment (nm-manual.patch)
diff -ur network-manager-orig-0.8//system-settings/plugins/ifupdown/parser.c
network-manager-0.8//system-settings/plugins/ifupdown/parser.c
--- network-manager-orig-0.8//system-settings/plugins/ifupdown/parser.c
2010-04-03 21:14:49.0 +0200
+++ network-manager-0.8//system-settings/plugins/ifupdown/parser.c
2010-04-04 13:18:16.0 +0200
@@ -55,6 +55,12 @@
ret_type = NM_SETTING_PPP_SETTING_NAME;
}
+// Added by Okkel Klaver i...@vanhetland.nl
+// Make ifupdown plugin respect manual setting
+if(value !strcmp(manual, value)) {
+ret_type = NM_SETTING_MANUAL_SETTING_NAME;
+}
+
while(!ret_type curr) {
if(!strncmp(wireless-, curr-key, strlen(wireless-)) ||
!strncmp(wpa-, curr-key, strlen(wpa-))) {
@@ -561,16 +567,21 @@
PLUGIN_PRINT(SCPlugin-Ifupdown,
update_connection_setting_from_if_block: name:%s, type:%s, id:%s, uuid: %s,
block-name, type, idstr,
nm_setting_connection_get_uuid (s_con));
+// Modified by Okkel Klaver i...@vanhetland.nl
+// Make ifupdown plugin respect manual setting
if (!strcmp (NM_SETTING_WIRED_SETTING_NAME, type))
update_wired_setting_from_if_block (connection, block);
else if (!strcmp (NM_SETTING_WIRELESS_SETTING_NAME, type)) {
update_wireless_setting_from_if_block (connection, block);
update_wireless_security_setting_from_if_block (connection,
block);
}
+else if(!strcmp(NM_SETTING_MANUAL_SETTING_NAME, type))
+success = TRUE;
update_ip4_setting_from_if_block (connection, block);
- success = nm_connection_verify (connection, error);
+ if(!success)
+success = nm_connection_verify (connection, error);
g_free (idstr);
return success;
diff -ur network-manager-orig-0.8//system-settings/plugins/ifupdown/plugin.h
network-manager-0.8//system-settings/plugins/ifupdown/plugin.h
--- network-manager-orig-0.8//system-settings/plugins/ifupdown/plugin.h
2010-04-03 21:14:49.0 +0200
+++ network-manager-0.8//system-settings/plugins/ifupdown/plugin.h
2010-04-04 13:18:16.0 +0200
@@ -35,6 +35,10 @@
#define SC_IS_PLUGIN_IFUPDOWN_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((obj),
SC_TYPE_PLUGIN_IFUPDOWN))
#define SC_PLUGIN_IFUPDOWN_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS
((obj), SC_TYPE_PLUGIN_IFUPDOWN, SCPluginIfupdownClass))
+// Added by Okkel Klaver i...@vanhetland.nl
+// Make ifupdown plugin respect manual setting
+#define NM_SETTING_MANUAL_SETTING_NAME manual
+
typedef struct _SCPluginIfupdown SCPluginIfupdown;
typedef struct _SCPluginIfupdownClass SCPluginIfupdownClass;
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
___
Re: Readin connection file in Network-Manager
On Fri, 2010-04-02 at 15:11 +0200, Sébastien Fillaudeau wrote: Hi everybody, For my study in my university, i work on network-manager source code. I download the sources file of network-manager by the git repositories I study the source code but i don't find where is the code where Network-manager load the wifi setting connection situed in ~/.gconf/system/networking/connections/ If you could help me by giving me the name of function or the file were i can find this information , i would really appreciate. You can read a bit about the NM architecture here: http://live.gnome.org/NetworkManagerConfiguration what happens is that nm-applet reads in the connections from GConf, then provides them over D-Bus to NetworkManager and other applications. NM waits for nm-applet to appear as a D-Bus service (it's the 'user settings service') and when it does, queries nm-applet for all the connections that nm-applet knows about. NM does that in nm-manager.c:user_query_connections(). nm-applet provides the connections through a subclass of NMSettingsService, called NMAGConfSettings. NMAGConfSettings is defined in nma-gconf-settings.c, and it registers a hook with its superclass called list_connections (see nma_gconf_settings_class_init) that gets called whenever some other D-Bus client asks the applet for any connections it knows about. I hope that gives you start! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ModemManager and e160
On Fri, 2010-04-02 at 10:41 +0200, Georg Grabler wrote: Dear .. all :-). I've been using Network Manager (KNetworkManager) for quite some time now. Due to a problem with my huawei e220 (instability), I got myself a huawei e160. The E220 is well-known to require firmware updates to be fully stable with Linux, not just NM. Lately I installed networkmanager 0.8 and modemmanager 0.3. Since that, my modem is still found, but it seems as if it's not initialized properly. I can activate it / connect, but activating the state changes to connecting (Activating), but immediately (1 second to five seconds?) switches back to a state as if i never tried to connect / as if it couldn't get a connection. The best thing to do is to follow the directions here: http://live.gnome.org/NetworkManager/Debugging under the section Debugging NetworkManager 0.8.x 3G connections. We specifically want the modem-manager --debug logs, which should tell us what is going wrong with the device. If you can get those, we can debug further and probably figure out what's going wrong. Dan Note: With the e220 it works properly, so I think it's probably some kind of initialization problem (in modemmanager?). If I try it with wvdial, it works fine. The modem gets in an enough unusable state, that I can't connect at all anymore (not with wvdial or with networkmanager). I've tried both, KNetworkManager and gnome networkmanager applet. Is there any way to backtrace it properly / provide help on this? I've tried making a bug report, but for some reason the gnome bugtracker won't send me my activation e-mail (grml). Output I could get: NetworkManager: info Activation (ttyUSB0) starting connection 'bob.at' NetworkManager: info (ttyUSB0): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info (ttyUSB0): device state change: 4 - 6 (reason 0) NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info (ttyUSB0): device state change: 6 - 4 (reason 0) NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: WARN stage1_prepare_done(): GSM modem connection failed: (32) No cause information available NetworkManager: info (ttyUSB0): device state change: 4 - 9 (reason 1) NetworkManager: info Marking connection 'bob.at' invalid. NetworkManager: info Activation (ttyUSB0) failed. NetworkManager: info (ttyUSB0): device state change: 9 - 3 (reason 0) NetworkManager: info (ttyUSB0): deactivating device (reason: 0). Kind regards, Georg ___ 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: gui design of nm-applet
On Thu, 2010-04-01 at 10:35 +0200, Torsten Spindler wrote: Hello, On Thu, 2010-04-01 at 20:52 +1300, Simon Geard wrote: ... Your link doesn't seem to be publicly accessible - I get You are not allowed to view this page when I click on it... you are right. My wrong for sending out an internal link. I guess the work results will be published some time on the public Ubuntu wiki. Sorry for the mis-information. Would be nice to coordinate designs, however, while they are actually in-progress. I know the GNOME Shell team is also working on a redesign for GNOME 3.0, plus there's the existing design ideas we had from a year or two ago that I blogged about. If there end up being more than one design proposals, it's going to be a lot harder to make any of them happen... Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Does network manager support WPS?
Hi all, I also want to know this. Does NM have plan support WPS? or already supported in newest version. Thanks! 2010/1/30 Dan Williams d...@redhat.com On Tue, 2010-01-26 at 18:03 +0800, Dig wrote: Hi someone, I'm using uBuntu 10.04 on my PC, wpa_supplicant is ready for WPS, but I don't know how to setup a WPS connection to My linksys wrt54g. At this time NM doesn't support WPS; we needed to add some functionality to wpa_supplicant's dbus interface first to make this happen. Now that the support has landed in wpa_supplicant (though only in the latest development versions of it) we can work on adding that support to NetworkManager and nm-applet. 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: Segfault
On Sunday 04 of April 2010 09:03:54 David Richfield wrote: Hi, I'm running NetworkManager Applet 0.7.996 (stock standard Ubuntu Karmic version). I've got a new USB wifi dongle that I'm using to connect my laptop to my ADSL router. Today it went down for no apparent reason, and when I looked in /var/log/syslog, I found this line: Apr 4 08:05:15 davelaptop kernel: [ 757.375313] nm-applet[2022]: segfault at 64 ip 0806d850 sp bfbaa3d0 error 4 in nm-applet[8048000+53000] What can I do to give a good bug report? Another thing: how do I interpret the log messages? I can't find a man page or any useful documentation in /usr/share/doc/network-manager. I keep seeing things like: Apr 4 08:05:15 davelaptop NetworkManager: info (wlan12): device state change: 8 - 3 (reason 38) or Apr 4 08:05:15 davelaptop NetworkManager: info (00:23:B4:25:E4:39): device state change: 3 - 1 (reason 36) Where is a list of what the different states are, and what the reasons mean? The messages are mainly useful for the developers, the states and reason codes can be found in the header file: http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/include/NetworkManager.h#n165 Jirka ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wilreless connection before login
On Monday 05 of April 2010 17:20:48 Aaron Konstam wrote: A week or so ago I posted the following question: I have meant to follow up on this years ago but let it slip. But this came up recently on the fedora-list so I need to ask. It seems to me that several versions ago it was possible to have NM create a wireless connection on boot rather than only on login. Is this possible and if so how does one set this up? - From Marc Herbert I received the response Wild guess: did you try to configure it using system-config-network, and then pass it to NM using the ifcfg-rh plugin? http://live.gnome.org/NetworkManager/SystemSettings --- I used system-configure-network to re-configure the ifcfg-eth1 file and am using the ifcfg-rh plugin. I got no connection before boot although the ifcfg-eth1 file indicated the ONBOOT=yes option Please post a /var/log/messages file to see if ifcfg-rh reads the file successfully. Basically if you use ifcfg-rh plugin, NM will read your ifcfg-eth1 file from /etc/sysconfig/network-scripts/ directory. What is the contents of the file? --- from Dan Williams I got the comment: You can also move connections between user and system with nm-connection-editor; look for the Available to all users checkbox in each connection's edit window. Checking that box makes it a system connection (thus available at boot time) as long as a plugin is enabled that allows writing of system connections. That wiki page should also talk about system settings plugins. Dan --- I tried that. I used nm-connection-editor to edit the entry for the AP I was using. Checked: the Available to all users checkbox. Then maybe I made a mistake by clicking activate. The result was the AP disappeared from the list of APs seen in the nm-applet, so that was no good. By checking the box, the connection settings are saved by a system settings plugin that is configured in the /etc/NetworkManager/nm-system-settings.conf (or NetworkManager.conf) via 'plugins' key. What plugins do you have configured here? What is the name of your created connection? Would someone just tell me how to activate a wireless connection before logging in with clear instructions I can follow. I assume this is possible Yes, it's possible. 1. check you have plugins=ifcfg-rh,keyfile in /etc/NetworkManager/nm-system- settings.conf (or NetworkManager.conf) file 2. start nm-connection-editor 3. click Wireless tab, click Add button 4. Put SSID of your AP to SSID edit box 5. name your connection to your favourite name in Connection name edit box 6. click OK to save a connection ifcfg-rh plugin will create a file ifcfg-your_name file in /etc/sysconfig /network-scripts Upon startup NM should activate the connection. Jirka ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager Trunk and Fedora 12
On Tue, Apr 6, 2010 at 3:34 AM, Dan Williams d...@redhat.com wrote: On Thu, 2010-04-01 at 08:55 -0400, Darren Albers wrote: On Wed, Mar 31, 2010 at 10:02 AM, Colin Walters walt...@redhat.com wrote: - Dan Williams d...@redhat.com wrote: /var/log/messages: Mar 25 19:51:58 localhost dbus-daemon: Rejected send message, 2 matched rules; type=method_return, sender=:1.12 (uid=0 pid=1424 comm=/usr/sbin/bluetoothd) interface=(unset) member=(unset) error name=(unset) requested_reply=0 destination=:1.10 (uid=0 pid=1414 comm=NetworkManager)) At what point does that failure come? This could be caused by recent (well, year-old) dbus policy changes for unrequested reply messages which I'm not 100% sure how to get fixed... walters; what could be the cause of this sort of thing again? The operative component here is requested_reply=0, and the policy is to reject unrequested replies. Often this is harmless because if a message wasn't expecting a reply, denying a reply shouldn't matter. If however the binding/code was setting no_reply AND actually expecting to process the reply, that's a bug in the calling code. I ran modem-manager with debug and here is the output: ** Message: (rfcomm0) opening serial device... ** (modem-manager:2090): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'ATICR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'Research In Motion BlackBerry IP ModemCRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+CPIN: READYCRLFCRLFOKCRLF' ** Message: (rfcomm0) closing serial device... ** Message: Generic: (tty/rfcomm0) WARNING: missing udev 'device' file ** Message: (rfcomm0) opening serial device... ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 claimed port rfcomm0 ** (modem-manager:2090): DEBUG: Added modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+CPIN: READYCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'CRLFOKCRLF' ** Message: (rfcomm0) closing serial device... ** (modem-manager:2090): DEBUG: Exported modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 as /org/freedesktop/ModemManager/Modems/0 ** Message: (rfcomm0) opening serial device... ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'ATZ E0 V1 +CMEE=1CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'CRLFERRORCRLF' ** (modem-manager:2090): DEBUG: Got failure code 100: Unknown error ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - disabled) ** Message: (rfcomm0) closing serial device... ** (modem-manager:2090): DEBUG: Removed modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 Looks like there is something else going on and the Blackberry rejected the connection? Like you found, it probably doesn't like +CMEE=1... guess we'll have to handle that somewhat differently in the generic plugin. Dan Is there some alternatives you would like me to test via minicom or equivalent? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
complex openvpn - can nm just launch?
I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. I've tried importing/exporting a tweaking, but the wizard thing just isn't flexible enough. (the xml-ization aka 'registry-ization' of just standard config files seems to bite me in various aspects of computing) I'd like to launch openvpn with my config file from nm. Is there a way? Short of that is there a way to make dbus or whatever think of I have network without launching from nm? Thanks! -Scott ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-Manager Trunk and Fedora 12
On Tue, 2010-04-06 at 10:56 -0400, Darren Albers wrote: On Tue, Apr 6, 2010 at 3:34 AM, Dan Williams d...@redhat.com wrote: On Thu, 2010-04-01 at 08:55 -0400, Darren Albers wrote: On Wed, Mar 31, 2010 at 10:02 AM, Colin Walters walt...@redhat.com wrote: - Dan Williams d...@redhat.com wrote: /var/log/messages: Mar 25 19:51:58 localhost dbus-daemon: Rejected send message, 2 matched rules; type=method_return, sender=:1.12 (uid=0 pid=1424 comm=/usr/sbin/bluetoothd) interface=(unset) member=(unset) error name=(unset) requested_reply=0 destination=:1.10 (uid=0 pid=1414 comm=NetworkManager)) At what point does that failure come? This could be caused by recent (well, year-old) dbus policy changes for unrequested reply messages which I'm not 100% sure how to get fixed... walters; what could be the cause of this sort of thing again? The operative component here is requested_reply=0, and the policy is to reject unrequested replies. Often this is harmless because if a message wasn't expecting a reply, denying a reply shouldn't matter. If however the binding/code was setting no_reply AND actually expecting to process the reply, that's a bug in the calling code. I ran modem-manager with debug and here is the output: ** Message: (rfcomm0) opening serial device... ** (modem-manager:2090): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+GCAP:CRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'ATICR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'Research In Motion BlackBerry IP ModemCRLFCRLFOKCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+CPIN: READYCRLFCRLFOKCRLF' ** Message: (rfcomm0) closing serial device... ** Message: Generic: (tty/rfcomm0) WARNING: missing udev 'device' file ** Message: (rfcomm0) opening serial device... ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 claimed port rfcomm0 ** (modem-manager:2090): DEBUG: Added modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- '+CPIN: READYCRLF' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'CRLFOKCRLF' ** Message: (rfcomm0) closing serial device... ** (modem-manager:2090): DEBUG: Exported modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 as /org/freedesktop/ModemManager/Modems/0 ** Message: (rfcomm0) opening serial device... ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'ATZ E0 V1 +CMEE=1CR' ** (modem-manager:2090): DEBUG: (rfcomm0): -- 'CRLFERRORCRLF' ** (modem-manager:2090): DEBUG: Got failure code 100: Unknown error ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - disabled) ** Message: (rfcomm0) closing serial device... ** (modem-manager:2090): DEBUG: Removed modem /sys/devices/pci:00/:00:1a.0/usb3/3-1 Looks like there is something else going on and the Blackberry rejected the connection? Like you found, it probably doesn't like +CMEE=1... guess we'll have to handle that somewhat differently in the generic plugin. Dan Is there some alternatives you would like me to test via minicom or equivalent? ATZ E0 V1 AT+CMEE=1 and see which of those two fail. As long as it's the AT+CMEE=1, we can deal with it easily. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: complex openvpn - can nm just launch?
On Tue, 2010-04-06 at 10:05 -0600, Scott Serr wrote: I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. Which options? Dan I've tried importing/exporting a tweaking, but the wizard thing just isn't flexible enough. (the xml-ization aka 'registry-ization' of just standard config files seems to bite me in various aspects of computing) I'd like to launch openvpn with my config file from nm. Is there a way? Short of that is there a way to make dbus or whatever think of I have network without launching from nm? Thanks! -Scott ___ 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: complex openvpn - can nm just launch?
On 04/06/2010 10:25 AM, Dan Williams wrote: On Tue, 2010-04-06 at 10:05 -0600, Scott Serr wrote: I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. Which options? Dan I suspect there will always be a new option to chase. Here is mine: dev tun remote 127.0.0.1 41927 tcp-client proto tcp-client ifconfig 192.168.56.2 192.168.56.1 route 0.0.0.0 128.0.0.0 route 128.0.0.0 128.0.0.0 socket-flags TCP_NODELAY ping 10 dhcp-option DNS 192.168.56.1 There is no encryption, data is sent in cleartext. This is appropriate for use with Azilink on Android phones. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: complex openvpn - can nm just launch?
On Tue, 2010-04-06 at 11:28 -0600, Scott Serr wrote: On 04/06/2010 10:25 AM, Dan Williams wrote: On Tue, 2010-04-06 at 10:05 -0600, Scott Serr wrote: I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. Which options? Dan I suspect there will always be a new option to chase. Probably, but at some point we reach the set of options that 95% of people use. There are seriously so many options with openvpn that it's not funny, and the program is completely incapable of auto-negotiating them, which is also not funny. It's downright sad. Here is mine: dev tun remote 127.0.0.1 41927 tcp-client proto tcp-client ifconfig 192.168.56.2 192.168.56.1 route 0.0.0.0 128.0.0.0 route 128.0.0.0 128.0.0.0 socket-flags TCP_NODELAY ping 10 dhcp-option DNS 192.168.56.1 There is no encryption, data is sent in cleartext. This is appropriate for use with Azilink on Android phones. The only thing I can see that's not yet supported is the no encryption part, which (not to be pedantic) isn't really a VPN. But I suppose that's something we can add. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
domainname in serviceproviders.xml
Hi. It looks like that nm is still not able to read bluetooth connections from system-connection files. I tested this sometimes but it does not work. So I'm looking for a workaround currently. Our users are not able to use their SIM cards with any APN. These SIM cards are configured by our provider to only allow to use our own private APN. So I'm modifying the following file: /usr/share/mobile-broadband-provider-info/serviceproviders.xml so the user can only select our APN configuration. My Problem is that the domain extension is ignored in this file. I tried domainmycompany.de/domain but that does not work. Can someone give me a hint? Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
domainname in serviceproviders.xml
Hi. It looks like that nm is still not able to read bluetooth connections from system-connection files. I tested this sometimes but it does not work. So I'm looking for a workaround currently. Our users are not able to use their SIM cards with any APN. These SIM cards are configured by our provider to only allow to use our own private APN. So I'm modifying the following file: /usr/share/mobile-broadband-provider-info/serviceproviders.xml so the user can only select our APN configuration. My Problem is that the domain extension is ignored in this file. I tried domainmycompany.de/domain but that does not work. Can someone give me a hint? Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.8 can't connect to PEAP
On Tue, 2010-03-30 at 16:23 -0400, Matthew Saltzman wrote: On Tue, 2010-03-30 at 13:11 -0700, Dan Williams wrote: On Mon, 2010-03-29 at 09:58 -0400, Matthew Saltzman wrote: I installed NetworkManager-1:0.8.0-4.git20100325.fc12.x86_64 from Fedora 12 updates-testing. After that, I was unable to connect to my PEAP-based wireless network at work. The new security screen has a checkbox for always prompt for user password, which was not in 0.7. Whether that is checked or not, attempts to enter the password and connect just keep repeatedly popping up the security screen with the password field blanked out. Interesting, I'll check that out, thanks. Also, a problem I have mentioned before where the connection fails to remember the location of its cert file across reboots persists in NM-0.8. And that one too. Is it the case that the cert file gets clear only when the connection fails and you are asked for a password? Yes, and in fact, only after rebooting (restarting NM or nm-applet, maybe?), AFAICT. I had the connection fail on its own (probably due to a WAP reset or some such) and the password dialect popped up with the cert file listed. I'm pretty sure pressing Connect reconnected with no other changes. And that the certificate is not correctly filled into the file chooser when the password window comes up? Yes, after reboot. The field is blank. I found and fixed the continuous asking for the password even when Always ask wasn't checked. I could not reproduce the missing CA certificate issue though. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: domainname in serviceproviders.xml
On Tue, 2010-04-06 at 20:43 +0200, Hans-Gerd van Schelve wrote: Hi. It looks like that nm is still not able to read bluetooth connections from system-connection files. I tested this sometimes but it does not work. So I'm looking for a workaround currently. Our users are not able to use their SIM cards with any APN. These SIM cards are configured by our provider to only allow to use our own private APN. So I'm modifying the following file: /usr/share/mobile-broadband-provider-info/serviceproviders.xml so the user can only select our APN configuration. My Problem is that the domain extension is ignored in this file. I tried domainmycompany.de/domain but that does not work. Can someone give me a hint? That file doesn't have anything to do with domain or anything. What are you trying to do here? serviceproviders.xml only handles APNs really (DNS is ignored since it's passed back from PPP). If you want to control the search domains, then you'll want modify the NM connection itself. If there's a problem with BT system connections, we should fix that... Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: complex openvpn - can nm just launch?
On 04/06/2010 12:10 PM, Dan Williams wrote: On Tue, 2010-04-06 at 11:28 -0600, Scott Serr wrote: On 04/06/2010 10:25 AM, Dan Williams wrote: On Tue, 2010-04-06 at 10:05 -0600, Scott Serr wrote: I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. Which options? Dan I suspect there will always be a new option to chase. Probably, but at some point we reach the set of options that 95% of people use. There are seriously so many options with openvpn that it's not funny, and the program is completely incapable of auto-negotiating them, which is also not funny. It's downright sad. Here is mine: dev tun remote 127.0.0.1 41927 tcp-client proto tcp-client ifconfig 192.168.56.2 192.168.56.1 route 0.0.0.0 128.0.0.0 route 128.0.0.0 128.0.0.0 socket-flags TCP_NODELAY ping 10 dhcp-option DNS 192.168.56.1 There is no encryption, data is sent in cleartext. This is appropriate for use with Azilink on Android phones. The only thing I can see that's not yet supported is the no encryption part, which (not to be pedantic) isn't really a VPN. But I suppose that's something we can add. Dan Thanks for the info Dan. On Ubuntu Lucid Beta, there are some issues saving other options. I was going to attempt to hack up the xml and take out the key/user/pass. Do you think this would work? I wonder how easy it would be to have an ad-hoc sort of connection in nm. Where nm would not care about much other that running a start and stop script and telling dbus networking is up. For Azilink users: If you wish to use dbus-aware apps like Empathy, I've been successful now with /etc/init.d/network-manager stop. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: complex openvpn - can nm just launch?
On Tue, 2010-04-06 at 14:31 -0600, Scott Serr wrote: On 04/06/2010 12:10 PM, Dan Williams wrote: On Tue, 2010-04-06 at 11:28 -0600, Scott Serr wrote: On 04/06/2010 10:25 AM, Dan Williams wrote: On Tue, 2010-04-06 at 10:05 -0600, Scott Serr wrote: I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. Which options? Dan I suspect there will always be a new option to chase. Probably, but at some point we reach the set of options that 95% of people use. There are seriously so many options with openvpn that it's not funny, and the program is completely incapable of auto-negotiating them, which is also not funny. It's downright sad. Here is mine: dev tun remote 127.0.0.1 41927 tcp-client proto tcp-client ifconfig 192.168.56.2 192.168.56.1 route 0.0.0.0 128.0.0.0 route 128.0.0.0 128.0.0.0 socket-flags TCP_NODELAY ping 10 dhcp-option DNS 192.168.56.1 There is no encryption, data is sent in cleartext. This is appropriate for use with Azilink on Android phones. The only thing I can see that's not yet supported is the no encryption part, which (not to be pedantic) isn't really a VPN. But I suppose that's something we can add. Dan Thanks for the info Dan. On Ubuntu Lucid Beta, there are some issues saving other options. I was going to attempt to hack up the xml and take out the key/user/pass. Do you think this would work? The routes and the DNS option would go into the IPv4 tab, which may not actually get imported by the current import code. This is basically like a static key connection, except without the key. I wonder how easy it would be to have an ad-hoc sort of connection in nm. Where nm would not care about much other that running a start and stop script and telling dbus networking is up. That doesn't really work automatically, for the most part, and it's also a security issue since openvpn runs as 'root' and you're basically giving it unfiltered commands which will also get run as root. In the end, it's not that hard to support additional options, but we need people willing to write the patches. I can't do everything at once of course, and while others (Huzaifa for example) have been very good about picking issues out of bugzilla and fixing them, this isn't one that's been reported before and thus we haven't looked at it yet... Random question though, what exactly is Azilink and what are you using it for? Dan For Azilink users: If you wish to use dbus-aware apps like Empathy, I've been successful now with /etc/init.d/network-manager stop. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Portuguese (pt_PT) Europe Translation
I always use software in English, but if it needed pt_PT (Portuguese Europe) translations, please feel free to nag me. Kindest Regards, Nelson Marques. -- Nelson Marques PGP Fingerprint: 53E1 731B 85A4 A098 8382 8CFF 1AC7 AF01 7717 8063 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
coding standards question
Hello, all.
This is my first post to this list. I'm Dave Loyall, from Omaha,
Nebraska, USA. :)
I intend to make a small modification to nm-applet and submit it
upstream. A client of mine requires a new feature, which I can
implement. I hope that others will be able to benefit from the change
as well.
The feature will allow administrators to set the default connection
scope for new connections to System. Users with appropriate
permissions can already create System Connections, but this feature
will allow them to do with without having to click edit and check the
available to all users box. (My client requires this, for purposes
of a smooth user experience on the systems he controls.)
So, I figure I can add key/value pair to the existing configuration
file. I'll model my code after plugin_get_hostname(SCPluginKeyfile
*plugin) in network-manager-0.8/system-settings/plugins/keyfile/plugin.c.
...Which brings me to my question. Why does plugin_get_hostname take
an SCPluginKeyfile as an argument? 'plugin' doesn't seem to be
touched inside this function. Is it used in a way that I'm not
familiar with?
Does the function I'll make need to take SCPluginKeyfile *plugin as
well--I mean, is this required by some interface spec?
For bonus points: Is my strategy sound? :)
Cheers, and thanks,
--Dave
For your convenience:
//snip from network-manager-0.8/system-settings/plugins/keyfile/plugin.c
static char *
plugin_get_hostname (SCPluginKeyfile *plugin)
{
GKeyFile *key_file;
char *hostname = NULL;
GError *error = NULL;
key_file = g_key_file_new ();
if (g_key_file_load_from_file (key_file, CONF_FILE,
G_KEY_FILE_NONE, error))
hostname = g_key_file_get_value (key_file, keyfile,
hostname, NULL);
else {
g_warning (Error parsing file '%s': %s, CONF_FILE,
error-message);
g_error_free (error);
}
g_key_file_free (key_file);
return hostname;
}
//end snip
//more snip from the same
static void
sc_plugin_keyfile_init (SCPluginKeyfile *plugin)
{
SCPluginKeyfilePrivate *priv = SC_PLUGIN_KEYFILE_GET_PRIVATE (plugin);
priv-hostname = plugin_get_hostname (plugin);
}
//end snip
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: complex openvpn - can nm just launch?
On Tue, 06 Apr 2010 09:25:44 -0700, Dan Williams wrote: On Tue, 2010-04-06 at 10:05 -0600, Scott Serr wrote: I have an openvpn config file that works fine with openvpn. (ubuntu lucid beta) As far as I can tell there is no way to create a like config in the nm openvpn editor. I can make one somewhat similar and export, but it doesn't look enough like mine to work. Which options? Hi Dan this is my (short) list of missing options/features - support for external dhcp on the server side, normally I configure openvpn server to push only data that I can't provide via dhcp server. So ip/mask/dns is taken from dhcp and additional route from openvpn This configuration works perfectly for windows machine, on certain customer I have a dedicated openvpn only for me because I can't use normal openvpn configuration :-( - support for multiple remote server Dan I've tried importing/exporting a tweaking, but the wizard thing just isn't flexible enough. (the xml-ization aka 'registry-ization' of just standard config files seems to bite me in various aspects of computing) I'd like to launch openvpn with my config file from nm. Is there a way? Short of that is there a way to make dbus or whatever think of I have network without launching from nm? Thanks! -Scott ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Cordiali saluti Alessandro Bono ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Urdu and Urdu Pakistan Translation of network-manager-applet
On Wed, Apr 7, 2010 at 12:01 AM, makkiabufa...@aol.com wrote: hi Urdu and Urdu Pakistan Translation of network-manager-applet-0.8 are Attached. To submit translations to GNOME application, you need to go through the GNOME Translation Team (GTP) of your language, Urdu in your case. Read http://live.gnome.org/TranslationProject/ for more on the GNOME Translation Project. The mailing list for translation discussions is gnome-i18n, http://mail.gnome.org/mailman/listinfo/gnome-i18n According to http://l10n.gnome.org/languages/ there is an Urdu team, however there is no Urdu Pakistan team. Is it really necessary to have Urdu and Urdu-Pakistan? This is something to discuss with the other team members. The Urdu team is at http://l10n.gnome.org/languages/ur/ which shows the current team coordinator and his contact details. You need to contact the team coordinator to get your translations added to GNOME. Contact gnome-i18n in case he is not responding. Finally, you add the translation to http://l10n.gnome.org/vertimus/network-manager-applet/master/po/ur and either your team coordinator or another member from the GTP will upload it to git.gnome.org. Simos -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.8 can't connect to PEAP
On Tue, 2010-04-06 at 13:13 -0700, Dan Williams wrote: On Tue, 2010-03-30 at 16:23 -0400, Matthew Saltzman wrote: On Tue, 2010-03-30 at 13:11 -0700, Dan Williams wrote: On Mon, 2010-03-29 at 09:58 -0400, Matthew Saltzman wrote: I installed NetworkManager-1:0.8.0-4.git20100325.fc12.x86_64 from Fedora 12 updates-testing. After that, I was unable to connect to my PEAP-based wireless network at work. The new security screen has a checkbox for always prompt for user password, which was not in 0.7. Whether that is checked or not, attempts to enter the password and connect just keep repeatedly popping up the security screen with the password field blanked out. Interesting, I'll check that out, thanks. Also, a problem I have mentioned before where the connection fails to remember the location of its cert file across reboots persists in NM-0.8. And that one too. Is it the case that the cert file gets clear only when the connection fails and you are asked for a password? Yes, and in fact, only after rebooting (restarting NM or nm-applet, maybe?), AFAICT. I had the connection fail on its own (probably due to a WAP reset or some such) and the password dialect popped up with the cert file listed. I'm pretty sure pressing Connect reconnected with no other changes. And that the certificate is not correctly filled into the file chooser when the password window comes up? Yes, after reboot. The field is blank. I found and fixed the continuous asking for the password even when Always ask wasn't checked. That's not in NM-0.8.0-4.git20100325.fc12 I suppose. I'll look forward to testing the next update in F12 updates-testing. Thanks! I could not reproduce the missing CA certificate issue though. One thing that occurred to me: I'm using a pem cert. It used to be that you needed a der cert, and the problem doesn't seem to occur in an RHEL5 installation I set up today (although it needed the der). I can't recall what version of NM that was. I will check tomorrow if using the der gives a different result. Dan -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
