Re: 3G Modem DHCP time out
Hey, Thanks Olaf, that's exactly what I've done and it's working perfectly well. Bests, E. Le 25/09/2013 16:40, Olaf Schulz a écrit : Hi, I found another option to avoid the problem you observed on https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1169117: ...by adding a file /etc/modprobe.d/avoid-mbim.conf with content: options cdc_ncm prefer_mbim=N This helped me in this case. Olaf # Emmanuel Riboulet-Deyris schrieb am 27.03.2013 um 23:26 h Thank's a lot Bjørn for pointing me this bug report. It appears that it's exactly the bug I'm encountering (on the same laptop by the way). I'm very far away from being an expert about that, but if I understand, the simplest way to make thinks work currently with a 3.8.x kernel would be to rebuild my kernel with the key CONFIG_USB_NET_CDC_MBIM set to n. Is that correct ? Thanks again, E. Le 26/03/2013 17:45, Bjørn Mork a écrit : This may be a problem introduced with the cdc_mbim driver in Linux 3.8. The problem is that we don't have userspace support for it yet. See https://bugzilla.kernel.org/show_bug.cgi?id=54791 for more details. Ben Hutchins suggested that ModemManager could include a modprobe.d *.conf snippet setting ncm as preferred until the MBIM support is ready. But this might not be so easy as long as you need a 3.8.5 or newer kernel to have this option... Ideas are welcome. Bjørn ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Sierra Wireless MC8355 - Gobi 3000 with ATT
On 02/10/13 17:05, Kenneth Berland wrote: NM moves along well until it errors-out with these lines (I think): Oct 2 07:35:50 ken-x230 ModemManager[1811]: info error: couldn't start network: QMI protocol error (14): 'CallFailed' Oct 2 07:35:50 ken-x230 ModemManager[1811]: info call end reason (1018): 'gsm-wcdma-option-unsubscribed' Oct 2 07:35:50 ken-x230 ModemManager[1811]: info verbose call end reason (6,33): [3gpp] option-unsubscribed The 'gsm-wcdma-option-unsubscribed' error is actually the default error sent when the APN is wrong... I would really check what APN is being used. -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Sierra Wireless MC8355 - Gobi 3000 with ATT
Kenneth Berland k...@hero.com writes: apn=wap.cingular I don't know anything about ATT services, but Google sent me to this page: http://www.wireless.att.com/support_static_files/KB/KB41477.html where wap.cingular is documented as Does not allow tethering (using phone as a modem) of a handset or PDA for internet access on a computer. Could very well be that they forbid using that APN with a Sierra Wireless IMEI. Bjørn ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Sierra Wireless MC8355 - Gobi 3000 with ATT
On 03/10/13 10:15, Bjørn Mork wrote: Could very well be that they forbid using that APN with a Sierra Wireless IMEI. Really? Why would they do that? -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Sierra Wireless MC8355 - Gobi 3000 with ATT
Aleksander Morgado aleksan...@lanedo.com writes: On 03/10/13 10:15, Bjørn Mork wrote: Could very well be that they forbid using that APN with a Sierra Wireless IMEI. Really? Why would they do that? To force the APN to be used exclusively with handsets, because the provided services aren't suitable/scalable for high speed PC modems. This is just a wild and unfounded speculation from my side. I have no idea what ATT does. But I read from the APN docs that they would prefer other APNs for straight Internet access. From what I have gathered, mobile operator IP networks are typically a mess of firewalled services and weird accounting solutions, making it really inconvenient to provide both high speed Internet access and semi-private WAP gateway access using the same APN. But I don't know if this is true for all operators, and I don't know anything in particular about ATT. Bjørn ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Sierra Wireless MC8355 - Gobi 3000 with ATT
That was it: wrong APN. Perhaps MM or NM could be a bit more descriptive about the problem? I can patch it. Are there any other error you know of that provide a more verbose reason when encountered? I can follow the existing pattern, if there is one and add a message regarding the APN. Thanks again for the fast expert debug. -KB On Thu, 3 Oct 2013, Aleksander Morgado wrote: On 02/10/13 17:05, Kenneth Berland wrote: NM moves along well until it errors-out with these lines (I think): Oct 2 07:35:50 ken-x230 ModemManager[1811]: info error: couldn't start network: QMI protocol error (14): 'CallFailed' Oct 2 07:35:50 ken-x230 ModemManager[1811]: info call end reason (1018): 'gsm-wcdma-option-unsubscribed' Oct 2 07:35:50 ken-x230 ModemManager[1811]: info verbose call end reason (6,33): [3gpp] option-unsubscribed The 'gsm-wcdma-option-unsubscribed' error is actually the default error sent when the APN is wrong... I would really check what APN is being used. -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [patch network-manager-applet v2] add support for team devices
On Wednesday 25 of September 2013 17:18:35 Jiri Pirko wrote: Wed, Sep 25, 2013 at 04:46:48PM CEST, d...@gnome.org wrote: On 09/16/2013 03:28 AM, Jiri Pirko wrote: Hi, any comments please? I discussed this with jklimes and he seems happy with it. Sorry for the delay. Mostly good, and I see jklimes already fixed some things on the jklimes/team branch in git. I added another patch there to fix some layout problems. Two remaining questions: 1. Should we add a filepicker to the Team Port page like jklimes did on the team page? Both pages should behave the same in this aspect, so yes. 2. Does the team driver let you team InfiniBand devices with other devices? I know you can't do that with bonding because of the different hardware address size, and so there's code in page-bond.c to keep track of what kind of children the bond has, and after you've added one, you can't add the other kind any more. The team page, as it is now, will let you add both an ethernet and an infiniband device to the team. no, you cannot combine dev types. That should be probably addressed by a followup patch. But anyway, teamd would yell at you about this... -- Dan I have addressed both things in jklimes/team. Please review so that it could be closed. https://bugzilla.gnome.org/show_bug.cgi?id=708245 https://bugzilla.redhat.com/show_bug.cgi?id=1003646 Jirka ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
