Re: Problem Connecting to Mobile Broadband
On Thu, 2011-02-10 at 08:33 +0800, ms zaryna wrote: > Hi, > I'm running Ubuntu 10.10 on my laptop, and been using network manager > for couple of years. It's been working just fine until several days > ago. I'm using mobile broadband with USB modem(Vodafone K-3565-Z), and > it was able to detect and connect to internet ok, but then after like > 2 minutes, it lost the connection. I have to keep plug off my modem > and plug it back to get the connection. The worst thing is it crashed > my laptop, I got black screen and I can't seem to do anything other > than reboot. I already made a report to my internet provider company, > which will take 3 days at least to figure out if there is something > wrong with my internet connection. Now I get connected ok, but I don't > think the problem would just disappear. Hope someone can help. Thanks To help you out we need see logs, on Ubuntu I think that /var/log/syslog is the best log , but you may have other on /var/log. We need to see if pppd die , and try find out if it is a ppp problem, or if it is usb problem , see dmesg , type dmesg > dmesg.txt after crash and see you you have anything new on end of dmesg.txt. USB modem k-2565-Z was worked before ? and send lsusb -v after plug your modem , to know what device we are talking about. you may should open a bug on https://bugzilla.gnome.org/browse.cgi?product=NetworkManager with all details ask before to tack down the problem. Regards, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problem Connecting to Mobile Broadband
Hi, I'm running Ubuntu 10.10 on my laptop, and been using network manager for couple of years. It's been working just fine until several days ago. I'm using mobile broadband with USB modem(Vodafone K-3565-Z), and it was able to detect and connect to internet ok, but then after like 2 minutes, it lost the connection. I have to keep plug off my modem and plug it back to get the connection. The worst thing is it crashed my laptop, I got black screen and I can't seem to do anything other than reboot. I already made a report to my internet provider company, which will take 3 days at least to figure out if there is something wrong with my internet connection. Now I get connected ok, but I don't think the problem would just disappear. Hope someone can help. Thanks. -- mszaryna ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On 09.02.2011 18:40, Dan Williams wrote: In current NM 0.8.x git, if you uncheck "Enable Wireless" from the menu, NM writes that to the state file. That will then be in-force until you re-check "Enable Wireless", even across reboots. This takes precedence over rfkill because it was an explicit user choice to disable wifi. This fix was included in NM 0.8.2. I don't think we should be relying on rfkill here, because then it's simply magic what happens on reboot. Some laptops expose multiple rfkill "switches" in the kernel, others expose one, some chain them together, etc. It's a big mess really, and trying to rely on the kernel behavior here isn't going to help much. Instead, I think it's a lot clearer that "If you turn off wifi it stays disabled til you turn it back on". Or? I think there are multiple issues in here. The one that I've mentioned in the original thread and you've commented about may be triggered by the bug that I've replied. So with NM 0.8.2 on my Toshiba Portege R700 (iwlagn, exposing only a soft rfkill which is correctly turning on/off on keypress), when I sw-kill the radio, this is correctly detected by NM. The "Enable Wireless" gets unchecked and WirelessEnabled=false is written to the state file. But when I unblock, NM detects this to some point (looking at the debugged outputs and the code) but doesn't update the state file and doesn't enable the wireless networking. So one should explicitly check the "enable wireless" every time after unblocking the rfkill. I think this should be fixed. I'd like to debug more but I'm really getting lost in the glib/gobject mechanisms and NM code which contains a lot of abstraction/callback stuff really hard to follow :( -- Pardus Linux http://www.pardus.org.tr/eng ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can't get address when two DHCP servers
On Wed, 2011-02-09 at 16:47 +, Marc Herbert wrote: > Le 09/02/2011 15:39, Shawn J. Goff a écrit : > > I'm on a network with two DHCP servers and can't connect using Network > > Manager. I performed a Wireshark capture and saw a DHCP request from me > > followed by a DHCP ack from one server and a DHCP nak from the other. I > > did the same thing with dhclient and saw the exact same packets, but > > then dhclient went ahead and added the address to the interface and I'm > > connected. > > > > Is this a bug in NM? > > It is a bug in your network, you simply cannot have two independent > and concurrent DHCP servers in the same broadcast segment. When this > is the case anything can happen. > > Are you actually interested in being assigned a random subnet? (or > worse: in address clashes?) Yeah, certainly bad network setup. But I thought dhclient would take the address of the first DHCP broadcast reply it received (which is of course random) and then switch to unicast after that, which could help work around the issue. But in the end, yeah, two DHCP servers on the same segment is kinda wrong. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: rt3070sta not controllable with networkmanager
On Sat, 2011-02-05 at 22:00 -0800, Dan O'Connor wrote: > Can you clarify what I need to do in my driver's config.mk file? The > only reference to network manager I saw was the following: > > > > # Support Native WpaSupplicant for Network Maganger [sic] > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y Correct, because only with that code does the following block happen: #ifdef NATIVE_WPA_SUPPLICANT_SUPPORT /* for supporting Network Manager. * Set the sysfs physical device reference for the network logical device if set prior to registration will * cause a symlink during initialization. */ #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)) SET_NETDEV_DEV(net_dev, &(usb_dev->dev)); #endif #endif /* NATIVE_WPA_SUPPLICANT_SUPPORT */ Strong work, Ralink. At least they make the effort for cfg80211 support though. It eludes my why this is an option, since every other driver in the Linux kernel is expected to set up sysfs device links correctly. Dan > > > I have not tried the rt2x00 driver, the wiki main page does not > mention my card, but I guess it is similar enough that it should work? > > > > Thanks, > dan > > > On Sat, Feb 5, 2011 at 1:40 PM, Steev Klimaszewski > wrote: > On Fri, Feb 4, 2011 at 3:30 AM, Dan O'Connor > wrote: > > Greetings, > > > > I have an rt3070sta based wifi usb adapter. I've actually > got it working, > > but I have to manually connect it to the correct ap (using > ifconfig, > > iwconfig, and dhcpcd) and cannot use NetworkManager. When > starting > > NetworkManager --no-daemon I get the following output: > > NetworkManager: starting... > > NetworkManager: modem-manager is now available > > > > (NetworkManager:5268): GLib-CRITICAL **: g_error_free: > assertion `error != > > NULL' failed > > NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red > Hat, Inc. To > > report bugs please use the NetworkManager mailing list. > > NetworkManager: WiFi enabled by radio killswitch; > enabled by state > > file > > NetworkManager: WWAN enabled by radio killswitch; > enabled by state > > file > > NetworkManager: Ignoring insecure configuration file > > > > '/etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0' > > NetworkManager: (eth0): carrier is OFF > > NetworkManager: (eth0): new Ethernet device (driver: > 'r8169') > > NetworkManager: (eth0): exported as > > /org/freedesktop/NetworkManager/Devices/0 > > NetworkManager: (eth0): now managed > > NetworkManager: (eth0): device state change: 1 -> 2 > (reason 2) > > NetworkManager: (eth0): preparing device. > > NetworkManager: (eth0): deactivating device (reason: > 2). > > NetworkManager: Added default wired connection 'Auto eth0' > for > > /sys/devices/pci:00/:00:1c.6/:08:00.0/net/eth0 > > NetworkManager: > device_creator(): /sys/devices/virtual/net/ra0: > > couldn't determine device driver; ignoring... > > * status: started > > NetworkManager: default_adapter_cb(): bluez error > getting default > > adapter: The name org.bluez was not provided by any .service > files > > > > The only important/unexpected line as far as I can tell is > that it couldn't > > determine the device driver for ra0, my wifi device. It > seems odd to me that > > this device is in a "virtual" device folder, is that part of > the problem? > > I'm at a total loss as to how NetworkManager is expecting to > relate the > > device to its driver. > > > > The distro I'm using is Gentoo, and I configured the kernel > myself. I also > > compiled the wifi driver myself (even had to make some > modifications to get > > it to compile.. nothing major, just update some function > names and add a > > license tag). > > I'm not sure what other info would be helpful in solving > this problem, I > > will try to be prompt with any requests for more > information. > > > > Thanks, > > Dan O. > > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > You need to turn on Network Manager support in the config.mk > file. > Out of curiosity, is rt2x00 not working for you, or is it just > not > stable enough? > > ___ > network
Re: [PATCH 2/2] src/main.c: Fix RFKILL logging domain
On Mon, 2011-02-07 at 22:45 +0200, Ozan Çağlayan wrote:
> Correct logging domain for RFKILL is RFKILL not RKILL.
Pushed:
e9c8ba4e3dde7332fb1002fa54cda93166aa04cb (master)
49bdcc31bed237619aa28c814ee52e371c79aada (0.8.x)
Thanks!
Dan
> Also fix the man page.
> ---
> man/NetworkManager.conf.5.in |2 +-
> src/main.c |2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man/NetworkManager.conf.5.in b/man/NetworkManager.conf.5.in
> index a45adde..2d7a9e8 100644
> --- a/man/NetworkManager.conf.5.in
> +++ b/man/NetworkManager.conf.5.in
> @@ -160,7 +160,7 @@ from earlier levels; thus setting the log level to INFO
> also logs error and
> warning messages.
> .TP
> .B domains=\fI,, ...\fP
> -The following log domains are available: [NONE, HW, RKILL, ETHER, WIFI, BT,
> MB,
> +The following log domains are available: [NONE, HW, RFKILL, ETHER, WIFI, BT,
> MB,
> DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, DNS, VPN, SHARING,
> SUPPLICANT,
> USER_SET, SYS_SET, SUSPEND, CORE, DEVICE, OLPC, WIMAX]. When "NONE" is
> given by
> itself, logging is disabled. MB = Mobile Broadband, USER_SET = user settings
> diff --git a/src/main.c b/src/main.c
> index 1e3db21..211a5b9 100644
> --- a/src/main.c
> +++ b/src/main.c
> @@ -482,7 +482,7 @@ main (int argc, char *argv[])
> { "plugins", 0, 0, G_OPTION_ARG_STRING, &plugins, "List of
> plugins separated by ','", "plugin1,plugin2" },
> { "log-level", 0, 0, G_OPTION_ARG_STRING, &log_level, "Log
> level: one of [ERR, WARN, INFO, DEBUG]", "INFO" },
> { "log-domains", 0, 0, G_OPTION_ARG_STRING, &log_domains,
> - "Log domains separated by ',': any combination of
> [NONE,HW,RKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,WIFI_SCAN,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,USER_SET,SYS_SET,SUSPEND,CORE,DEVICE,OLPC]",
> + "Log domains separated by ',': any combination of
> [NONE,HW,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,WIFI_SCAN,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,USER_SET,SYS_SET,SUSPEND,CORE,DEVICE,OLPC]",
> "HW,RFKILL,WIFI" },
> {NULL}
> };
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH 1/2] logging: Strip '\n' at the end of syslog() calls
On Mon, 2011-02-07 at 22:45 +0200, Ozan Çağlayan wrote:
> syslog already ensures that the messages are splitted by \n
> boundaries. Appending another \n in NM pollutes the logging:
Pushed:
90493585795d8b60eab91bd1ed359d61b57617c6 (master)
251731ef5b17394fb0e99e8636672b9e6a5bb404 (0.8.4)
Thanks!
Dan
> Feb 7 22:00:55 2011 NetworkManager[890]: ...
>
> Feb 7 22:00:56 2011 NetworkManager[890]: ...
>
> Feb 7 22:00:57 2011 NetworkManager[890]: ...
>
> etc.
> ---
> src/logging/nm-logging.c |8
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/src/logging/nm-logging.c b/src/logging/nm-logging.c
> index 01bbb36..84cf16f 100644
> --- a/src/logging/nm-logging.c
> +++ b/src/logging/nm-logging.c
> @@ -237,14 +237,14 @@ void _nm_log (const char *loc,
>
> if ((log_level & LOGL_DEBUG) && (level == LOGL_DEBUG)) {
> g_get_current_time (&tv);
> - syslog (LOG_INFO, " [%ld.%ld] [%s] %s(): %s\n",
> tv.tv_sec, tv.tv_usec, loc, func, msg);
> + syslog (LOG_INFO, " [%ld.%ld] [%s] %s(): %s", tv.tv_sec,
> tv.tv_usec, loc, func, msg);
> } else if ((log_level & LOGL_INFO) && (level == LOGL_INFO))
> - syslog (LOG_INFO, " %s\n", msg);
> + syslog (LOG_INFO, " %s", msg);
> else if ((log_level & LOGL_WARN) && (level == LOGL_WARN))
> - syslog (LOG_WARNING, " %s\n", msg);
> + syslog (LOG_WARNING, " %s", msg);
> else if ((log_level & LOGL_ERR) && (level == LOGL_ERR)) {
> g_get_current_time (&tv);
> - syslog (LOG_ERR, " [%ld.%ld] [%s] %s(): %s\n",
> tv.tv_sec, tv.tv_usec, loc, func, msg);
> + syslog (LOG_ERR, " [%ld.%ld] [%s] %s(): %s", tv.tv_sec,
> tv.tv_usec, loc, func, msg);
> }
> g_free (msg);
> }
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can't get address when two DHCP servers
Le 09/02/2011 15:39, Shawn J. Goff a écrit : > I'm on a network with two DHCP servers and can't connect using Network > Manager. I performed a Wireshark capture and saw a DHCP request from me > followed by a DHCP ack from one server and a DHCP nak from the other. I > did the same thing with dhclient and saw the exact same packets, but > then dhclient went ahead and added the address to the interface and I'm > connected. > > Is this a bug in NM? It is a bug in your network, you simply cannot have two independent and concurrent DHCP servers in the same broadcast segment. When this is the case anything can happen. Are you actually interested in being assigned a random subnet? (or worse: in address clashes?) ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM without PolicyKit ?
On Mon, 2011-01-31 at 17:43 +0100, toabctl wrote: > Hi, > > i ude NetworkManager on an embedded device and don't need policykit. > Is it possible to use network-manager without policykit? > > I've written a Client with libnm-glib and libnm-util and when i want > to use the client, i get: > > WARNING **: Remote Exception invoking > org.freedesktop.PolicyKit1.Authority.CheckAuthorization() > on /org/freedesktop/PolicyKit1/Authority at name > org.freedesktop.PolicyKit1: org.freedesktop.DBus.Error.ServiceUnknown: > The name org.freedesktop.PolicyKit1 was not provided by any .service > files It's not possible without code changes, but I wouldn't mind if a patch showed up. It should be pretty simple to do as the PolicyKit code isn't that hard to find, and isn't too hard to work around. Basically, instead of doing the PK stuff, just call the callback that we pass to PK with a result of AUTHORIZED. We do want it appropriately #ifdefed though, but it might be simpler to just make a small helper sourcefile for this that simulates the Polkit functions and bypasses them internally if polkit is disabled. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On Thu, 2011-02-03 at 13:00 +0200, Ozan Çağlayan wrote: > Hi, > > I have bug reports about some inconsistencies caused by the state file and > rfkill > interactions like when the user kills the radio and then re-enables it, the > WLAN can't be enabled > unless the state file is edited manually as root, etc. > > I think that when the system is booted, NM should ignore the state values in > the state file and > should rely only on the rfkill status. When the user disables the WLAN > through nm-applet or another > GUI, NM can internally remember this without needing that state file. > > Can someone explain how the logic currently works? In current NM 0.8.x git, if you uncheck "Enable Wireless" from the menu, NM writes that to the state file. That will then be in-force until you re-check "Enable Wireless", even across reboots. This takes precedence over rfkill because it was an explicit user choice to disable wifi. This fix was included in NM 0.8.2. I don't think we should be relying on rfkill here, because then it's simply magic what happens on reboot. Some laptops expose multiple rfkill "switches" in the kernel, others expose one, some chain them together, etc. It's a big mess really, and trying to rely on the kernel behavior here isn't going to help much. Instead, I think it's a lot clearer that "If you turn off wifi it stays disabled til you turn it back on". Or? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with new dbus wpa_supplicant api
On Tue, 2011-02-08 at 18:05 +0100, Harald Jung wrote: > Hi, > > the networkmanager i've built from the current git isn't able to get the > aviable access points via the new wpa_supplicant api (0.7.3). > > The scan request is initiated via dbus, but i think it doesn't listen for > dbus > events from wpa_supplicant. > > dbus: fi.w1.wpa_supplicant1.Interface.Scan > (/fi/w1/wpa_supplicant1/Interfaces/1) > . > dbus: flush_object_timeout_handler: Timeout - sending changed properties of > object /fi/w1/wpa_supplicant1/Interfaces/1 > > Has anyone an idea about that problem? The implementation in NM relies on a patch in the supplicant here: http://w1.fi/gitweb/gitweb.cgi?p=hostap-07.git;a=commit;h=b80b5639935d37b95d00f86b57f2844a9c775f57 which was a bug in the original new dbus API implementation. That patch sends out signals when the BSS list changes, so that NM does not have to poll for those changes, which is much more efficient. Unfortunately there hasn't been a wpa_supplicant release with that patch yet. We could poke Jouni to make one though. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with new dbus wpa_supplicant api
Hi, the networkmanager i've built from the current git isn't able to get the aviable access points via the new wpa_supplicant api (0.7.3). The scan request is initiated via dbus, but i think it doesn't listen for dbus events from wpa_supplicant. dbus: fi.w1.wpa_supplicant1.Interface.Scan (/fi/w1/wpa_supplicant1/Interfaces/1) . dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1 Has anyone an idea about that problem? best regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: rt3070sta not controllable with networkmanager
Can you clarify what I need to do in my driver's config.mk file? The only reference to network manager I saw was the following: # Support Native WpaSupplicant for Network Maganger [sic] HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y I have not tried the rt2x00 driver, the wiki main page does not mention my card, but I guess it is similar enough that it should work? Thanks, dan On Sat, Feb 5, 2011 at 1:40 PM, Steev Klimaszewski wrote: > On Fri, Feb 4, 2011 at 3:30 AM, Dan O'Connor > wrote: > > Greetings, > > > > I have an rt3070sta based wifi usb adapter. I've actually got it working, > > but I have to manually connect it to the correct ap (using ifconfig, > > iwconfig, and dhcpcd) and cannot use NetworkManager. When starting > > NetworkManager --no-daemon I get the following output: > > NetworkManager: starting... > > NetworkManager: modem-manager is now available > > > > (NetworkManager:5268): GLib-CRITICAL **: g_error_free: assertion `error > != > > NULL' failed > > NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To > > report bugs please use the NetworkManager mailing list. > > NetworkManager: WiFi enabled by radio killswitch; enabled by state > > file > > NetworkManager: WWAN enabled by radio killswitch; enabled by state > > file > > NetworkManager: Ignoring insecure configuration file > > '/etc/NetworkManager/system-connections/.keep_net-misc_networkmanager-0' > > NetworkManager: (eth0): carrier is OFF > > NetworkManager: (eth0): new Ethernet device (driver: 'r8169') > > NetworkManager: (eth0): exported as > > /org/freedesktop/NetworkManager/Devices/0 > > NetworkManager: (eth0): now managed > > NetworkManager: (eth0): device state change: 1 -> 2 (reason 2) > > NetworkManager: (eth0): preparing device. > > NetworkManager: (eth0): deactivating device (reason: 2). > > NetworkManager: Added default wired connection 'Auto eth0' for > > /sys/devices/pci:00/:00:1c.6/:08:00.0/net/eth0 > > NetworkManager: device_creator(): /sys/devices/virtual/net/ra0: > > couldn't determine device driver; ignoring... > > * status: started > > NetworkManager: default_adapter_cb(): bluez error getting default > > adapter: The name org.bluez was not provided by any .service files > > > > The only important/unexpected line as far as I can tell is that it > couldn't > > determine the device driver for ra0, my wifi device. It seems odd to me > that > > this device is in a "virtual" device folder, is that part of the problem? > > I'm at a total loss as to how NetworkManager is expecting to relate the > > device to its driver. > > > > The distro I'm using is Gentoo, and I configured the kernel myself. I > also > > compiled the wifi driver myself (even had to make some modifications to > get > > it to compile.. nothing major, just update some function names and add a > > license tag). > > I'm not sure what other info would be helpful in solving this problem, I > > will try to be prompt with any requests for more information. > > > > Thanks, > > Dan O. > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > You need to turn on Network Manager support in the config.mk file. > Out of curiosity, is rt2x00 not working for you, or is it just not > stable enough? > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Can't get address when two DHCP servers
I'm on a network with two DHCP servers and can't connect using Network Manager. I performed a Wireshark capture and saw a DHCP request from me followed by a DHCP ack from one server and a DHCP nak from the other. I did the same thing with dhclient and saw the exact same packets, but then dhclient went ahead and added the address to the interface and I'm connected. Is this a bug in NM? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
