Mark Juszczec wants to stay in touch on LinkedIn

[Mark Juszczec]

LinkedIn
Mark Juszczec requested to add you as a connection on LinkedIn:
--

Trey,

I'd like to add you to my professional network on LinkedIn.

- Mark Juszczec

Accept invitation from Mark Juszczec
http://www.linkedin.com/e/q0zYBr_CyGlVYKCIXGJ1Nr_O3Wl7Q1_du08bl9picfJd/blk/I1939615416_2/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYOnPoNd3kNdzAPej59bRhItTxUkRlCbPoOe3cSdPwVcj4LrCBxbOYWrSlI/EML_comm_afe/

View invitation from Mark Juszczec
http://www.linkedin.com/e/q0zYBr_CyGlVYKCIXGJ1Nr_O3Wl7Q1_du08bl9picfJd/blk/I1939615416_2/39vdz4Qdj4SejcVckALqnpPbOYWrSlI/svi/
 
--

DID YOU KNOW LinkedIn can help you find the right service providers using 
recommendations from your trusted network? Using LinkedIn Services, you can 
take the risky guesswork out of selecting service providers by reading the 
recommendations of credible, trustworthy members of your network. 
http://www.linkedin.com/e/svp/inv-25/

 
--
(c) 2010, LinkedIn Corporation___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Make NM respect manual setting in ifupdown

[Okkel]

-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:

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-
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 
+// 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 
+// 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 
+// Make ifupdown plugin respect manual setting
+#define NM_SETTING_MANUAL_SETTING_NAME  "manual"
+
 typedef struct _SCPluginIfupdown SCPluginIfupdown;
 typedef struct _SCPluginIfupdownClass SCPluginIfupdownClass;
 


nm-manual.patch.sig
Description: PGP signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Segfault

[David Richfield]

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:   (wlan12): device
state change: 8 -> 3 (reason 38)
or
Apr  4 08:05:15 davelaptop NetworkManager: 
(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,

-- 
David Richfield
e^(πi)+1=0
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list