Re: multiple entries for mobile phone

[Dan Williams <dcbw redhat com>]

On Tue, 2008-11-25 at 10:14 +0100, Nikolaus Filus wrote:
> Hi,
> 
> I own a Sony Ericsson W890i and want to use it for broadband with NM. As long as
> bluetooth support is not integrated in NM (BTW: is there a roadmap?) I'm using
> the USB data cable. The USB mode can be set to
> 
> - show menu
> - phone mode
> - media transfer
> - printing
> - mass storage (reboots into special mode)
> 
> With phone mode as my default NM recognizes the phone immediately and tries to
> acquire an address from usb0 - this is dangerous and should be disabled by

NM also supports USB ethernet devices, for which this behavior is quite
desirable.  What you probably want is a hint in HAL that the device
isn't really an ethernet adapter and thus maybe we shouldn't make it
autoconnect by default.  But by default, the interface looks no
different than a USB ethernet dongle like the D-Link DUB-E100.

> default! If my phone's connections would be set to auto-connect, every time I
> plug in the phone, it would make a costly connection to the internet and it is
> not possible to set a policy in NM until the device exists. I would wish to be
> prompted for something like
> 
> "
>   new device 'Sony Ericcsson ...' detected. Please set connection policy
>    [ ] auto connect by default
>    [ ] connect now
> "

Perhaps that would be acceptable if there was some indication from HAL
that the device was not really an ethernet device but a mobile phone,
but also remember that you can run NM in situations where there is no
logged-in user, and if there are existing ethernet connections that are
not locked to a specific MAC address, it's perfectly valid to activate
that connection for any adapter that is plugged in.

Perhaps we could implement better connection matching in NetworkManager
such that if there's a valid connection for a device that's locked to
the MAC address, prefer that one above others.  Thus, you create a "my
phone" wired connection, lock to the MAC address of your phone, and when
you plug the phone in, only that connection would be honored.  If that
connection is autoconnect=false, it simply wouldn't be activated by NM
until you told NM to do so.

> Main problem is, that there are 2 cdc_acm devices and NM shows the broadband
> options twice. How to fix this?

In HAL.  Which device is the real TTY?  You need to tag that device as
the only modem port.  Soon we'll be probing each TTY (though Ubuntu has
non-upstream patches that hack in probing to NetworkManager so you'll
want to ask in Launchpad instead.

Dan

> version used: 0.7~~svn20081018t105859-0ubuntu1 (official repo)
> 
> Thank you
> 
> 
> [ 9098.056179] usb 4-2: new high speed USB device using ehci_hcd and address 5
> [ 9098.215371] usb 4-2: configuration #3 chosen from 1 choice
> [ 9099.257753] cdc_acm 4-2:3.1: ttyACM0: USB ACM device
> [ 9099.263453] cdc_acm 4-2:3.3: ttyACM1: USB ACM device
> [ 9099.265719] usbcore: registered new interface driver cdc_acm
> [ 9099.266691] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems
> 		and ISDN adapters
> [ 9099.300527] cdc_wdm 4-2:3.7: cdc-wdm0: USB WDM device
> [ 9099.301908] usbcore: registered new interface driver cdc_wdm
> [ 9099.349959] usb0: register 'cdc_ether' at usb-0000:00:1d.7-2, CDC Ethernet
> 		Device, 02:80:37:fe:02:00
> [ 9099.351561] usbcore: registered new interface driver cdc_ether
> [ 9100.045710] ttyS2: LSR safety check engaged!
> [ 9100.757328] ttyS2: LSR safety check engaged!
> [ 9115.600037] usb0: no IPv6 routers present
> 
> lshal -m
> 10:03:57.123: usb_device_fce_d0b3_3523820281403050 added
> 10:03:57.146: usb_device_fce_d0b3_3523820281403050 property info.linux.driver =
> 'usb' (new)
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if0 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if1 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if2 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if3 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if4 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if5 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if6 added
> 10:03:58.442: usb_device_fce_d0b3_3523820281403050_if7 added
> 10:03:58.443: usb_device_fce_d0b3_3523820281403050_if8 added
> 10:03:58.443: usb_device_fce_d0b3_3523820281403050_if9 added
> 10:03:58.570: usb_device_fce_d0b3_3523820281403050_if0_0 added
> 10:03:58.573: usb_device_fce_d0b3_3523820281403050_if2 property
> info.linux.driver = 'cdc_acm' (new)
> 10:03:58.620: usb_device_fce_d0b3_3523820281403050_if1 property
> info.linux.driver = 'cdc_acm' (new)
> 10:03:58.628: usb_device_fce_d0b3_3523820281403050_if1_serial_unknown_0 added
> 10:03:58.628: usb_device_fce_d0b3_3523820281403050_if3_serial_unknown_1 added
> 10:03:58.628: usb_device_ffffffff_ffffffff_noserial added
> 10:03:58.629: net_02_80_37_fe_02_00 added
> 
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list