Re: WAN Ericsson F3507g
Thanks Dan. Here is the output: NetworkManager: Activation (ttyACM0) starting connection 'Auto GSM network connection' NetworkManager: (ttyACM0): device state change: 3 -> 4 NetworkManager: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: [1226010840.735911] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: [1226010840.841058] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' NetworkManager: [1226010840.869797] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' NetworkManager: [1226010840.880689] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ERROR ' NetworkManager: init_done(): Modem initialization failed NetworkManager: (ttyACM0): device state change: 4 -> 9 NetworkManager: [1226010840.880892] nm_serial_device_close(): Closing device 'ttyACM0' NetworkManager: Marking connection 'Auto GSM network connection' invalid. NetworkManager: Activation (ttyACM0) failed. NetworkManager: (ttyACM0): device state change: 9 -> 3 NetworkManager: (ttyACM0): deactivating device (reason: 0). 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 The light on my laptop indicating that the device is on, never turned on using NM. But if I do: cu -l /dev/ttyACM0 AT+CFUN=1 Then the light does come on. I have 0.7~~svn20081018t105859-0ubuntu2~nm4 from the PPA on Intrepid. Thanks for your help. -James On Thu, 2008-11-06 at 07:35 -0500, Dan Williams wrote: > On Wed, 2008-11-05 at 15:36 -0700, James Ward wrote: > > Hi, > > > > I just recently upgraded to the Lenovo W500 laptop which has a built-in > > Ericsson F2507g WAN card. Unfortunately I can't get this new card to > > work with NM because it needs to be turned on first. There is a thread > > about how to do this manually on Ubuntu: > > http://ubuntuforums.org/showthread.php?t=934013 > > NetworkManager does turn the card on with CFUN=1 already. I'll need > serial debug logging enabled to figure out what's going on with your > card. Stop NM, then as root run it like: > > NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon > > and try a connection. Attach the output of NM so we can figure out > what's actually going wrong here. > > Dan > > > My sim card doesn't require a password like the newer ones so this > > should be pretty simple. But I can't seem to make it work. I'm using > > the Ubuntu NM PPA. Any ideas? > > > > Thanks. > > > > -James > > > > ___ > > 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: E71 Nokia with NetworkManager Applet 0.7.0 for 3G Internet connection
On Fri, Nov 7, 2008 at 12:48 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > On Thu, 2008-11-06 at 22:08 +0300, EMAD AL-BLOUSHI wrote: > > Dear All > > Honestly I would like to thank you for your valuable work besides I > > want to let you know about a little bug while using NetworkManager > > with E71 for 3G Internet connection using USB cable , it works > > perfectly but when I click on disconnect button nothing happen so > > kindly attached files for further details > > > > Finally, I'm using Ubuntu 8.10 - the Intrepid Ibex - released in October > 2008. > > If you could, stop NetworkManager, and then from a terminal as root: > > NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon > > then connect, and trigger your disconnect bug, and reply with a full log > of the NM output. > > Thanks! > Dan > I have done what you mentioned and I got this result when I run the command [EMAIL PROTECTED]:~$ sudo NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon NetworkManager: starting... NetworkManager: nm_dbus_manager_start_service(): Could not acquire the NetworkManager service as it is already taken. NetworkManager: disconnected by the system bus. NetworkManager: main(): Failed to start the dbus manager. Thanks, Emad Al-Bloushi ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: E71 Nokia with NetworkManager Applet 0.7.0 for 3G Internet connection
On Thu, 2008-11-06 at 22:08 +0300, EMAD AL-BLOUSHI wrote: > Dear All > Honestly I would like to thank you for your valuable work besides I > want to let you know about a little bug while using NetworkManager > with E71 for 3G Internet connection using USB cable , it works > perfectly but when I click on disconnect button nothing happen so > kindly attached files for further details > > Finally, I'm using Ubuntu 8.10 - the Intrepid Ibex - released in October > 2008. If you could, stop NetworkManager, and then from a terminal as root: NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon then connect, and trigger your disconnect bug, and reply with a full log of the NM output. Thanks! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Strange VPN problems
On Thu, 2008-11-06 at 18:24 +, Rick Jones wrote: > --On Thursday, November 06, 2008 16:49:29 + Rick Jones > <[EMAIL PROTECTED]> wrote: > > ¦ I take your point. In fact for my purpose I should really have a > gateway route just to 192.168.7.* via the VPN server. Can this kind of > routing policy be configured in NM? > ¦ > ¦ However, there's still a strange problem with these routes. If the > default route to the MB gateway on ppp0 is not present, then nothing > will go over the VPN on ppp1, not even the echo packets. Successful > echo depends _only_ on the existence of this route. Other > communication over the VPN depends on both this _and_ an explicit > route to the VPN server on ppp1. > ¦ > ¦ I've tried all kinds of route permutations, and it won't work if the > original MB default route is not there. It doesn't seem to make a lot > of sense, but that's what's happening. Maybe you can figure it out? > > Cracked it! > > There must be at minimum a gateway route to the VPN host via ppp0, > since pptp is using that to carry the VPN packets. By adding just that > route, everything then works. The routing table ends up as: > > 82.153.174.82 10.44.200.0 255.255.255.255 > UGH 0 00 ppp0 > 10.44.200.0 0.0.0.0 255.255.255.255 > UH0 00 ppp0 > 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 ppp1 > > The first line is the route I manually added. 82.153.174.82 is the > public address of my server, 10.44.200.0 is the MB gateway for the > current session. If the original default route via the MB gateway is > removed, then it must be replaced by this. This is how it should already work with recent VPN and PPTP fixes; I fixed a few PPTP things the other day. If it doesn't do this with latest SVN then it's a bug. > It would be nice to be able to set a policy of which addresses go via > the VPN, but it's not critical so long as this routing fix is made. You do this from the Routes dialog in the IPv4 tab of the connection editor Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Strange VPN problems
--On Thursday, November 06, 2008 16:49:29 + Rick Jones <[EMAIL PROTECTED]> wrote: ¦ I take your point. In fact for my purpose I should really have a gateway route just to 192.168.7.* via the VPN server. Can this kind of routing policy be configured in NM? ¦ ¦ However, there's still a strange problem with these routes. If the default route to the MB gateway on ppp0 is not present, then nothing will go over the VPN on ppp1, not even the echo packets. Successful echo depends _only_ on the existence of this route. Other communication over the VPN depends on both this _and_ an explicit route to the VPN server on ppp1. ¦ ¦ I've tried all kinds of route permutations, and it won't work if the original MB default route is not there. It doesn't seem to make a lot of sense, but that's what's happening. Maybe you can figure it out? Cracked it! There must be at minimum a gateway route to the VPN host via ppp0, since pptp is using that to carry the VPN packets. By adding just that route, everything then works. The routing table ends up as: 82.153.174.82 10.44.200.0 255.255.255.255 UGH 0 00 ppp0 10.44.200.0 0.0.0.0 255.255.255.255 UH0 00 ppp0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 ppp1 The first line is the route I manually added. 82.153.174.82 is the public address of my server, 10.44.200.0 is the MB gateway for the current session. If the original default route via the MB gateway is removed, then it must be replaced by this. It would be nice to be able to set a policy of which addresses go via the VPN, but it's not critical so long as this routing fix is made. (I'm sending this email logged into my IMAP server via VPN over MB, just to prove to myself it can be done!) -- Cheers Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Strange VPN problems
--On Thursday, November 06, 2008 07:33:07 -0500 Dan Williams <[EMAIL PROTECTED]> wrote: ¦ mobile broadband I assume? Yes, my main use for VPN is over MB. ¦ > When the VPN is up, this entry has gone, replaced by something that ¦ > looks to me like a meaningless route: ¦ > ¦ > 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp1 ¦ ¦ No, this is a default route through the VPN, which is expected, since ¦ there aren't any custom routes either sent by the VPN server or added by ¦ you. If there are no custom routes, everything will be sent through the ¦ VPN because you have not told NetworkManager what specific routes to use ¦ the VPN for. ¦ ¦ > Standard pptp leaves the default route alone, as it should. ¦ ¦ Maybe, maybe not :) It depends on policy. I take your point. In fact for my purpose I should really have a gateway route just to 192.168.7.* via the VPN server. Can this kind of routing policy be configured in NM? However, there's still a strange problem with these routes. If the default route to the MB gateway on ppp0 is not present, then nothing will go over the VPN on ppp1, not even the echo packets. Successful echo depends _only_ on the existence of this route. Other communication over the VPN depends on both this _and_ an explicit route to the VPN server on ppp1. I've tried all kinds of route permutations, and it won't work if the original MB default route is not there. It doesn't seem to make a lot of sense, but that's what's happening. Maybe you can figure it out? -- Cheers Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WAN Ericsson F3507g
Hello James, Ok, I'll try describe a process here to get this modem running. First, the thread you point to could make it work with a ppp connection. That is not the way to do it though, since it has a much more efficient way to do communication. Here is a alternative howto: 1. Patch your kernel with this patch: http://kerneltrap.org/mailarchive/linux-net/2008/10/29/3846534 2. After reboot with this new kernel, you should see like: dmesg: [ 20.122239] cdc_acm 5-8:1.1: usb_probe_interface [ 20.122243] cdc_acm 5-8:1.1: usb_probe_interface - got id [ 20.122322] cdc_acm 5-8:1.1: ttyACM0: USB ACM device [ 20.124354] cdc_acm 5-8:1.3: usb_probe_interface [ 20.124357] cdc_acm 5-8:1.3: usb_probe_interface - got id [ 20.124438] cdc_acm 5-8:1.3: ttyACM1: USB ACM device [ 20.127392] cdc_acm 5-8:1.9: usb_probe_interface [ 20.127395] cdc_acm 5-8:1.9: usb_probe_interface - got id [ 20.127481] cdc_acm 5-8:1.9: ttyACM2: USB ACM device [ 20.134318] usbcore: registered new interface driver cdc_acm [ 20.134322] drivers/usb/class/cdc-acm.c: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters [ 20.271221] usbcore: registered new interface driver cdc_ether [ 20.310117] mbm 5-8:1.7: usb_probe_interface [ 20.310121] mbm 5-8:1.7: usb_probe_interface - got id [ 20.329548] mbm 5-8:1.7: status ep7in, 8 bytes period 7 [ 20.329740] mb0: register 'mbm' at usb-:00:1d.7-8, MBM Mobile WAN Device, 02:80:37:ec:02:00 [ 20.329754] usbcore: registered new interface driver mbm You should also see a interface mb0 when you do ifconfig for example. 3. You can now test this manually, I mean without NetworkManager. Just to see that the driver part is ok. 3.1 Open /dev/ttyACM[0,1 or 2] in your favorite terminal emulator, this will give you an interface to do AT commands in. 3.2 You need a AT sequence like this to bring up your modem: 3.2.1 AT&F 3.2.2 AT+CFUN=1 3.2.3 AT*EIAC=1 3.2.4 AT*EIAPSW=1,1,"" 3.2.5 AT*ENAP=1,1 3.3 Now the connection should be up and you use dhclient to get an IP on mb0 like "dhclient mb0" or similar. 3.4 Time to start surf and read mails! :-) 4. To get NM to use this module, you currently need to work with the sources of NetworkManager and modemmanager. This is so far work in progress and I'm not sure when the distributions will pick these things up. Best regards, Per James Ward wrote: Hi, I just recently upgraded to the Lenovo W500 laptop which has a built-in Ericsson F2507g WAN card. Unfortunately I can't get this new card to work with NM because it needs to be turned on first. There is a thread about how to do this manually on Ubuntu: http://ubuntuforums.org/showthread.php?t=934013 My sim card doesn't require a password like the newer ones so this should be pretty simple. But I can't seem to make it work. I'm using the Ubuntu NM PPA. Any ideas? Thanks. -James ___ 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: WAN Ericsson F3507g
On Wed, 2008-11-05 at 15:36 -0700, James Ward wrote: > Hi, > > I just recently upgraded to the Lenovo W500 laptop which has a built-in > Ericsson F2507g WAN card. Unfortunately I can't get this new card to > work with NM because it needs to be turned on first. There is a thread > about how to do this manually on Ubuntu: > http://ubuntuforums.org/showthread.php?t=934013 NetworkManager does turn the card on with CFUN=1 already. I'll need serial debug logging enabled to figure out what's going on with your card. Stop NM, then as root run it like: NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon and try a connection. Attach the output of NM so we can figure out what's actually going wrong here. Dan > My sim card doesn't require a password like the newer ones so this > should be pretty simple. But I can't seem to make it work. I'm using > the Ubuntu NM PPA. Any ideas? > > Thanks. > > -James > > ___ > 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: Strange VPN problems
On Thu, 2008-11-06 at 12:09 +, Rick Jones wrote: > --On 06 November 2008 06:42 -0500 Dan Williams <[EMAIL PROTECTED]> > wrote: > ¦ > ¦ Is 192.168.7.128 the address of the VPN server? > > Yes > > ¦ > NM clearly doesn't insert a route to the VPN server > (192.168.7.128). > ¦ > ¦ But it should; if it doesn't there's a bug. There's currently a bug > ¦ where, upon DHCP renewal, NM will flush that host route to the VPN > ¦ gateway. I'm trying to fix that right now. > > Sounds like it could be the problem. The VPN server is also the DHCP > server, and I guess the client renews the lease on each connection. > ¦ > ¦ > It has also zapped the default route. Has this been fixed in > later > ¦ > build? > ¦ > ¦ If there are any custom routes sent by the VPN server (pptp doesn't > have > ¦ this capability) or entered by you in the IP4 Routes dialog, NM > assumes > ¦ that you do not want the VPN to be the default connection (if it > was, > ¦ any custom routes would be completely redundant). I don't think > that's > ¦ the case here, your issue looks like a bug. > > AFAIK the server is not doing anything fancy with routes. Prior to > establishing the VPN, the default route is to the MB host address: > > 0.0.0.0 10.36.193.0 0.0.0.0 UG0 0 > 0 ppp0 mobile broadband I assume? > When the VPN is up, this entry has gone, replaced by something that > looks to me like a meaningless route: > > 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 ppp1 No, this is a default route through the VPN, which is expected, since there aren't any custom routes either sent by the VPN server or added by you. If there are no custom routes, everything will be sent through the VPN because you have not told NetworkManager what specific routes to use the VPN for. > Standard pptp leaves the default route alone, as it should. Maybe, maybe not :) It depends on policy. Dan > ¦ Any idea what SVN revision your NM is based on? > > The package id on ppa.launchpad.net is > 0.7~~svn20081018t105859-0ubuntu2-nm2-hardy1. I guess that's from SVN > dated 2008/10/18, the other numbers don't mean anything to me. > > I've can confirm that routing is the sole cause of the problem - if I > make the VPN connection in NM, then immediately enter the missing > routes manually, it all works and stays connected, echo packets > function, etc. > > -- > Cheers > Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Strange VPN problems
--On 06 November 2008 06:42 -0500 Dan Williams <[EMAIL PROTECTED]> wrote: ¦ ¦ Is 192.168.7.128 the address of the VPN server? Yes ¦ > NM clearly doesn't insert a route to the VPN server (192.168.7.128). ¦ ¦ But it should; if it doesn't there's a bug. There's currently a bug ¦ where, upon DHCP renewal, NM will flush that host route to the VPN ¦ gateway. I'm trying to fix that right now. Sounds like it could be the problem. The VPN server is also the DHCP server, and I guess the client renews the lease on each connection. ¦ ¦ > It has also zapped the default route. Has this been fixed in a later ¦ > build? ¦ ¦ If there are any custom routes sent by the VPN server (pptp doesn't have ¦ this capability) or entered by you in the IP4 Routes dialog, NM assumes ¦ that you do not want the VPN to be the default connection (if it was, ¦ any custom routes would be completely redundant). I don't think that's ¦ the case here, your issue looks like a bug. AFAIK the server is not doing anything fancy with routes. Prior to establishing the VPN, the default route is to the MB host address: 0.0.0.0 10.36.193.0 0.0.0.0 UG0 00 ppp0 When the VPN is up, this entry has gone, replaced by something that looks to me like a meaningless route: 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 ppp1 Standard pptp leaves the default route alone, as it should. ¦ Any idea what SVN revision your NM is based on? The package id on ppa.launchpad.net is 0.7~~svn20081018t105859-0ubuntu2-nm2-hardy1. I guess that's from SVN dated 2008/10/18, the other numbers don't mean anything to me. I've can confirm that routing is the sole cause of the problem - if I make the VPN connection in NM, then immediately enter the missing routes manually, it all works and stays connected, echo packets function, etc. -- Cheers Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
