Re: networkmanager-list Digest, Vol 90, Issue 23

["Dr. Amr Osman" <dr3mro gmail com>]

On 03/12/2012 09:20 PM, networkmanager-list-request gnome org wrote:
> Send networkmanager-list mailing list submissions to
> 	networkmanager-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mail.gnome.org/mailman/listinfo/networkmanager-list
> or, via email, send a message with subject or body 'help' to
> 	networkmanager-list-request gnome org
>
> You can reach the person managing the list at
> 	networkmanager-list-owner gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of networkmanager-list digest..."
>
>
> Today's Topics:
>
>    1. Re: [MM 0.6] Plumb up the SPN display-rule bits
>       (Aleksander Morgado)
>    2. Re: [PATCH] gsm: pass the PPP auth preferences for STATIC and
>       DHCP	device use (Dan Williams)
>    3. Re: [PATCH] dbus error enum fixes (Dan Williams)
>    4. Re: [PATCH] libnm-glib: add missing nm_device_set_device_type
>       to	libnm-glib.ver (Dan Williams)
>    5. Re: DBUS specifications for NetworkManager 0.9 (Dan Williams)
>    6. Re: [back to this topic] Re: PIN handling problem on Connect
>       automatically (S?rgio Basto)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 12 Mar 2012 14:28:03 +0100
> From: Aleksander Morgado <aleksander lanedo com>
> To: Nathan Williams <njw google com>, "Williams, Dan"
> 	<dcbw redhat com>
> Cc: networkmanager-list gnome org
> Subject: Re: [MM 0.6] Plumb up the SPN display-rule bits
> Message-ID: <4F5DF9E3 7090604 lanedo com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hey,
>
>>>         A possible fix to handle the case where we don't know how much
>>>         we can
>>>
>>>         read would be to try to read the first bytes of the record (3 or
>>>         4 or 5
>>>         just in case) to get the full record length of the record,
>>>         assuming 1-3
>>>         bytes max for the size field, so we read "A3" + size encoded in
>>>         1 or 2
>>>         or 3 bytes + "80"); and once we know the whole record size, read the
>>>         exact list size.
>>>
>>>
>>>     Yeah, I thought about this, but had hoped to avoid it (If the record
>>>     is present at all, there will be a minimum of 7 bytes -
>>>     A3058003FFFFFF -  so I think that's the right amount for an initial
>>>     read). 
>>>
>>>
>>> Here's a version that does the 7-then-more retry. It works on my SIM
>>> (retrying from 7 to 34 bytes, even though the entries are all FFFFFF);
>>> see what you think.
>>>
>> That worked very well for me.
>>
>> Now that we have the 3 values we needed from the SIM card (2 flags +
>> SPDI list), we could now also implement the "RequiredNameDisplay"
>> property which contains the whole logic for us, as Dan suggested
>> earlier. Given that this value depends on the current 3GPP operator ID,
>> I would really include that new property in the 3GPP interface. Will try
>> to implement this later on today.
>>
> I pushed now a '06-api-display-rules' branch in upstream git; with the
> changes discussed here and a new "RequiredDisplayName" property.
>
> Dan, Nathan, are you guys happy with the new branch? I'm not very
> convinced yet about the flag property names...
>
hello
I use ubuntu 11.10 with latest version of modem manager and network manager
and zte usb modem mf 190 (19d2:0033)
the problem is that it failed to connect when it's detected on ttyUSB2
and i have
to disconnect it and reconnect servral times until it's detected on
ttyUSB3 then
it will connect
but if i use sakis3G script it's detected fine by sakies only and
connect on ttyUSB3 even if
nm-tool detect the modem in the same setting on ttyUSB2 how come???
please if some one can make a patch and i can test be welcomed
thanks