Re: NO MORE MAIL PLEASE!
NO MORE MAIL PLEASE! You have to unsubscribe yourself in order to not receive any more mail. Please visit http://mail.gnome.org/mailman/listinfo/networkmanager-list Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: system-connection for WWAN not working
Well, I am not Dan, and I am not *sure*, but this part of the log of failed session does not seem to support this theory: rcvd [CHAP Challenge id=0x1 ae19e43f460f5298ca0a6933246e4335, name = UMTS_CHAP_SRVR] ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... ** Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager sent [CHAP Response id=0x1 d29bfa4e9cab3171192695c3c3d62cf6, name = username] rcvd [CHAP Success id=0x1 ] CHAP authentication succeeded Could the radius log be from another session, that failed for a different reason? This is possible but during the time from the Logfiles I really did some tests. If you think it can be helpful, I will try to capture the logs from a complete session again NM and Radius. But let me put it together again: - T-Mobile Internet connection is OK when configured as User connection as well as system-connection - MyWWAN works only when configured as User connection. When using this as system-connection connection don't come up. I compared T-Mobile and MyWWAN system-connection files from /etc/NetworkManager/system-connections and they are different only in password, username and apn (as well as uuid and id) -- Hans-Gerd Looking closer at the logs, side by side, shows that the difference starts *after* successful authentication, here: BAD: sent [IPCP ConfReq id=0x1 compress VJ 0f 01 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-dns2 0.0.0.0] GOOD: sent [IPCP ConfReq id=0x1 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-dns2 0.0.0.0] I cannot tell what exactly goes on here, though... Don't know the PPP protocol well enough. Eugene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] supplicant: switched to new supplicant's DBus API
Patch resent with a bug fix. There was a bug in adding a blob procedure, witch caused to fail when adding an already added blob. Fixed. Now NM tries to remove each blob before adding. Corrected patch is below: NetworkManager now uses the new DBus API of wpa_supplicant. It changes interfaces and methods and signals names to, change some signals to PropertyChanged signal and some method calls to property Get calls in order to fit new API. General principle of operation supplicant manager is not changed. --- src/NetworkManagerAP.c | 14 +- src/nm-device-wifi.c |2 - src/supplicant-manager/nm-supplicant-interface.c | 579 +++--- src/supplicant-manager/nm-supplicant-interface.h |3 +- src/supplicant-manager/nm-supplicant-manager.c |2 +- src/supplicant-manager/nm-supplicant-manager.h |6 +- 6 files changed, 308 insertions(+), 298 deletions(-) diff --git a/src/NetworkManagerAP.c b/src/NetworkManagerAP.c index 9b95924..274862a 100644 --- a/src/NetworkManagerAP.c +++ b/src/NetworkManagerAP.c @@ -380,7 +380,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) if (G_VALUE_HOLDS_BOXED (variant)) { GArray *array = g_value_get_boxed (variant); - if (!strcmp (key, ssid)) { + if (!strcmp (key, SSID)) { guint32 len = MIN (IW_ESSID_MAX_SIZE, array-len); GByteArray * ssid; @@ -396,7 +396,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) g_byte_array_append (ssid, (const guint8 *) array-data, len); nm_ap_set_ssid (ap, ssid); g_byte_array_free (ssid, TRUE); - } else if (!strcmp (key, bssid)) { + } else if (!strcmp (key, BSSID)) { struct ether_addr addr; if (array-len != ETH_ALEN) @@ -404,7 +404,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) memset (addr, 0, sizeof (struct ether_addr)); memcpy (addr, array-data, ETH_ALEN); nm_ap_set_address (ap, addr); - } else if (!strcmp (key, wpaie)) { + } else if (!strcmp (key, WPAIE)) { guint8 * ie = (guint8 *) array-data; guint32 flags = nm_ap_get_wpa_flags (ap); @@ -412,7 +412,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) return; flags = nm_ap_add_security_from_ie (flags, ie, array-len); nm_ap_set_wpa_flags (ap, flags); - } else if (!strcmp (key, rsnie)) { + } else if (!strcmp (key, RSNIE)) { guint8 * ie = (guint8 *) array-data; guint32 flags = nm_ap_get_rsn_flags (ap); @@ -424,16 +424,16 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) } else if (G_VALUE_HOLDS_INT (variant)) { gint32 int_val = g_value_get_int (variant); - if (!strcmp (key, frequency)) { + if (!strcmp (key, Frequency)) { nm_ap_set_freq (ap, (guint32) int_val); - } else if (!strcmp (key, maxrate)) { + } else if (!strcmp (key, MaxRate)) { /* Supplicant reports as b/s, we use Kb/s internally */ nm_ap_set_max_bitrate (ap, int_val / 1000); } } else if (G_VALUE_HOLDS_UINT (variant)) { guint32 val = g_value_get_uint (variant); - if (!strcmp (key, capabilities)) { + if (!strcmp (key, Capabilities)) { if (val IEEE80211_CAP_ESS) { nm_ap_set_mode (ap, NM_802_11_MODE_INFRA); } else if (val IEEE80211_CAP_IBSS) { diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c index 6307ae6..b83e34d 100644 --- a/src/nm-device-wifi.c +++ b/src/nm-device-wifi.c @@ -208,7 +208,6 @@ static void supplicant_iface_scanned_ap_cb (NMSupplicantInterface * iface, NMDeviceWifi * self); static void supplicant_iface_scan_request_result_cb (NMSupplicantInterface * iface, - gboolean success, NMDeviceWifi * self); static void supplicant_iface_scan_results_cb (NMSupplicantInterface * iface, @@ -1782,7 +1781,6 @@ cancel_pending_scan (NMDeviceWifi *self) static void supplicant_iface_scan_request_result_cb (NMSupplicantInterface *iface, - gboolean success, NMDeviceWifi *self) { if (can_scan (self)) diff --git
Re: [PATCH] supplicant: switched to new supplicant's DBus API
One more bug fix, I hope it's the last one. Fixed reading AP properties while calculating signal strength from wpa_supplicant. Corrected patch is below: NetworkManager now uses the new DBus API of wpa_supplicant. It changes interfaces and methods and signals names to, change some signals to PropertyChanged signal and some method calls to property Get calls in order to fit new API. General principle of operation supplicant manager is not changed. --- src/NetworkManagerAP.c | 14 +- src/nm-device-wifi.c | 18 +- src/supplicant-manager/nm-supplicant-interface.c | 579 +++--- src/supplicant-manager/nm-supplicant-interface.h |3 +- src/supplicant-manager/nm-supplicant-manager.c |2 +- src/supplicant-manager/nm-supplicant-manager.h |6 +- 6 files changed, 316 insertions(+), 306 deletions(-) diff --git a/src/NetworkManagerAP.c b/src/NetworkManagerAP.c index 9b95924..274862a 100644 --- a/src/NetworkManagerAP.c +++ b/src/NetworkManagerAP.c @@ -380,7 +380,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) if (G_VALUE_HOLDS_BOXED (variant)) { GArray *array = g_value_get_boxed (variant); - if (!strcmp (key, ssid)) { + if (!strcmp (key, SSID)) { guint32 len = MIN (IW_ESSID_MAX_SIZE, array-len); GByteArray * ssid; @@ -396,7 +396,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) g_byte_array_append (ssid, (const guint8 *) array-data, len); nm_ap_set_ssid (ap, ssid); g_byte_array_free (ssid, TRUE); - } else if (!strcmp (key, bssid)) { + } else if (!strcmp (key, BSSID)) { struct ether_addr addr; if (array-len != ETH_ALEN) @@ -404,7 +404,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) memset (addr, 0, sizeof (struct ether_addr)); memcpy (addr, array-data, ETH_ALEN); nm_ap_set_address (ap, addr); - } else if (!strcmp (key, wpaie)) { + } else if (!strcmp (key, WPAIE)) { guint8 * ie = (guint8 *) array-data; guint32 flags = nm_ap_get_wpa_flags (ap); @@ -412,7 +412,7 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) return; flags = nm_ap_add_security_from_ie (flags, ie, array-len); nm_ap_set_wpa_flags (ap, flags); - } else if (!strcmp (key, rsnie)) { + } else if (!strcmp (key, RSNIE)) { guint8 * ie = (guint8 *) array-data; guint32 flags = nm_ap_get_rsn_flags (ap); @@ -424,16 +424,16 @@ foreach_property_cb (gpointer key, gpointer value, gpointer user_data) } else if (G_VALUE_HOLDS_INT (variant)) { gint32 int_val = g_value_get_int (variant); - if (!strcmp (key, frequency)) { + if (!strcmp (key, Frequency)) { nm_ap_set_freq (ap, (guint32) int_val); - } else if (!strcmp (key, maxrate)) { + } else if (!strcmp (key, MaxRate)) { /* Supplicant reports as b/s, we use Kb/s internally */ nm_ap_set_max_bitrate (ap, int_val / 1000); } } else if (G_VALUE_HOLDS_UINT (variant)) { guint32 val = g_value_get_uint (variant); - if (!strcmp (key, capabilities)) { + if (!strcmp (key, Capabilities)) { if (val IEEE80211_CAP_ESS) { nm_ap_set_mode (ap, NM_802_11_MODE_INFRA); } else if (val IEEE80211_CAP_IBSS) { diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c index 6307ae6..ab3b138 100644 --- a/src/nm-device-wifi.c +++ b/src/nm-device-wifi.c @@ -107,7 +107,7 @@ typedef enum { } NMWifiError; #define NM_WIFI_ERROR (nm_wifi_error_quark ()) -#define NM_TYPE_WIFI_ERROR (nm_wifi_error_get_type ()) +#define NM_TYPE_WIFI_ERROR (nm_wifi_error_get_type ()) typedef struct SupplicantStateTask { NMDeviceWifi *self; @@ -156,7 +156,7 @@ struct _NMDeviceWifiPrivate { NMAccessPoint * current_ap; guint32 rate; gboolean enabled; /* rfkilled or not */ - + glong scheduled_scan_time; guint8scan_interval; /* seconds */ guint pending_scan_id; @@ -208,7 +208,6 @@ static void supplicant_iface_scanned_ap_cb (NMSupplicantInterface * iface, NMDeviceWifi * self); static void supplicant_iface_scan_request_result_cb (NMSupplicantInterface * iface, -
Re: nm-applet stopped connecting to wired network
On Thu, 2009-11-19 at 00:18 +0100, Daniel Fetchinson wrote: Hi folks, I have a super weird situation on my Sony VAIO VGN-FZ240E: I have Fedora 8 which ships network manager 0.7.0-0.5.svn3030 and until yesterday everything has been working perfectly well, nm-applet connected to both wired and wireless networks without a problem. And the strange thing is that I didn't do anything, no new installs, no upgrades, absolutely nothing (that I know of). What's the output of 'nm-tool' when that command is run in a terminal, when you're experiencing the problem? Thanks for the answer, so nm-tool says this: NetworkManager Tool State: disconnected - Device: eth0 Type: Wired Driver:sky2 Active:no HW Address:00:1A:80:49:CF:34 Capabilities: Supported: yes Carrier Detect: yes Speed: 100 Mb/s Wired Settings - Device: wlan0 Type: 802.11 Wireless Driver:iwl4965 Active:no HW Address:00:13:E8:87:8E:4F Capabilities: Supported: yes Wireless Settings WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points I noticed the line 'State: disconnected' however right now I'm connected, I'm sending this email :) Again I had to manually 'dhclient eth0' which results in a working connection, only nm-applet thinks that somehow there is no wired network connection. Right, because the connection wasn't made through NetworkManager, and thus the information about the connection isn't available to NEtworkManager because dhclient wasn't run with the right callout script, etc. Can you grab /var/log/messages for me? That will show what NM thinks is going on. It may be a carrier change race that was fixed in F10 and higher and the logs might help us figure that out. My reply with the attached /var/log/messages got held up for moderation because it was too big so I've uploaded the /var/log/messages file to http://danielfetchinson.appspot.com/ I think it's more these: Nov 17 02:29:48 localhost NetworkManager: Missing required value 'name'. Nov 17 02:29:48 localhost NetworkManager: 'connection' setting not present. I don't know what the cause of that could be off the top of my head, but you said you're running svn3030, which is from Sat Oct 27 2007. That's really, really old :) The latest NetworkManager available for Fedora 8 is: NetworkManager-0.7.0-0.12.svn4326.fc8 From which repo is this available? yum tells me no upgrades are available. My enabled repos are: fedora, fedora-updates, livna. It looks like the updates have been cleared from the mirrors since F8 has been unsupported for a year already. You have to play roulette to find a mirror that has them, and I got lucky when I tried: http://mirror.steadfast.net/fedora//updates/8/ None of the other mirrors have F-8 anymore. Assuming you aren't running a 64-bit install (if you are, replace i386 with x86_64 as appropriate), install this RPM with rpm -Uhv filename: http://mirror.steadfast.net/fedora//updates/8/i386.newkey/fedora-release-8-6.transition.noarch.rpm Then update your fedora.repo and fedora-updates.repo files to point to the steadfast.net mirror. The sections should look like this: [updates] name=Fedora $releasever - $basearch - Updates failovermethod=priority baseurl=http://mirror.steadfast.net/fedora//updates/$releasever/$basearch.newkey/ #mirrorlist= (and the same for fedora.repo) And then 'yum upgrade NetworkManager* Thanks Dan, I've done all of this, NetworkManager* is at the latest fedora 8 version. However this didn't solve the problem, the only difference I'm seeing is that the nm-applet icon that showed no connection before (static icon) is now an animated icon as if it were trying to connect but couldn't. Again clicking the 'Wired network' radio button doesn't do anything. The relevant section of /var/log/messages is this, it's full of suspicious items from NetworkManager, I'm pretty sure something is screwed up with gconf connections and it's not the fault of NetworkManager itself. As I've said everything was working everywhere (home, office, 2 different continents, about 5 countries :)) in the last 2 years: Nov 18 23:57:24 localhost acpid: starting up Nov 18 23:57:25 localhost gpm[1991]: *** info [startup.c(95)]: Nov 18 23:57:25 localhost gpm[1991]: Started gpm successfully. Entered daemon mode. Nov 18 23:57:28
How to stop wireless autostarting at boot?
I use ubuntu 9.10 and when i boot wireless always starts. Is there a way to disable wireless autostarting using some network manager option or configuration? Thanks in advance, Panayiotis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to stop wireless autostarting at boot?
On Thu, Nov 19, 2009 at 6:15 PM, Panayiotis Mousouliotis pmous...@gmail.com wrote: I use ubuntu 9.10 and when i boot wireless always starts. Is there a way to disable wireless autostarting using some network manager option or configuration? Thanks in advance, Panayiotis Do you want to start with Wireless disabled completely or just not autoconnect to AP's? If you edit the profile for your wireless networks you can uncheck connect automatically to make all networks manual connections. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to stop wireless autostarting at boot?
I would like to start with Wireless disabled completely and enable it from network manager whenever i need it. Now, i have blacklisted the wireless module (in /etc/modprobe.d/blacklist.conf) and i make a script that executes modprobe iwlagn in order to start wireless. Loading the module makes wireless to start in network manager in my acer 5920g latop. And i would like to know if there is a simpler and more elegant way to do this.. maybe using network manager. Panayiotis On Fri, Nov 20, 2009 at 1:45 AM, Darren Albers dalb...@gmail.com wrote: On Thu, Nov 19, 2009 at 6:15 PM, Panayiotis Mousouliotis pmous...@gmail.com wrote: I use ubuntu 9.10 and when i boot wireless always starts. Is there a way to disable wireless autostarting using some network manager option or configuration? Thanks in advance, Panayiotis Do you want to start with Wireless disabled completely or just not autoconnect to AP's? If you edit the profile for your wireless networks you can uncheck connect automatically to make all networks manual connections. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to stop wireless autostarting at boot?
I use this in /etc/rc.local: dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager \ /org/freedesktop/NetworkManager org.freedesktop.DBus.Properties.Set \ string:org.freedesktop.NetworkManager string:WirelessEnabled variant:boolean:false /dev/null ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to stop wireless autostarting at boot?
There was a patch submitted to the master branch around a month ago. See here: http://www.mail-archive.com/networkmanager-list@gnome.org/msg14215.html I guess it will be in a distribution near you soon :) Graham 2009/11/20 Panayiotis Mousouliotis pmous...@gmail.com I would like to start with Wireless disabled completely and enable it from network manager whenever i need it. Now, i have blacklisted the wireless module (in /etc/modprobe.d/blacklist.conf) and i make a script that executes modprobe iwlagn in order to start wireless. Loading the module makes wireless to start in network manager in my acer 5920g latop. And i would like to know if there is a simpler and more elegant way to do this.. maybe using network manager. Panayiotis On Fri, Nov 20, 2009 at 1:45 AM, Darren Albers dalb...@gmail.com wrote: On Thu, Nov 19, 2009 at 6:15 PM, Panayiotis Mousouliotis pmous...@gmail.com wrote: I use ubuntu 9.10 and when i boot wireless always starts. Is there a way to disable wireless autostarting using some network manager option or configuration? Thanks in advance, Panayiotis Do you want to start with Wireless disabled completely or just not autoconnect to AP's? If you edit the profile for your wireless networks you can uncheck connect automatically to make all networks manual connections. ___ 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
using head -n 1 instead head -1?
Hi all, Not sure this has been mentioned before? NM0.7.1.998 configure script when check intltool with: INTLTOOL_APPLIED_VERSION=`intltool-update --version | head -1 | cut -d -f3` It use head -1. Better using head -n 1 instead? head -1 will get error in some environment. head: `-1' option is obsolete; use `-n 1' and make the configure failed. So in the m4/intltool.m4. Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How nm-modem-probe work?
Hi all, I have a HuaWei EM770 modem. Through add rules in udev I can make NM0.7.1.998 found it and work. But I have to set the ID_NM_MODEM_GSM=1 in the rules like 77-nm-zte-port-types.rules. This make udevadm_get_modem_capabilities(Do not have libudev support) return correct bits. But in 77-nm-probe-modem-capabilities.rules, it does not set any related environment value and just call nm-modem-probe instead. I suppose nm-modem-probe set related environment value? But from the codes nm-modem-probe.c, It seems not. How this work? Need libudev support? Thank! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list