Re: Hello, please help with my 3G device
在 2012-7-17 PM2:46，"Aleksander Morgado" 写道： > > >>Hello, it works now! nearly perfect, but still another problem, how >>could I lock the >>network to 3g(td-scdma), and not automaticly switch back and forth between >>3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little >>low, >>and I'd like to not switch back to 2g. >> >>I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', >>then the profile >>didn't work. >> >>Again the detailed log. >> >>> >>> > >>> >I cannot see any "AT^SYSCFG" call in that log, which is the Huawei-specific >>> >way to get/set allowed modes.. so there's something wrong somewhere. >>> >Specifying the allowed mode in the Simple Connect settings should trigger >>> >mode change if the current allowed modes are different than the requested >>> >ones. >> >> Let me clarify it: its status not changed during one connection, but between >> different ones, that is, every time I reconnect, the status changed. and the log >> is only one time of them. >> > > I don't think you clarified it much :-) So the mode *does* change between connections or it *doesn't*? Can you provide full debug logs, including several connections and mode change requests? The mode does change between connections, and does not change during one(the same) connection, so the log is exactly the same between connections. Anyway, I'm already satisfied with the current situation, I can use it easily most of the time. Thank you very much. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
>>Hello, it works now! nearly perfect, but still another problem, how >>could I lock the >>network to 3g(td-scdma), and not automaticly switch back and forth between >>3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little >>low, >>and I'd like to not switch back to 2g. >> >>I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', >>then the profile >>didn't work. >> >>Again the detailed log. >> > >I cannot see any "AT^SYSCFG" call in that log, which is the Huawei-specific >way to get/set allowed modes.. so there's something wrong somewhere. >Specifying the allowed mode in the Simple Connect settings should trigger >mode change if the current allowed modes are different than the requested >ones. Let me clarify it: its status not changed during one connection, but between different ones, that is, every time I reconnect, the status changed. and the log is only one time of them. I don't think you clarified it much :-) So the mode *does* change between connections or it *doesn't*? Can you provide full debug logs, including several connections and mode change requests? -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
Probably your modem doesn't support mode switching with AT^SYSCFG then... I just found some manual [1], the command need an '?' after it, thus should be 'AT^SYSCFG?'. [1] http://www.letswireless.com.cn/cn/down/download.asp?id=81&t=en , section 10.6 on page 43 Yeah, we know that. We actually use already AT^SYSCFG? for loading of the currently allowed modes, and AT^SYSCFG=something to update it. Speaking of which, the same AT^SYSCFG is used for band and mode selection, and we seem to be hardcoding one of the values when requesting to modify the other. I added a task in the TODO file at git master to try to fix that; this is, when modifying the band use the current mode and when modifying the mode use the current band. Cheers, -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Mon, Jul 16, 2012 at 11:19 PM, Aleksander Morgado wrote: > Hello, it works now! nearly perfect, but still another problem, how could I lock the network to 3g(td-scdma), and not automaticly switch back and forth between 3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little low, and I'd like to not switch back to 2g. I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', then the profile didn't work. Again the detailed log. >>> >>> I cannot see any "AT^SYSCFG" call in that log, which is the >>> Huawei-specific >>> way to get/set allowed modes.. so there's something wrong somewhere. >>> Specifying the allowed mode in the Simple Connect settings should trigger >>> mode change if the current allowed modes are different than the requested >>> ones. >>> >>> Anyway, can you try to run the following between plugging the modem and >>> launching the connection request (assuming here the modem gets index 0)? >>> >>> $> sudo dbus-send \ >>> --system \ >>> --dest=org.freedesktop.ModemManager \ >>> --print-reply \ >>> /org/freedesktop/ModemManager/Modems/0 \ >>> org.freedesktop.ModemManager.Modem.Gsm.Network.SetAllowedMode \ >>> uint32:4 >> >> >> It simply return the following line: >> Error org.freedesktop.ModemManager.Modem.OperationNotSupported: >> Operation not supported >> > > Probably your modem doesn't support mode switching with AT^SYSCFG then... I just found some manual [1], the command need an '?' after it, thus should be 'AT^SYSCFG?'. [1] http://www.letswireless.com.cn/cn/down/download.asp?id=81&t=en , section 10.6 on page 43 -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 Welcome to minicom 2.6.1 OPTIONS: I18n Compiled on Feb 11 2012, 18:12:55. Port /dev/ttyACM0 Press CTRL-A Z for help on special keys AT^SYSCFG +CME ERROR: 3 AT^SYSCFG? ^SYSCFG: 15,2,,0,2 OK AT^SYSCONFIG? ^SYSCONFIG: 15,2,0,2 OK ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
Hello, it works now! nearly perfect, but still another problem, how could I lock the network to 3g(td-scdma), and not automaticly switch back and forth between 3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little low, and I'd like to not switch back to 2g. I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', then the profile didn't work. Again the detailed log. I cannot see any "AT^SYSCFG" call in that log, which is the Huawei-specific way to get/set allowed modes.. so there's something wrong somewhere. Specifying the allowed mode in the Simple Connect settings should trigger mode change if the current allowed modes are different than the requested ones. Anyway, can you try to run the following between plugging the modem and launching the connection request (assuming here the modem gets index 0)? $> sudo dbus-send \ --system \ --dest=org.freedesktop.ModemManager \ --print-reply \ /org/freedesktop/ModemManager/Modems/0 \ org.freedesktop.ModemManager.Modem.Gsm.Network.SetAllowedMode \ uint32:4 It simply return the following line: Error org.freedesktop.ModemManager.Modem.OperationNotSupported: Operation not supported Probably your modem doesn't support mode switching with AT^SYSCFG then... -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Mon, Jul 16, 2012 at 10:00 PM, Aleksander Morgado wrote: > >> Hello, it works now! nearly perfect, but still another problem, how >> could I lock the >> network to 3g(td-scdma), and not automaticly switch back and forth between >> 3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little >> low, >> and I'd like to not switch back to 2g. >> >> I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', >> then the profile >> didn't work. >> >> Again the detailed log. >> > > I cannot see any "AT^SYSCFG" call in that log, which is the Huawei-specific > way to get/set allowed modes.. so there's something wrong somewhere. > Specifying the allowed mode in the Simple Connect settings should trigger > mode change if the current allowed modes are different than the requested > ones. Let me clarify it: its status not changed during one connection, but between different ones, that is, every time I reconnect, the status changed. and the log is only one time of them. > Anyway, can you try to run the following between plugging the modem and > launching the connection request (assuming here the modem gets index 0)? > > $> sudo dbus-send \ > --system \ > --dest=org.freedesktop.ModemManager \ > --print-reply \ > /org/freedesktop/ModemManager/Modems/0 \ > org.freedesktop.ModemManager.Modem.Gsm.Network.SetAllowedMode \ > uint32:4 > > Cheers, > > -- > Aleksander -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Mon, Jul 16, 2012 at 10:00 PM, Aleksander Morgado wrote: > >> Hello, it works now! nearly perfect, but still another problem, how >> could I lock the >> network to 3g(td-scdma), and not automaticly switch back and forth between >> 3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little >> low, >> and I'd like to not switch back to 2g. >> >> I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', >> then the profile >> didn't work. >> >> Again the detailed log. >> > > I cannot see any "AT^SYSCFG" call in that log, which is the Huawei-specific > way to get/set allowed modes.. so there's something wrong somewhere. > Specifying the allowed mode in the Simple Connect settings should trigger > mode change if the current allowed modes are different than the requested > ones. > > Anyway, can you try to run the following between plugging the modem and > launching the connection request (assuming here the modem gets index 0)? > > $> sudo dbus-send \ > --system \ > --dest=org.freedesktop.ModemManager \ > --print-reply \ > /org/freedesktop/ModemManager/Modems/0 \ > org.freedesktop.ModemManager.Modem.Gsm.Network.SetAllowedMode \ > uint32:4 It simply return the following line: Error org.freedesktop.ModemManager.Modem.OperationNotSupported: Operation not supported -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
Hello, it works now! nearly perfect, but still another problem, how could I lock the network to 3g(td-scdma), and not automaticly switch back and forth between 3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little low, and I'd like to not switch back to 2g. I tried the option 'Type', change it from 'any' to '3G(UMTS/HSPA)', then the profile didn't work. Again the detailed log. I cannot see any "AT^SYSCFG" call in that log, which is the Huawei-specific way to get/set allowed modes.. so there's something wrong somewhere. Specifying the allowed mode in the Simple Connect settings should trigger mode change if the current allowed modes are different than the requested ones. Anyway, can you try to run the following between plugging the modem and launching the connection request (assuming here the modem gets index 0)? $> sudo dbus-send \ --system \ --dest=org.freedesktop.ModemManager \ --print-reply \ /org/freedesktop/ModemManager/Modems/0 \ org.freedesktop.ModemManager.Modem.Gsm.Network.SetAllowedMode \ uint32:4 Cheers, -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
The Huawei plugin always starts probing USB interface 0; and it seems that none of the 3 ttyACM ports given has usbif 0, so never starts probing the other ports. The plugin should possibly wait up to N seconds for usbif 0 to appear, and keep on probing normally if it doesn't appear in that time. Will try to prepare a patch for that. Great! cannot wait to try :) Attached is a patch to apply on top of the MM_05 branch of ModemManager: $> git clone git://anongit.freedesktop.org/ModemManager/ModemManager $> cd ModemManager $> git checkout -b MM_05 origin/MM_05 $> git am /path/to/the/patch.diff $> ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var $> make $> sudo make install It is not a perfect solution, but should do the trick. I'll find a better fix for git master/0.7; as I do have some probing improvements ready there which would help quite a lot also in this case. Let me know if it worked or not, as I don't have any Huawei modem around to play with. Please attach debug logs in any case. Hello, it partially works. I can find the device in nm now, but when try to connect to 3g net, it fails. Seems we're mixing up which is the port we use for control and the one we use for PPP. Can you run "AT^GETPORTMODE" with minicom in each of the ttyUSB? I suppose you mean ttACM*? I tried and all of them returned simple 'ERROR', seems not support that AT command. and I do it while connecting to 3g net via wvdial, the result is different: ACM0 just says locked, ACM1 respones the same to the situation when offline, ACM2 instantly return some '^DSFLOWRPT' and '*PHBI'. Ah wait, just found an error in your setup. When selecting a number to call in the connection profile, do *not* explicitly list the PDP context to use, so don't write "*99***1", write instead: "*99#". It seems we're building the wrong ATD call if you explicitly select the PDP context: (ttyACM0): --> 'ATD*99***1***2#' (ttyACM0): <-- '+CME ERROR: 3' Just provide a proper APN to connect to in your connection profile, and MM will try to create the PDP context if it doesn't exist or just connect to an already available one. The ports mismatch may end up not being an issue here as there seems to be no mismatch (ttyACM0 really seems to be the port to use for control). -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Mon, Jul 16, 2012 at 1:09 PM, Aleksander Morgado wrote: > > The Huawei plugin always starts probing USB interface 0; and it seems > that none of the 3 ttyACM ports given has usbif 0, so never starts > probing the other ports. The plugin should possibly wait up to N > seconds > for usbif 0 to appear, and keep on probing normally if it doesn't > appear > in that time. > > Will try to prepare a patch for that. Great! cannot wait to try :) >>> >>> Attached is a patch to apply on top of the MM_05 branch of ModemManager: >>>$> git clone git://anongit.freedesktop.org/ModemManager/ModemManager >>>$> cd ModemManager >>>$> git checkout -b MM_05 origin/MM_05 >>>$> git am /path/to/the/patch.diff >>>$> ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var >>>$> make >>>$> sudo make install >>> >>> It is not a perfect solution, but should do the trick. I'll find a >>> better fix for git master/0.7; as I do have some probing improvements >>> ready there which would help quite a lot also in this case. >>> >>> Let me know if it worked or not, as I don't have any Huawei modem around >>> to play with. Please attach debug logs in any case. >> >> >> Hello, it partially works. >> >> I can find the device in nm now, but when try to connect to 3g net, it >> fails. >> > > Seems we're mixing up which is the port we use for control and the one we > use for PPP. Can you run "AT^GETPORTMODE" with minicom in each of the > ttyUSB? I suppose you mean ttACM*? I tried and all of them returned simple 'ERROR', seems not support that AT command. and I do it while connecting to 3g net via wvdial, the result is different: ACM0 just says locked, ACM1 respones the same to the situation when offline, ACM2 instantly return some '^DSFLOWRPT' and '*PHBI'. -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 emfox@emfox:~$ sudo minicom -D /dev/ttyACM0 Device /dev/ttyACM0 is locked. emfox@emfox:~$ sudo minicom -D /dev/ttyACM1 Welcome to minicom 2.6.1 OPTIONS: I18n Compiled on Feb 11 2012, 18:12:55. Port /dev/ttyACM1 Press CTRL-A Z for help on special keys AT OK ATZ OK AT+CGDCONT? +CGDCONT: 1,"IP","CMWAP","0.0.0.0",0,0 +CGDCONT: 2,"IP","cmnet","0.0.0.0",0,0 +CGDCONT: 3,"IP","","0.0.0.0",0,0 OK AT^GETPORTMODE ERROR AT ^ GETPORTMODE ERROR AT^SETPORT? ERROR emfox@emfox:~$ sudo minicom -D /dev/ttyACM2 Welcome to minicom 2.6.1 OPTIONS: I18n Compiled on Feb 11 2012, 18:12:55. Port /dev/ttyACM2 Press CTRL-A Z for help on special keys ^DSFLOWRPT: 0196,,,000c8189,005a5b3f,0097,0097 ^DSFLOWRPT: 0198,,,000c8189,005a5b3f,0097,0097 ^DSFLOWRPT: 019a,,,000c8189,005a5b3f,0097,0097 ^DSFLOWRPT: 019c,,,000c8189,005a5b3f,0097,0097 ^DSFLOWRPT: 01b0,,,000c8da4,005a6df0,0097,0097 ^DSFLOWRPT: 01b2,00a7,009b,000c8ef3,005a6f26,0097,0097 ^DSFLOWRPT: 01b4,,,000c8ef3,005a6f26,0097,0097 ^DSFLOWRPT: 01b6,,,000c8ef3,005a6f26,0097,0097 ^DSFLOWRPT: 01b8,,,000c8ef3,005a6f26,0097,0097 ^DSFLOWRPT: 01ba,,,000c8ef3,005a6f26,0097,0097 *PHBI: 0,1 ^DSFLOWRPT: 01bc,,,000c8ef3,005a6f26,0097,0097 ^DSFLOWRPT: 01be,,,000c8ef3,005a6f26,0097,0097 ^DSFLOWRPT: 01c0,,,000c8ef3,005a6f26,0097,0097 *PHBI: 0,2 ^DSFLOWRPT: 01c2,04f4,0173,000c98dc,005a720c,0097,0097 ^DSFLOWRPT: 01c4,00c1,0046,000c9a5f,005a7298,0097,0097 ^DSFLOWRPT: 01c6,,,000c9a5f,005a7298,0097,0097 ^DSFLOWRPT: 01c8,00b6,073f,000c9bcb,005a8117,0097,0097 ^DSFLOWRPT: 01ca,001a,001a,000c9bff,005a814b,0097,0097 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
The Huawei plugin always starts probing USB interface 0; and it seems that none of the 3 ttyACM ports given has usbif 0, so never starts probing the other ports. The plugin should possibly wait up to N seconds for usbif 0 to appear, and keep on probing normally if it doesn't appear in that time. Will try to prepare a patch for that. Great! cannot wait to try :) Attached is a patch to apply on top of the MM_05 branch of ModemManager: $> git clone git://anongit.freedesktop.org/ModemManager/ModemManager $> cd ModemManager $> git checkout -b MM_05 origin/MM_05 $> git am /path/to/the/patch.diff $> ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var $> make $> sudo make install It is not a perfect solution, but should do the trick. I'll find a better fix for git master/0.7; as I do have some probing improvements ready there which would help quite a lot also in this case. Let me know if it worked or not, as I don't have any Huawei modem around to play with. Please attach debug logs in any case. Hello, it partially works. I can find the device in nm now, but when try to connect to 3g net, it fails. Seems we're mixing up which is the port we use for control and the one we use for PPP. Can you run "AT^GETPORTMODE" with minicom in each of the ttyUSB? -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
Hey,
>>
Can you get ModemManager debug logs by following the steps given in
section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the
following page?:
https://live.gnome.org/NetworkManager/Debugging
>>>
>>> Hello, thanks for replying, here's the logs.
>>>
>>
>> The Huawei plugin always starts probing USB interface 0; and it seems
>> that none of the 3 ttyACM ports given has usbif 0, so never starts
>> probing the other ports. The plugin should possibly wait up to N seconds
>> for usbif 0 to appear, and keep on probing normally if it doesn't appear
>> in that time.
>>
>> Will try to prepare a patch for that.
>
> Great! cannot wait to try :)
>
Attached is a patch to apply on top of the MM_05 branch of ModemManager:
$> git clone git://anongit.freedesktop.org/ModemManager/ModemManager
$> cd ModemManager
$> git checkout -b MM_05 origin/MM_05
$> git am /path/to/the/patch.diff
$> ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var
$> make
$> sudo make install
It is not a perfect solution, but should do the trick. I'll find a
better fix for git master/0.7; as I do have some probing improvements
ready there which would help quite a lot also in this case.
Let me know if it worked or not, as I don't have any Huawei modem around
to play with. Please attach debug logs in any case.
Cheers!
--
Aleksander
>From d36dcdd2c13f01dafc994d9b60f68e568a8f8ea0 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado
Date: Sun, 15 Jul 2012 18:26:11 +0200
Subject: [PATCH] huawei: limit the number of deferred tasks
The Huawei plugin requires to probe first the USB interface 0; all the other
probing tasks in the remaining ports will get deferred until the interface 0
gets probed. But, some modems (e.g. Huawei ET8282), don't expose the USB
interface 0 as an AT port, so we get an infinite loop as no port ends up being
probed.
In order to fix this, we will limit to a predefined maximum the number of times a given probing task is deferred, 4 in this case. So, if a given probing task is
deferred for more than 4x3s=12s, probing will get forced.
---
plugins/mm-plugin-huawei.c | 30 --
1 file changed, 28 insertions(+), 2 deletions(-)
diff --git a/plugins/mm-plugin-huawei.c b/plugins/mm-plugin-huawei.c
index fe7ffa0..d861a37 100644
--- a/plugins/mm-plugin-huawei.c
+++ b/plugins/mm-plugin-huawei.c
@@ -159,6 +159,9 @@ add_regex (MMAtSerialPort *port, const char *match, gpointer user_data)
g_regex_unref (regex);
}
+#define TAG_DEFER_COUNTS_PREFIX "huawei-defer-counts"
+#define MAX_DEFERS 4
+
static MMPluginSupportsResult
supports_port (MMPluginBase *base,
MMModem *existing,
@@ -198,8 +201,31 @@ supports_port (MMPluginBase *base,
* we need to use the first port that does respond to probing to create the
* right type of mode (GSM or CDMA), and then re-check the other interfaces.
*/
-if (!existing && usbif != 0)
-return MM_PLUGIN_SUPPORTS_PORT_DEFER;
+if (!existing && usbif != 0) {
+gchar *tag;
+guint n_deferred;
+
+/* We need to defer the probing as usbif 0 wasn't probed yet. We need to
+ * protect against the case of not having usbif 0 as an AT port, and we
+ * do that by limiting the number of times we defer the probing. */
+
+tag = g_strdup_printf ("%s-%s/%s", TAG_DEFER_COUNTS_PREFIX, subsys, name);
+/* First time requested will be 0 */
+n_deferred = GPOINTER_TO_UINT (g_object_get_data (G_OBJECT (base), tag));
+if (n_deferred < MAX_DEFERS) {
+/* Update defer count */
+g_object_set_data (G_OBJECT (base), tag, GUINT_TO_POINTER (n_deferred + 1));
+g_free (tag);
+return MM_PLUGIN_SUPPORTS_PORT_DEFER;
+}
+
+mm_dbg ("(%s): no longer waiting for usbif 0, will launch probing in interface (%s/%s)",
+mm_plugin_get_name (MM_PLUGIN (base)), subsys, name);
+g_free (tag);
+
+/* Clear tag */
+g_object_set_data (G_OBJECT (base), tag, NULL);
+}
/* CDMA devices don't have problems with the secondary ports, so after
* ensuring we have a device by probing the first port, probe the secondary
--
1.7.10.4
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Sun, Jul 15, 2012 at 11:25 PM, Aleksander Morgado wrote: > Hey, > >>> Can you get ModemManager debug logs by following the steps given in >>> section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the >>> following page?: >>> https://live.gnome.org/NetworkManager/Debugging >> >> Hello, thanks for replying, here's the logs. >> > > The Huawei plugin always starts probing USB interface 0; and it seems > that none of the 3 ttyACM ports given has usbif 0, so never starts > probing the other ports. The plugin should possibly wait up to N seconds > for usbif 0 to appear, and keep on probing normally if it doesn't appear > in that time. > > Will try to prepare a patch for that. Great! cannot wait to try :) -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
Hey, >> >>> It's a Huawei ET8282, TD-SCDMA HSDPA 3g mobile broadbrand card. >>> It's on ExpessCard, but appears to be a stand USB device in my Debian >>> Squeeze Box. >>> >>> I have made it to work with wvdial by usb-modeswitch. yes, it's a device >>> with id 12d1:1da1, after eject the cd, it became 12d1:1d09, and >>> /dev/ttyACM[0-2] turn up, the I could use it by manual pon/poff, wvdial >>> and gnome-ppp, connecting to the 3g net without any problem. >>> >>> But I even cannot see it in Network Manager device list, when I want to >>> create a connection, the list is gray out. >>> >>> Here's some infos of my device, since it even does not appear in Network >>> Mananger, I do not know what log else should attach, if any need, please >>> tell me. >>> >> >> Can you get ModemManager debug logs by following the steps given in >> section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the >> following page?: >> https://live.gnome.org/NetworkManager/Debugging > > Hello, thanks for replying, here's the logs. > The Huawei plugin always starts probing USB interface 0; and it seems that none of the 3 ttyACM ports given has usbif 0, so never starts probing the other ports. The plugin should possibly wait up to N seconds for usbif 0 to appear, and keep on probing normally if it doesn't appear in that time. Will try to prepare a patch for that. -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Sun, Jul 15, 2012 at 10:22 PM, Aleksander Morgado wrote: > >> It's a Huawei ET8282, TD-SCDMA HSDPA 3g mobile broadbrand card. >> It's on ExpessCard, but appears to be a stand USB device in my Debian >> Squeeze Box. >> >> I have made it to work with wvdial by usb-modeswitch. yes, it's a device >> with id 12d1:1da1, after eject the cd, it became 12d1:1d09, and >> /dev/ttyACM[0-2] turn up, the I could use it by manual pon/poff, wvdial >> and gnome-ppp, connecting to the 3g net without any problem. >> >> But I even cannot see it in Network Manager device list, when I want to >> create a connection, the list is gray out. >> >> Here's some infos of my device, since it even does not appear in Network >> Mananger, I do not know what log else should attach, if any need, please >> tell me. >> > > Can you get ModemManager debug logs by following the steps given in > section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the > following page?: > https://live.gnome.org/NetworkManager/Debugging Hello, thanks for replying, here's the logs. -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 emfox@emfox:~$ sudo /etc/init.d/network-manager stop [ ok ] Stopping network connection manager: NetworkManager. emfox@emfox:~$ sudo killall -TERM modem-manager emfox@emfox:~$ sudo modem-manager --debug modem-manager[9926]: [1342362975.036471] [main.c:167] main(): ModemManager (version 0.5.2.0) starting... modem-manager[9926]: [1342362975.038615] [mm-manager.c:120] load_plugin(): Loaded plugin Nokia modem-manager[9926]: [1342362975.038839] [mm-manager.c:120] load_plugin(): Loaded plugin Option modem-manager[9926]: [1342362975.039003] [mm-manager.c:120] load_plugin(): Loaded plugin Linktop modem-manager[9926]: [1342362975.048647] [mm-manager.c:120] load_plugin(): Loaded plugin X22X modem-manager[9926]: [1342362975.063517] [mm-manager.c:120] load_plugin(): Loaded plugin Huawei modem-manager[9926]: [1342362975.064326] [mm-manager.c:120] load_plugin(): Loaded plugin Option High-Speed modem-manager[9926]: [1342362975.064748] [mm-manager.c:120] load_plugin(): Loaded plugin Novatel modem-manager[9926]: [1342362975.065436] [mm-manager.c:120] load_plugin(): Loaded plugin ZTE modem-manager[9926]: [1342362975.065635] [mm-manager.c:120] load_plugin(): Loaded plugin Gobi modem-manager[9926]: [1342362975.066077] [mm-manager.c:120] load_plugin(): Loaded plugin AnyData modem-manager[9926]: [1342362975.066775] [mm-manager.c:120] load_plugin(): Loaded plugin Wavecom modem-manager[9926]: [1342362975.067526] [mm-manager.c:120] load_plugin(): Loaded plugin Samsung modem-manager[9926]: [1342362975.067686] [mm-manager.c:120] load_plugin(): Loaded plugin Longcheer modem-manager[9926]: [1342362975.067854] [mm-manager.c:120] load_plugin(): Loaded plugin Generic modem-manager[9926]: [1342362975.068265] [mm-manager.c:120] load_plugin(): Loaded plugin MotoC modem-manager[9926]: [1342362975.068941] [mm-manager.c:120] load_plugin(): Loaded plugin Sierra modem-manager[9926]: [1342362975.069392] [mm-manager.c:120] load_plugin(): Loaded plugin Ericsson MBM modem-manager[9926]: [1342362975.069742] [mm-manager.c:120] load_plugin(): Loaded plugin SimTech modem-manager[9926]: [1342362975.072600] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyACM0) deferring support check modem-manager[9926]: [1342362975.073581] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyACM1) deferring support check modem-manager[9926]: [1342362975.074526] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyACM2) deferring support check modem-manager[9926]: [1342362975.074692] [mm-manager.c:809] device_added(): (tty/ttyS0): port's parent platform driver is not whitelisted modem-manager[9926]: [1342362975.074849] [mm-manager.c:809] device_added(): (tty/ttyS1): port's parent platform driver is not whitelisted modem-manager[9926]: [1342362975.075000] [mm-manager.c:809] device_added(): (tty/ttyS2): port's parent platform driver is not whitelisted modem-manager[9926]: [1342362975.075142] [mm-manager.c:809] device_added(): (tty/ttyS3): port's parent platform driver is not whitelisted modem-manager[9926]: [1342362978.074793] [mm-manager.c:457] supports_defer_timeout(): (ttyACM0): re-checking support... modem-manager[9926]: [1342362978.075812] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyACM0) deferring support check modem-manager[9926]: [1342362978.075887] [mm-manager.c:457] supports_defer_timeout(): (ttyACM1): re-checking support... modem-manager[9926]: [1342362978.076602] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyACM1) deferring support check modem-manager[9926]: [1342362978.076668] [mm-manager.c:457] supports_defer_timeout(): (ttyACM2): re-checking support... modem-manager[9926]: [1342362978.077373] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyACM2) deferring support check modem-manager[9926]: [1342362981.079631] [mm-manager.c:457] supports_defer_timeout(): (ttyACM0):
Re: Hello, please help with my 3G device
> It's a Huawei ET8282, TD-SCDMA HSDPA 3g mobile broadbrand card. > It's on ExpessCard, but appears to be a stand USB device in my Debian > Squeeze Box. > > I have made it to work with wvdial by usb-modeswitch. yes, it's a device > with id 12d1:1da1, after eject the cd, it became 12d1:1d09, and > /dev/ttyACM[0-2] turn up, the I could use it by manual pon/poff, wvdial > and gnome-ppp, connecting to the 3g net without any problem. > > But I even cannot see it in Network Manager device list, when I want to > create a connection, the list is gray out. > > Here's some infos of my device, since it even does not appear in Network > Mananger, I do not know what log else should attach, if any need, please > tell me. > Can you get ModemManager debug logs by following the steps given in section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the following page?: https://live.gnome.org/NetworkManager/Debugging Cheers, -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello, please help with my 3G device
On Sat, Jul 14, 2012 at 10:00 PM, Emfox Zhou wrote: > It's a Huawei ET8282, TD-SCDMA HSDPA 3g mobile broadbrand card. > It's on ExpessCard, but appears to be a stand USB device in my Debian > Squeeze Box. > > I have made it to work with wvdial by usb-modeswitch. yes, it's a device > with id 12d1:1da1, after eject the cd, it became 12d1:1d09, and > /dev/ttyACM[0-2] turn up, the I could use it by manual pon/poff, wvdial > and gnome-ppp, connecting to the 3g net without any problem. > > But I even cannot see it in Network Manager device list, when I want to > create a connection, the list is gray out. > > Here's some infos of my device, since it even does not appear in Network > Mananger, I do not know what log else should attach, if any need, please > tell me. forgot to tell, NetworkManager is version 0.9.4.0, while ModemManager is 0.5.2.0. -- Emfox Zhou GnuPG Public Key: 0xF7142EC2 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello
On Fri, 1 Jun 2007, [ISO-8859-1] J�rg Billeter wrote: > > The source code control now uses svn. The URL is > > svn://websvn.kde.org/home/kde/trunk/extragear/network/knetworkmanager. > That's only the KDE GUI, the core is at > http://svn.gnome.org/svn/NetworkManager/trunk > > The GNOME applet is at > http://svn.gnome.org/svn/network-manager-applet/trunk So, if I want to add a quit option to the applet, as I suggested, I'd start with "network-manager-applet"? -- David Griffith [EMAIL PROTECTED] A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello
On Fre, 2007-06-01 at 13:06 -0500, Larry Finger wrote: > Benjamin Kreuter wrote: > > Also, I am having trouble connecting to anoncvs.gnome.org -- is this server > > still in use? If not, which repository should I be using (and why does the > > website still say to get files from there)? > > The source code control now uses svn. The URL is > svn://websvn.kde.org/home/kde/trunk/extragear/network/knetworkmanager. That's only the KDE GUI, the core is at http://svn.gnome.org/svn/NetworkManager/trunk The GNOME applet is at http://svn.gnome.org/svn/network-manager-applet/trunk HTH, Jürg ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello
On Fri, 2007-06-01 at 13:06 -0500, Larry Finger wrote: > Benjamin Kreuter wrote: > > Hi All -- > > > > My name is Benjamin Kreuter, and I'm going to be contributing a bit to > > NetworkManager this summer, and possibly after that. I just thought I > > would > > announce myself to the list. > > > > Also, I am having trouble connecting to anoncvs.gnome.org -- is this server > > still in use? If not, which repository should I be using (and why does the > > website still say to get files from there)? > > The source code control now uses svn. The URL is > svn://websvn.kde.org/home/kde/trunk/extragear/network/knetworkmanager. > > I don't know why the website is out of date. Because I'm lazy. Dan > > Larry > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello
Benjamin Kreuter wrote: > Hi All -- > > My name is Benjamin Kreuter, and I'm going to be contributing a bit to > NetworkManager this summer, and possibly after that. I just thought I would > announce myself to the list. > > Also, I am having trouble connecting to anoncvs.gnome.org -- is this server > still in use? If not, which repository should I be using (and why does the > website still say to get files from there)? The source code control now uses svn. The URL is svn://websvn.kde.org/home/kde/trunk/extragear/network/knetworkmanager. I don't know why the website is out of date. Larry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Hello everybody
On Mon, 2005-02-14 at 16:36 +, Rui Campos wrote: > Hi Dan, > > Thanks for your quick answers! > > I am wondering whether "Network Manager" could manage such a switch in a > transparent way for the applications. Anyway, you already answered this > question in our comprehensive explanation. Thanks for that! Without something like Mobile-IP, I think it's impossible not to break existing IP connections. Instead, we need to make applications aware of the network events that NM broadcasts, like "network now up" and "network now down". In the gaim example, when gaim receives the "down" signal, it should disconnect its connections, and wait for the "up" signal. If it receives that signal within, say, 10 seconds, it should reconnect the connections that were broken by the "down" event. If not, perhaps it should display the "You were disconnected" dialog. Its a hard problem, because there is no guarantee how long the network will stay "down". The user may be searching for the correct WEP key or passphrase, may be away from their desk when the passphrase dialog pops up, or they may have traveled to an area where no network connection is possible. Applications have to take into account that the network does not have to come back up immediately. Really, they have to be anything other than incompetent about network state, which is what they are now. Evolution, for example, has online/offline modes, but it expects the network to be available when you choose "offline", because it tells each of its backends (IMAP, POP3, etc) to move to offline mode where each backend may do something like cache mail. That takes time. In the NM model, you don't have any time since the network has already gone away. > In my PhD thesis (I just started four months ago :-)), I am looking for > mobility and multihoming support in an integrated fashion, in a > heterogeneous environment. The kind of mobility support I am interested in > is similar to that provided by Mobile IP framework, i.e. changes in network > access are transparent to transport and application layer. > > P.S. By the way, have you ever considered some kind of synergy between > Mobile IP and such a Network Manager? I had talked about it with one of our other guys here quite a while back. I just went and read http://www.computer.org/internet/v2n1/perkins.htm to brush up a bit. It appears that this would need both kernel-side and user-space-side components. First, on the kernel side, we need to ensure that the encapsulated packets from the home agent are decapsulated correctly and delivered to the upper layers of the TCP stack with the correct home IP address intact. That seems like a job of the network stack or of iptables, which can rewrite packets depending on certain rules. Of course, since these rules would be dynamic, iptables might need modification. But certainly something on the kernel side needs it. On the user-space side, where NM lives, we'd need a couple more things. First, when we move to new networks, we would need to broadcast a request for a new "care-of" address. Once the reply was received, NM would need to notify the kernel of the new care-of address so it could rewrite the packets correctly. NM would then need to ensure that the care-of address works correctly, then notify the home-agent of the new care-of address. NM would then need to set up the IP-within-IP tunnel. Once that is done, the network is more or less "up" and applications could send and receive data with no interruption. In an upcoming rewrite of NM (starting this spring), I hope to make the NM architecture more modular to support more services and devices. For example, the Mobile-IP bits don't really need to be a core part of NM, but could be a service that NM depends on and makes requests of. Something like "Hi, Mobile-IP, please get a new care-of address and tell me when you're done." The mobile IP bits don't need to know which network you're connecting to (ie wired, wireless, whatever), they just need to know which particular network interface to start operating on. NM doesn't need to know about the details of the Mobile-IP negotiations, just when they either complete successfully, or fail, so that NM can announce the network as "up" or switch the connection to something else. As long as the kernel facilities are there to support Mobile-IP, the packet encapsulation/decapsulation, and delivery of packets with the correct "Home" IP address to the application layers, I think this isn't a hard problem to solve. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Hello everybody
Hi Dan, Thanks for your quick answers! I am wondering whether "Network Manager" could manage such a switch in a transparent way for the applications. Anyway, you already answered this question in our comprehensive explanation. Thanks for that! In my PhD thesis (I just started four months ago :-)), I am looking for mobility and multihoming support in an integrated fashion, in a heterogeneous environment. The kind of mobility support I am interested in is similar to that provided by Mobile IP framework, i.e. changes in network access are transparent to transport and application layer. I hope I have answered your question! BR, Rui Campos P.S. By the way, have you ever considered some kind of synergy between Mobile IP and such a Network Manager? -Original Message- From: Dan Williams [mailto:[EMAIL PROTECTED] Sent: segunda-feira, 14 de Fevereiro de 2005 16:18 To: Rui Campos Cc: networkmanager-list@gnome.org Subject: Re: Hello everybody On Mon, 2005-02-14 at 15:53 +, Rui Campos wrote: > I am doing my PhD in the networking area (particularly in Mobile > Networks) and I am very interested in this Network Manager, you have > been designing and implementing. Can anybody tell me a bit more about > it? For example, are you considering things like Mobility, i.e. > always-on connectivity service? In the web page of the project, I > think that you don't refer explicitly to such a feature! Hi, Great to hear you're interested. The point of NetworkManager was to _attempt_ to provide a network connection no matter where you are. Eventually, we hope to support things like Bluetooth, GPRS, and probably ISDN and modems as well. The auto-switching capability is a large part of this, for example: if you've been using the wireless network, and you plug in the cable, NM will switch your connection to the cable. When you unplug (or undock) it will switch to wireless. NM attempts to be as automatic as possible. Some issues that get in the way are likely to be solved in the future, for example not all wired cards support link-detection right now, and NM just ignores those cards unless you explicitly tell it to switch to them. Furthermore, many wireless cards don't report correct signal quality, making it impossible to pick wireless base stations based on their quality or proximity. This stuff slowly gets fixed in the kernel though. Many applications (like gaim or evolution) also aren't aware of network changes, so when NM switches the network connection gaim pops up a "you've been disconnected" dialog. Support for NetworkManager will gradually work its way into these apps. We don't support WPA or other types of authentication besides WEP right now, but that will hopefully be fixed in the coming months. Again, that needs to be seamless so the user is minimally interrupted. Could you explain a bit more about the areas of mobility that you're interested in, or some of the things you're looking at for your thesis? Thanks Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Hello everybody
On Mon, 2005-02-14 at 15:53 +, Rui Campos wrote: > I am doing my PhD in the networking area (particularly in Mobile > Networks) and I am very interested in this Network Manager, you have > been designing and implementing. Can anybody tell me a bit more about > it? For example, are you considering things like Mobility, i.e. > always-on connectivity service? In the web page of the project, I > think that you donât refer explicitly to such a feature! Hi, Great to hear you're interested. The point of NetworkManager was to _attempt_ to provide a network connection no matter where you are. Eventually, we hope to support things like Bluetooth, GPRS, and probably ISDN and modems as well. The auto-switching capability is a large part of this, for example: if you've been using the wireless network, and you plug in the cable, NM will switch your connection to the cable. When you unplug (or undock) it will switch to wireless. NM attempts to be as automatic as possible. Some issues that get in the way are likely to be solved in the future, for example not all wired cards support link-detection right now, and NM just ignores those cards unless you explicitly tell it to switch to them. Furthermore, many wireless cards don't report correct signal quality, making it impossible to pick wireless base stations based on their quality or proximity. This stuff slowly gets fixed in the kernel though. Many applications (like gaim or evolution) also aren't aware of network changes, so when NM switches the network connection gaim pops up a "you've been disconnected" dialog. Support for NetworkManager will gradually work its way into these apps. We don't support WPA or other types of authentication besides WEP right now, but that will hopefully be fixed in the coming months. Again, that needs to be seamless so the user is minimally interrupted. Could you explain a bit more about the areas of mobility that you're interested in, or some of the things you're looking at for your thesis? Thanks Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
