RE: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13Beta
Hi, It seems that NetworkManager cannot find driver for your device, also your device is not provide 'Generic interface'. Try to find/write its driver for yourself. _ From: networkmanager-list-boun...@gnome.org [mailto:networkmanager-list-boun...@gnome.org] On Behalf Of Ascanio Alba Sent: Sunday, May 09, 2010 9:55 PM To: networkmanager-list@gnome.org Subject: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13Beta Hi, I have a bluetooth DUN device (/dev/rfcomm0) exported by modem-manager but being ignored by NetworkManager. This is on Fedora 13 Beta, latest updates-testing. I was getting some SELinux denials but did an audit2allow to remove that variable from the system. blueman attaches to the DUN service. modem-manager sees and exports the device, but NM ignores it. Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64 NetworkManager --no-daemon --log-level=DEBUG -- Original message: type=0x14 length=56 flags=REQUEST,ACK,ATOMIC sequence-nr=1273466780 pid=4202530 NetworkManager[8226]: warn bluez error getting default adapter: The name org.bluez was not provided by any .service files NetworkManager[8226]: debug [1273466770.628023] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 1 flags 0x10049 NetworkManager[8226]: debug [1273466770.628166] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 2 flags 0x11043 NetworkManager[8226]: debug [1273466770.628277] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 3 flags 0x1002 NetworkManager[8226]: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled... NetworkManager[8226]: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started... NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete. NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... NetworkManager[8226]: info (eth0): device state change: 7 - 8 (reason 0) NetworkManager[8226]: info Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS. NetworkManager[8226]: info Activation (eth0) successful, device activated. NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. NetworkManager[8226]: debug [1273466778.926831] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 7 flags 0x1002 NetworkManager[8226]: debug [1273466778.937908] [nm-udev-manager.c:477] handle_uevent(): UDEV event: action 'add' subsys 'net' device 'pan0' NetworkManager[8226]: warn /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring... NetworkManager[8226]: debug [1273466785.853458] [nm-udev-manager.c:477] handle_uevent(): UDEV event: action 'change' subsys 'rfkill' device 'rfkill0' NetworkManager[8226]: info ignoring modem 'rfcomm0' (no associated Bluetooth device) modem-manager --debug: ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin Ericsson MBM ** Message: Loaded plugin Huawei ** Message: Loaded plugin Generic ** Message: Loaded plugin MotoC ** Message: Loaded plugin AnyData ** Message: Loaded plugin Sierra ** Message: Loaded plugin Nokia ** Message: Loaded plugin Option ** Message: Loaded plugin ZTE ** Message: Loaded plugin Novatel ** Message: Loaded plugin Longcheer ** Message: Loaded plugin Gobi ** (modem-manager:8225): DEBUG: (tty/ttyS1): port's parent platform driver is not whitelisted ** (modem-manager:8225): DEBUG: (tty/ttyS2): port's parent platform driver is not whitelisted ** (modem-manager:8225): DEBUG: (tty/ttyS3): port's parent platform driver is not whitelisted ** (modem-manager:8225): DEBUG: (tty/ttyS0): could not get port's parent device ** (modem-manager:8225): DEBUG: (net/vboxnet0): could not get port's parent device ** (modem-manager:8225): DEBUG: (net/pan0): could not get port's parent device ** (modem-manager:8225): DEBUG: (tty/rfcomm0): could not get port's parent device ** Message: (rfcomm0) opening serial device... ** (modem-manager:8225): DEBUG: 1273466797.123682 (rfcomm0) device open count is 1 (open) ** (modem-manager:8225): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:8225): DEBUG: 1273466797.222951 (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:8225): DEBUG: 1273466798.23952 (rfcomm0): -- 'AT+GCAPCRCRLF+GCAP: +CGSM,+DS,+WCRLFCRLFOKCRLF' ** (modem-manager:8225): DEBUG: 1273466798.24144 (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** Message: (rfcomm0) type primary claimed by /sys/devices/pci:00/:00:13.0/usb5/5-1 ** Message: (rfcomm0) opening serial device... ** (modem-manager:8225): DEBUG: 1273466798.25980 (rfcomm0) device open count is
add-system-connection.py - dbus.exceptions.DBusException: org.freedesktop.NetworkManagerSettings.InvalidProperty: addresses
Hi, i tried to execute the example script NetworkManager/examples/python/add-system-connection.py python add-system-connection.py Traceback (most recent call last): File add-system-connection.py, line 47, in module settings.AddConnection(con) File /usr/lib/pymodules/python2.5/dbus/proxies.py, line 68, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/pymodules/python2.5/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/pymodules/python2.5/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.NetworkManagerSettings.InvalidProperty: addresses I use debian squeeze with NetworkManager from the debian repository (0.8-1). Can anybody help? Cheers, Tom ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: add-system-connection.py - dbus.exceptions.DBusException: org.freedesktop.NetworkManagerSettings.InvalidProperty: addresses
On Monday 10 of May 2010 11:11:22 toabctl wrote: Hi, i tried to execute the example script NetworkManager/examples/python/add-system-connection.py python add-system-connection.py Traceback (most recent call last): File add-system-connection.py, line 47, in module settings.AddConnection(con) File /usr/lib/pymodules/python2.5/dbus/proxies.py, line 68, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/pymodules/python2.5/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/pymodules/python2.5/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.NetworkManagerSettings.InvalidProperty: addresses I use debian squeeze with NetworkManager from the debian repository (0.8-1). Can anybody help? Cheers, Tom It was fixed upstream a few days ago. Get the script here: http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/examples/python/add- system-connection.py Note: The prefix was zero, which is incorrect. Jirka ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta
On Mon, 2010-05-10 at 12:54 +0800, Ascanio Alba wrote: Hi, I have a bluetooth DUN device (/dev/rfcomm0) exported by modem-manager but being ignored by NetworkManager. This is on Fedora 13 Beta, latest updates-testing. I was getting some SELinux denials but did an audit2allow to remove that variable from the system. blueman attaches to the DUN service. modem-manager sees and exports the device, but NM ignores it. Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64 Don't use blueman to set up DUN, use the wizard in gnome-bluetooth instead (you'll need to re-pair your device to do that, and it should ask you a question once setup). Blueman's way of setting up rfcomm was always hacky, and is now out-of-date. Cheers ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RADIUS backend and Win2003 Server with specific pathch don't work Was: Error searching on specific ssid
On Thursday 06 of May 2010 14:23:52 Bjorge Solli wrote: Info: www.eduroam.org, www.eduroam.no Setup: we have two Win2k3 servers as authenticators for our two domains (students and staff) and one had this patch and the other didn't: http://support.microsoft.com/kb/948963 The domain with the patch failed to authenticate and removing the patch solved the problem. The patch adds TLS_RSA_WITH_AES_128_CBC_SHA AES128-SHA and the TLS_RSA_WITH_AES_256_CBC_SHA AES256-SHA AES. This patch is backported from Win Server 2008.. Thanks for the info. It's good to know that it works without the hotfix on Windows. In that case, RC4-based cipher is probably used. Nevertheless, it is ironic that with the hotfix the negotiation is not successful, because it's meant to improve cooperation with OpenSSL. Our problem is solved for now, but maybe someone should try to solve the underlying problem? I have attached the wpa_supplicant log of a failing connection. I don't know what the actual problem is, but TLS/SSL handshake was not successful. If you have a chance to capture packets with Wireshark (or something) in not- working case, it would help to identify issues in SSL handshake. BTW, what distributions do you use? What are the versions of NM, wpa_supplicant and OpenSSL? Searching a bit on the problem, there could be a bug in older versions of wpa_supplicant. Please cc to me on replies as I don't read the list every day. On 27/04/10 13:30, Jirka Klimes wrote: You can follow instructions in section Debugging WiFi Connections on http://live.gnome.org/NetworkManager/Debugging Thanks! - Bjørge Jirka ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta
I tried without blueman and got a similar error message. I disabled blueman and went via the gnome-bluetooth wizard to setup new device. I reached Access Internet using your mobile phone (DUN) Got Detecting phone configuration... MM seems to detect the 3G phone and exported it but NM rejects. Then MM removes the device. I tried this on another system but even worse gnome bluetooth wizard ABRTing. NM reports: NetworkManager[14671]: info ignoring modem 'rfcomm0' (no associated Bluetooth device) MM reports: ** (modem-manager:14420): DEBUG: (tty/rfcomm0): could not get port's parent device ** Message: (rfcomm0) opening serial device... ** (modem-manager:14420): DEBUG: 1273497578.791149 (rfcomm0) device open count is 1 (open) ** (modem-manager:14420): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:14420): DEBUG: 1273497578.890504 (rfcomm0): -- 'AT+GCAPCR' ** (modem-manager:14420): DEBUG: 1273497579.691510 (rfcomm0): -- 'AT+GCAPCRCRLF+GCAP: +CGSM,+DS,+WCRLFCRLFOKCRLF' ** (modem-manager:14420): DEBUG: 1273497579.691700 (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** Message: (rfcomm0) type primary claimed by /sys/devices/pci:00/:00:13.0/usb5/5-2 ** Message: (rfcomm0) opening serial device... ** (modem-manager:14420): DEBUG: 1273497579.692679 (rfcomm0) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:13.0/usb5/5-2 claimed port rfcomm0 ** (modem-manager:14420): DEBUG: Added modem /sys/devices/pci:00/:00:13.0/usb5/5-2 ** (modem-manager:14420): DEBUG: (tty/rfcomm0): outstanding support task prevents export of /sys/devices/pci:00/:00:13.0/usb5/5-2 ** (modem-manager:14420): DEBUG: 1273497579.692956 (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:14420): DEBUG: 1273497579.702872 (rfcomm0): -- 'AT+' ** (modem-manager:14420): DEBUG: 1273497579.703528 (rfcomm0): -- 'C' ** (modem-manager:14420): DEBUG: 1273497579.707549 (rfcomm0): -- 'P' ** (modem-manager:14420): DEBUG: 1273497579.708539 (rfcomm0): -- 'I' ** (modem-manager:14420): DEBUG: 1273497579.710546 (rfcomm0): -- 'N' ** (modem-manager:14420): DEBUG: 1273497579.711523 (rfcomm0): -- '?' ** (modem-manager:14420): DEBUG: 1273497579.713537 (rfcomm0): -- 'CRCRLF+CPIN: READYCRLFCRLFOKCRLF' ** (modem-manager:14420): DEBUG: 1273497579.713673 (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** (modem-manager:14420): DEBUG: Exported modem /sys/devices/pci:00/:00:13.0/usb5/5-2 as /org/freedesktop/ModemManager/Modems/2 ** (modem-manager:14420): DEBUG: (/org/freedesktop/ModemManager/Modems/2): data port is rfcomm0 ** (modem-manager:14420): DEBUG: Removed modem /sys/devices/pci:00/:00:13.0/usb5/5-2 On Mon, May 10, 2010 at 6:16 PM, Bastien Nocera had...@hadess.net wrote: On Mon, 2010-05-10 at 12:54 +0800, Ascanio Alba wrote: Hi, I have a bluetooth DUN device (/dev/rfcomm0) exported by modem-manager but being ignored by NetworkManager. This is on Fedora 13 Beta, latest updates-testing. I was getting some SELinux denials but did an audit2allow to remove that variable from the system. blueman attaches to the DUN service. modem-manager sees and exports the device, but NM ignores it. Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64 Don't use blueman to set up DUN, use the wizard in gnome-bluetooth instead (you'll need to re-pair your device to do that, and it should ask you a question once setup). Blueman's way of setting up rfcomm was always hacky, and is now out-of-date. Cheers ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RADIUS backend and Win2003 Server with specific pathch don't work Was: Error searching on specific ssid
Hi Jirka, thanks for your reply! On 10/05/10 14:52, Jirka Klimes wrote: On Thursday 06 of May 2010 14:23:52 Bjorge Solli wrote: Info: www.eduroam.org, www.eduroam.no Setup: we have two Win2k3 servers as authenticators for our two domains (students and staff) and one had this patch and the other didn't: http://support.microsoft.com/kb/948963 The domain with the patch failed to authenticate and removing the patch solved the problem. The patch adds TLS_RSA_WITH_AES_128_CBC_SHA AES128-SHA and the TLS_RSA_WITH_AES_256_CBC_SHA AES256-SHA AES. This patch is backported from Win Server 2008.. Thanks for the info. It's good to know that it works without the hotfix on Windows. In that case, RC4-based cipher is probably used. Nevertheless, it is ironic that with the hotfix the negotiation is not successful, because it's meant to improve cooperation with OpenSSL. Our problem is solved for now, but maybe someone should try to solve the underlying problem? I have attached the wpa_supplicant log of a failing connection. I don't know what the actual problem is, but TLS/SSL handshake was not successful. If you have a chance to capture packets with Wireshark (or something) in not- working case, it would help to identify issues in SSL handshake. We did have that, but it was unfortunately deleted. We don't want to break the system just to produce it again.. BTW, what distributions do you use? Fedora 12, tested on both 32-bit and 64-bit. Updated to latest in yum repos. What are the versions of NM, wpa_supplicant and OpenSSL? Searching a bit on the problem, there could be a bug in older versions of wpa_supplicant. # rpm -qa | egrep -i '(wpa|networkmanager|openssl)' openssl-1.0.0-0.13.beta4.fc12.i686 NetworkManager-glib-0.8.0-6.git20100408.fc12.x86_64 pyOpenSSL-0.9-1.fc12.x86_64 NetworkManager-openconnect-0.7.996-4.git20090921.fc12.x86_64 NetworkManager-pptp-0.7.997-3.git20100120.fc12.x86_64 openssl-1.0.0-0.13.beta4.fc12.x86_64 NetworkManager-gnome-0.8.0-6.git20100408.fc12.x86_64 wpa_supplicant-0.6.8-8.fc12.x86_64 NetworkManager-vpnc-0.7.996-4.git20090921.fc12.x86_64 NetworkManager-0.8.0-6.git20100408.fc12.x86_64 NetworkManager-openvpn-0.7.996-4.git20090923.fc12.x86_64 Please cc to me on replies as I don't read the list every day. On 27/04/10 13:30, Jirka Klimes wrote: You can follow instructions in section Debugging WiFi Connections on http://live.gnome.org/NetworkManager/Debugging Thanks! - Bjørge -- Regards/Mvh, Bjørge Solli Staff engineer/Overingeniør at Uni. Bergen, IT, Infrastruktur, Unix Nygårdsgaten 5. Pb.7800, N-5020 Bergen, Norway. www.uib.no/it (+47) Tlf: (555)82774 Mob: 91614343 Fax: (555)48299 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta
On Mon, 2010-05-10 at 21:26 +0800, Ascanio Alba wrote: I tried without blueman and got a similar error message. I disabled blueman and went via the gnome-bluetooth wizard to setup new device. I reached Access Internet using your mobile phone (DUN) Got Detecting phone configuration... MM seems to detect the 3G phone and exported it but NM rejects. Then MM removes the device. I tried this on another system but even worse gnome bluetooth wizard ABRTing. If the bluetooth wizard from gnome-bluetooth crashes, please file a bug. Cheers ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta
On Mon, 2010-05-10 at 14:36 +0100, Bastien Nocera wrote: On Mon, 2010-05-10 at 21:26 +0800, Ascanio Alba wrote: I tried without blueman and got a similar error message. I disabled blueman and went via the gnome-bluetooth wizard to setup new device. I reached Access Internet using your mobile phone (DUN) Got Detecting phone configuration... MM seems to detect the 3G phone and exported it but NM rejects. Then MM removes the device. I tried this on another system but even worse gnome bluetooth wizard ABRTing. If the bluetooth wizard from gnome-bluetooth crashes, please file a bug. My guess is that it's a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=590666 Which is a bug in NetworkManager's gnome-bluetooth plugin. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can not build network-manager from git with debian squeeze
you need libiw-dev. markus Hi, i tried to build the latest git sources and got the following error: ### BEGIN ### $ ./autogen.sh ... ... checking Linux Wireless Extensions = 18... no configure: error: wireless-tools library and development headers = 28pre9 not installed or not functional ### END ### but: $ dpkg -l|grep wireless-tools ii wireless-tools30~pre9-4 Tools for manipulating Linux Wireless Extensions so wireless-tools are version 30. Any idea? Cheers, Tom ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can not build network-manager from git with debian squeeze
On 05/10/2010 09:17 AM, toabctl wrote: checking Linux Wireless Extensions = 18... no configure: error: wireless-tools library and development headers = 28pre9 not installed or not functional ### END ### but: $ dpkg -l|grep wireless-tools ii wireless-tools30~pre9-4 Tools for manipulating Linux Wireless Extensions so wireless-tools are version 30. Any idea? Try installing libiw-dev, I think that will fix it. (It's confusing, I agree.) Hope that helps! Have a good one, Daniel ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: connection error on duplicate SSID
Darren Albers dalb...@gmail.com schrieb am 10.05.2010 01:43: It exists when you add a network manually so you could always use that method to add a network. I don't see a gconf option for this but maybe Dan has some super double-secret option somewhere for this. thanx darren, now that i brought it up i can stop reminding myself of it ;) i'll fix it for myself.. hoping someone will find a way to make this automatic for the novice user.. safe ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
