Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta
Thank you for the quick turn around. I can confirm that the F13 packages have fixed my problems. NM Bluetooth DUN is setup correctly by the wizard, and ppp connection is made successfully. On Tue, May 11, 2010 at 4:06 PM, Dan Williams d...@redhat.com wrote: On Mon, 2010-05-10 at 14:49 +0100, Bastien Nocera wrote: 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. And is now fixed upstream and in F13. Dan ___ 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: 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: 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
NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta
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 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:13.0/usb5/5-1 claimed port rfcomm0 ** (modem-manager:8225): DEBUG: Added modem /sys/devices/pci:00/:00:13.0/usb5/5-1 ** (modem-manager:8225): DEBUG: (tty/rfcomm0): outstanding support task prevents export of /sys/devices/pci:00/:00:13.0/usb5/5-1 ** (modem-manager:8225): DEBUG: 1273466798.26270 (rfcomm0): -- 'AT+CPIN?CR' ** (modem-manager:8225): DEBUG:
