Re: NM 0.7.1 rc3 oddness with 3G USB device
On Fri, 2009-03-13 at 17:02 +0100, Jacob Nielsen wrote: > Hi, > > On Mon, 2009-03-09 at 15:05 -0400, Dan Williams wrote: > > > > The devices don't always get cleared from the list of Broadband devices > > > when > > > the device is removed - these can keep mounting up. > > > > That's quite odd; can you post some logs of this happening in NM? I've > > heard of similar issues before but we could never nail them down to > > either NM or HAL. > > I see the same behaviour with my Huawei e160g dongle: > > When the dongle is inserted, two ttyUSB devices appear. If it is removed > without making a connection, they both disappear again. > > After connecting to and disconnecting from the network through the > nm-applet menu, the dongle is left registered to the network (according > to the dongle's LED code). If it is removed in this state, the > lower-numbered tty device remains. When it is reconnected, two tty > devices appear again, for a total of three. Also, the applet menu will > then have two identical entries for the 3g provider. (And it is still > possible to connect.) I finally ran into this yesterday myself so there's some hope I can fix it :) Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.1 rc3 oddness with 3G USB device
Hi, On Mon, 2009-03-09 at 15:05 -0400, Dan Williams wrote: > > The devices don't always get cleared from the list of Broadband devices when > > the device is removed - these can keep mounting up. > > That's quite odd; can you post some logs of this happening in NM? I've > heard of similar issues before but we could never nail them down to > either NM or HAL. I see the same behaviour with my Huawei e160g dongle: When the dongle is inserted, two ttyUSB devices appear. If it is removed without making a connection, they both disappear again. After connecting to and disconnecting from the network through the nm-applet menu, the dongle is left registered to the network (according to the dongle's LED code). If it is removed in this state, the lower-numbered tty device remains. When it is reconnected, two tty devices appear again, for a total of three. Also, the applet menu will then have two identical entries for the 3g provider. (And it is still possible to connect.) NM debug output and syslog attached. (Tested in Ubuntu jaunty alpha 6 (USB stick). FTR, the behavior was the same in Fedora 10 + updates to 0.7.1.99 (live CD).) Best regards, Jacob Nielsen NetworkManager: starting... NetworkManager: (eth0): new Ethernet device (driver: 'r8169') NetworkManager: (eth0): exported as /org/freedesktop/Hal/devices/net_00_1f_d0_ad_34_43 NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) NetworkManager: (eth0): device state change: 1 -> 2 NetworkManager: (eth0): bringing up device. NetworkManager: (eth0): preparing device. NetworkManager: (eth0): deactivating device (reason: 2). NetworkManager: (ttyUSB0): detected GSM modem via HAL capabilities NetworkManager: (ttyUSB0): new Modem device (driver: 'option') NetworkManager: (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0 NetworkManager: (ttyUSB0): device state change: 1 -> 2 NetworkManager: (ttyUSB0): deactivating device (reason: 2). NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed NetworkManager: (ttyUSB0): device state change: 2 -> 3 NetworkManager: (ttyUSB0): now unmanaged NetworkManager: (ttyUSB0): device state change: 3 -> 1 NetworkManager: (ttyUSB0): cleaning up... NetworkManager: (ttyUSB0): taking down device. NetworkManager: (ttyUSB0): detected GSM modem via HAL capabilities NetworkManager: (ttyUSB0): new Modem device (driver: 'option') NetworkManager: (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0 NetworkManager: (ttyUSB0): device state change: 1 -> 2 NetworkManager: (ttyUSB0): deactivating device (reason: 2). NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed NetworkManager: (ttyUSB0): device state change: 2 -> 3 NetworkManager: Activation (ttyUSB0) starting connection 'oister' NetworkManager: (ttyUSB0): device state change: 3 -> 4 NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... NetworkManager: [1236955082.238117] nm_serial_device_open(): (ttyUSB0) opening device... NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: [1236955082.344984] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' NetworkManager: [1236955082.374032] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0' NetworkManager: [1236955082.374208] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' NetworkManager: [1236955082.381801] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0 OK ' NetworkManager: [1236955082.381830] nm_serial_debug(): Sending: 'AT+CPIN? ' NetworkManager: [1236955082.391706] nm_serial_debug(): Got: ' +CPIN: SIM PIN OK ' NetworkManager: (ttyUSB0): GSM pin secret required NetworkManager: (ttyUSB0): device state change: 4 -> 6 NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... NetworkManager: (ttyUSB0): device state change: 6 -> 4 NetworkManager: [1236955086.246913] nm_serial_device_open(): (ttyUSB0) opening device... NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: [1236955086.348101] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' NetworkManager: [1236955086.383323] nm_serial_debug(): Got: ' OK ' NetworkManager: [1236955086.383363] nm_serial_debug(): Sending: 'AT+CPIN? ' NetworkManager: [1236
Re: NM 0.7.1 rc3 oddness with 3G USB device
On Tue, 2009-03-10 at 12:42 +0200, Tambet Ingo wrote: > On Mon, Mar 9, 2009 at 21:05, Dan Williams wrote: > > Mobile broadband capabilities are detected with udev capabilities now > > too, but the problem here is that nothing reports which channel is the > > control channel and which isn't. That information need to go into the > > driver somewhere like it does for 'hso' type devices. I don't know; > > maybe asac is right and we do need to prefer HAL over udev at least for > > 0.7.1. > > I agree with asac then. With any modem other than HSO, you have no > idea from probing which port is the control port and which just > accepts AT commands. With HAL, while things are fragile and require > manual updates, there's at least a chance it works. Alternatively, we could use the HAL information in addition to the udev information. Given a udev probe of the ports, get the HAL info as well. If HAL thinks the port is GSM/CDMA-capable, use it. If HAL doesn't know about any ports for the device, just pick a port to use like the udev stuff does now. Or we could start putting port-types into the udev rules just like we've done for HAL. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.1 rc3 oddness with 3G USB device
On Mon, Mar 9, 2009 at 21:05, Dan Williams wrote: > Mobile broadband capabilities are detected with udev capabilities now > too, but the problem here is that nothing reports which channel is the > control channel and which isn't. That information need to go into the > driver somewhere like it does for 'hso' type devices. I don't know; > maybe asac is right and we do need to prefer HAL over udev at least for > 0.7.1. I agree with asac then. With any modem other than HSO, you have no idea from probing which port is the control port and which just accepts AT commands. With HAL, while things are fragile and require manual updates, there's at least a chance it works. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.1 rc3 oddness with 3G USB device
On Mon, 2009-03-09 at 15:05 -0400, Dan Williams wrote: > On Mon, 2009-03-09 at 17:34 +, Conor Nolan wrote: > > Ubuntu Jaunty - 0.7.1~rc3-0ubuntu1 > > > > After updating to the above I'm see strange behaviour with a Huawei E180. > > > > First to note the device works fine - still reported as an E220/270. > > > > The strange behaviour is that nm-applet is now reporting two devices: > > ttyUSB0 and ttyUSB1 (the control channel), instead of just the one. > > Mobile broadband capabilities are detected with udev capabilities now > too, but the problem here is that nothing reports which channel is the > control channel and which isn't. That information need to go into the > driver somewhere like it does for 'hso' type devices. I don't know; > maybe asac is right and we do need to prefer HAL over udev at least for > 0.7.1. Well - it's not a show stopper. But 'looks' bad. > > The devices don't always get cleared from the list of Broadband devices when > > the device is removed - these can keep mounting up. > > That's quite odd; can you post some logs of this happening in NM? I've > heard of similar issues before but we could never nail them down to > either NM or HAL. I'll attempt to capture this occurrence, Thanks for the informative reply. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.1 rc3 oddness with 3G USB device
On Mon, 2009-03-09 at 17:34 +, Conor Nolan wrote: > Ubuntu Jaunty - 0.7.1~rc3-0ubuntu1 > > After updating to the above I'm see strange behaviour with a Huawei E180. > > First to note the device works fine - still reported as an E220/270. > > The strange behaviour is that nm-applet is now reporting two devices: > ttyUSB0 and ttyUSB1 (the control channel), instead of just the one. Mobile broadband capabilities are detected with udev capabilities now too, but the problem here is that nothing reports which channel is the control channel and which isn't. That information need to go into the driver somewhere like it does for 'hso' type devices. I don't know; maybe asac is right and we do need to prefer HAL over udev at least for 0.7.1. > The devices don't always get cleared from the list of Broadband devices when > the device is removed - these can keep mounting up. That's quite odd; can you post some logs of this happening in NM? I've heard of similar issues before but we could never nail them down to either NM or HAL. > Another issue I noticed is that the wired ethernet device's (not ifupdown) > address moved from eth0 -> eth2. Ditto wireless eth1 -> eth3. From where > is this controlled? udev, most likely. There are usually some "persistent-net-rules" scripts in the udev rules directory (most likely /lib/udev/rules.d) that will try to keep persistent net device names based on MAC address. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM 0.7.1 rc3 oddness with 3G USB device
Ubuntu Jaunty - 0.7.1~rc3-0ubuntu1 After updating to the above I'm see strange behaviour with a Huawei E180. First to note the device works fine - still reported as an E220/270. The strange behaviour is that nm-applet is now reporting two devices: ttyUSB0 and ttyUSB1 (the control channel), instead of just the one. The devices don't always get cleared from the list of Broadband devices when the device is removed - these can keep mounting up. Another issue I noticed is that the wired ethernet device's (not ifupdown) address moved from eth0 -> eth2. Ditto wireless eth1 -> eth3. From where is this controlled ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM 0.7.1 rc3 oddness with 3G USB device
Ubuntu Jaunty - 0.7.1~rc3-0ubuntu1 After updating to the above I'm see strange behaviour with a Huawei E180. First to note the device works fine - still reported as an E220/270. The strange behaviour is that nm-applet is now reporting two devices: ttyUSB0 and ttyUSB1 (the control channel), instead of just the one. The devices don't always get cleared from the list of Broadband devices when the device is removed - these can keep mounting up. Another issue I noticed is that the wired ethernet device's (not ifupdown) address moved from eth0 -> eth2. Ditto wireless eth1 -> eth3. From where is this controlled? -- CN ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
