Re: Mobile broadband and carriers
On Tue, Jan 20, 2009 at 10:18:01AM -0500, Dan Williams wrote: > Which exact version of NetworkManager are you using? It looks like > NetworkManager cannot properly initialize the phone to be able to check > for a PIN. This could be due to the older version of NM that Ubuntu > ships, we've done some work in NetworkManager since that version > (including the actual 0.7.0 release) that fixes that issue for many > devices (by trying alternate init commands). Trying the latest NM from > the PPA might help to isolate that issue. FWIW, here the PPA address http://launchpad.net/~network-manager/+archive > > If the latest Ubuntu bits fail, then open a Terminal, become root, stop > the NetworkManager service, and execute the following command: > > NM_SERIAL_DEBUG=1 NetworkManager --no-daemon > > then wait about 10 seconds, and try your 3G connection. Grab the output > that NM spits out into the terminal, and paste it into a reply to this > message. > - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband and carriers
On Tue, 2009-01-20 at 13:26 +0200, Janne Boman wrote: > Marc Luethi wrote: > > > > Try disabling Wireless globally in NM before starting the Mobile > > Broadband connection. > > > > I can't get Mobile Broadband to work either on my Ubuntu 8.10 while any > > WiFi or LAN connection remains enabled. It results in a very wierd > > setup, where the default route remains on the wlan0 interface (or eth0, > > for that matter...). > > > > ~$ route -n > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Iface > > 10.6.6.60.0.0.0 255.255.255.255 UH0 ppp0 > > 172.20.124.00.0.0.0 255.255.255.0 U 2 wlan0 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 1000ppp0 > > 0.0.0.0 172.20.124.10.0.0.0 UG0 wlan0 > > > > > > Yet, the Mobile ISP's DNS servers take precedence over the WLAN ones: > > > > m...@torch:~$ more /etc/resolv.conf > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > > resolvconf(8) > > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > > nameserver 138.188.101.186 > > nameserver 138.188.101.189 > > nameserver 172.20.124.1 > > > > > > > > This can't work, really - what if the Mobile ISP assigns DNS addresses > > that are not routeable via the WLAN network? > > > > > > regards > > > > Marc > > > > > > ___ > > NetworkManager-list mailing list > > NetworkManager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > Now I've got something, here is the relevant part from > /var/log/daemon.log after disabling wlan & plugging phone: Which exact version of NetworkManager are you using? It looks like NetworkManager cannot properly initialize the phone to be able to check for a PIN. This could be due to the older version of NM that Ubuntu ships, we've done some work in NetworkManager since that version (including the actual 0.7.0 release) that fixes that issue for many devices (by trying alternate init commands). Trying the latest NM from the PPA might help to isolate that issue. If the latest Ubuntu bits fail, then open a Terminal, become root, stop the NetworkManager service, and execute the following command: NM_SERIAL_DEBUG=1 NetworkManager --no-daemon then wait about 10 seconds, and try your 3G connection. Grab the output that NM spits out into the terminal, and paste it into a reply to this message. Thanks! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband and carriers
On Tue, 2009-01-20 at 09:12 +0100, Marc Luethi wrote: > On Mon, 2009-01-19 at 19:47 +0200, Janne Boman wrote: > > > Nothing gets written to that file when I plug in the phone. The applet > > goes trough the set up dialogs, an option to select my carrier appears > > on the list of available networks, but when I select the mobile carrier > > the connection returns to use the wireless network (or whatever I was > > using at that time...). It's kinda weird, the last log entry is dated > > about 7 hours ago, there's nothing on my current session (a power of in > > the middle). > > Try disabling Wireless globally in NM before starting the Mobile > Broadband connection. > > I can't get Mobile Broadband to work either on my Ubuntu 8.10 while any > WiFi or LAN connection remains enabled. It results in a very wierd > setup, where the default route remains on the wlan0 interface (or eth0, > for that matter...). That part is expected, since WiFi is almost always faster than the 3G, NM will prefer the wifi as your primary connection. > ~$ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Iface > 10.6.6.60.0.0.0 255.255.255.255 UH0 ppp0 > 172.20.124.0 0.0.0.0 255.255.255.0 U 2 wlan0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 1000ppp0 > 0.0.0.0 172.20.124.10.0.0.0 UG0 wlan0 > > > Yet, the Mobile ISP's DNS servers take precedence over the WLAN ones: That's not expected, and not something I can duplicate with the 0.7.0 release code. It could be an Ubuntu-specific bug; trying the latest PPA code which is more up-to-date might help to isolate the cause of this. Dan > m...@torch:~$ more /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 138.188.101.186 > nameserver 138.188.101.189 > nameserver 172.20.124.1 > > > > This can't work, really - what if the Mobile ISP assigns DNS addresses > that are not routeable via the WLAN network? > > > regards > > Marc > > > ___ > 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: Mobile broadband and carriers
On Tue, 2009-01-20 at 13:26 +0200, Janne Boman wrote: > Jan 20 13:06:22 lauta NetworkManager: check_pin_done(): PIN > checking timed out Which mechanism are you using to "give" the PIN to the device? When editing the connection in NM's GUI (under "Edit Connections" in the "Mobile Broadband" tab), did you enter the PIN in the field? Using it with NM's functionality instead of the KPP & scripts might make it work in the end. regards Marc ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband and carriers
Marc Luethi wrote: > > Try disabling Wireless globally in NM before starting the Mobile > Broadband connection. > > I can't get Mobile Broadband to work either on my Ubuntu 8.10 while any > WiFi or LAN connection remains enabled. It results in a very wierd > setup, where the default route remains on the wlan0 interface (or eth0, > for that matter...). > > ~$ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Iface > 10.6.6.60.0.0.0 255.255.255.255 UH0 ppp0 > 172.20.124.0 0.0.0.0 255.255.255.0 U 2 wlan0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 1000ppp0 > 0.0.0.0 172.20.124.10.0.0.0 UG0 wlan0 > > > Yet, the Mobile ISP's DNS servers take precedence over the WLAN ones: > > m...@torch:~$ more /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 138.188.101.186 > nameserver 138.188.101.189 > nameserver 172.20.124.1 > > > > This can't work, really - what if the Mobile ISP assigns DNS addresses > that are not routeable via the WLAN network? > > > regards > > Marc > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > Now I've got something, here is the relevant part from /var/log/daemon.log after disabling wlan & plugging phone: Jan 20 13:06:12 lauta nm-system-settings:SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_4e8_6601_noserial_if0_serial_unknown_0, iface: (null)): iface not found Jan 20 13:06:12 lauta NetworkManager: ttyACM0: driver is 'cdc_acm'. Jan 20 13:06:12 lauta NetworkManager: [1232449572.302092] setup_monitor_device(): No monitoring udi provided Jan 20 13:06:12 lauta NetworkManager: Found new Modem device 'ttyACM0'. Jan 20 13:06:12 lauta NetworkManager: (ttyACM0): exported as /org/freedesktop/Hal/devices/usb_device_4e8_6601_noserial_if0_serial_unknown_0 Jan 20 13:06:16 lauta NetworkManager: (ttyACM0): device state change: 1 -> 2 Jan 20 13:06:16 lauta NetworkManager: (ttyACM0): deactivating device (reason: 2). Jan 20 13:06:16 lauta NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed Jan 20 13:06:16 lauta NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed Jan 20 13:06:16 lauta NetworkManager: (ttyACM0): device state change: 2 -> 3 Jan 20 13:06:19 lauta NetworkManager: Activation (ttyACM0) starting connection 'Elisa' Jan 20 13:06:19 lauta NetworkManager: (ttyACM0): device state change: 3 -> 4 Jan 20 13:06:19 lauta NetworkManager: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... Jan 20 13:06:19 lauta NetworkManager: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... Jan 20 13:06:19 lauta NetworkManager: [1232449579.038966] nm_serial_device_open(): (ttyACM0) opening device... Jan 20 13:06:19 lauta NetworkManager: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. Jan 20 13:06:22 lauta NetworkManager: check_pin_done(): PIN checking timed out Jan 20 13:06:22 lauta NetworkManager: (ttyACM0): device state change: 4 -> 9 Jan 20 13:06:22 lauta NetworkManager: [1232449582.196186] nm_serial_device_close(): Closing device 'ttyACM0' Jan 20 13:06:22 lauta NetworkManager: Marking connection 'Elisa' invalid. Jan 20 13:06:22 lauta NetworkManager: Activation (ttyACM0) failed. Jan 20 13:06:22 lauta NetworkManager: (ttyACM0): device state change: 9 -> 3 Jan 20 13:06:22 lauta NetworkManager: (ttyACM0): deactivating device (reason: 0). Jan 20 13:06:22 lauta NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed Jan 20 13:06:22 lauta NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband and carriers
On Mon, 2009-01-19 at 19:47 +0200, Janne Boman wrote: > Nothing gets written to that file when I plug in the phone. The applet > goes trough the set up dialogs, an option to select my carrier appears > on the list of available networks, but when I select the mobile carrier > the connection returns to use the wireless network (or whatever I was > using at that time...). It's kinda weird, the last log entry is dated > about 7 hours ago, there's nothing on my current session (a power of in > the middle). Try disabling Wireless globally in NM before starting the Mobile Broadband connection. I can't get Mobile Broadband to work either on my Ubuntu 8.10 while any WiFi or LAN connection remains enabled. It results in a very wierd setup, where the default route remains on the wlan0 interface (or eth0, for that matter...). ~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Iface 10.6.6.60.0.0.0 255.255.255.255 UH0 ppp0 172.20.124.00.0.0.0 255.255.255.0 U 2 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000ppp0 0.0.0.0 172.20.124.10.0.0.0 UG0 wlan0 Yet, the Mobile ISP's DNS servers take precedence over the WLAN ones: m...@torch:~$ more /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 138.188.101.186 nameserver 138.188.101.189 nameserver 172.20.124.1 This can't work, really - what if the Mobile ISP assigns DNS addresses that are not routeable via the WLAN network? regards Marc ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband and carriers
Dan Williams wrote: > Can you grab some logs from /var/log/daemon.log and report what they > say? Depends on where the connection is actually failing. Then we can > try to run NM manually with some serial debugging information and see > what specific bits the phone doesn't like. > > Dan > > Nothing gets written to that file when I plug in the phone. The applet goes trough the set up dialogs, an option to select my carrier appears on the list of available networks, but when I select the mobile carrier the connection returns to use the wireless network (or whatever I was using at that time...). It's kinda weird, the last log entry is dated about 7 hours ago, there's nothing on my current session (a power of in the middle). Janne ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile broadband and carriers
On Sun, 2009-01-18 at 17:01 +0200, Janne Boman wrote: > Hello, > > I noticed that Ubuntu 8.10 with NetworkManager Applet 0.7.0 correctly > suggests the "mobile broadband" option when I plug in my gprs phone. > However, the connection fails. I can use my phone's gprs connection with > ppp and scripts from http://wiki.ubuntu-fi.org/Matkapuhelin_modeemina > (Finnish Ubuntu documentation). The page is in Finnish, but the relevant > part is that those scrips work. The attachment "elisa" is from > /etc/ppp/peers/ and the connect/disconnect scripts are from /etc/ppp/. > Can these be incorporated in network manager? I'm willing to do some > testing (not an expert, though...). Can you grab some logs from /var/log/daemon.log and report what they say? Depends on where the connection is actually failing. Then we can try to run NM manually with some serial debugging information and see what specific bits the phone doesn't like. Dan > Best Regards, Janne > > > plain text document attachment (elisa) > # Most GPRS phones don't reply to LCP echo's > lcp-echo-failure 0 > lcp-echo-interval 0 > > # Keep pppd attached to the terminal: > # Comment this to get daemon mode pppd > nodetach > > # Debug info from pppd: > # Comment this off, if you don't need more info > debug > > # Show password in debug messages > show-password > > # Connect script: > # scripts to initialize the GPRS modem and start the connection, > connect /etc/ppp/elisa-connect-chat > > # Disconnect script: > # AT commands used to 'hangup' the GPRS connection. > disconnect /etc/ppp/elisa-disconnect-chat > > # Serial device to which the GPRS phone is connected: > #/dev/ttyUSB0# USB > /dev/ttyACM0# Data cable device file > #/dev/rfcomm0# Bluetooth device file > > # Serial port line speed > 115200 # fast enough > #57600 > > # Hardware flow control: > # Use hardware flow control with cable, Bluetooth and USB but not with IrDA. > crtscts # serial cable, Bluetooth and USB, on some occations with IrDA too > #nocrtscts # IrDA > > # Ignore carrier detect signal from the modem: > local > > # IP addresses: > # - accept peers idea of our local address and set address peer as 10.0.0.1 > # (any address would do, since IPCP gives 0.0.0.0 to it) > # - if you use the 10. network at home or something and pppd rejects it, > # change the address to something else > 0.0.0.0:0.0.0.0 > > # pppd must not propose any IP address to the peer! > noipdefault > > # Accept peers idea of our local address > ipcp-accept-local > > # Add the ppp interface as default route to the IP routing table > defaultroute > > # DNS servers from the phone: > # some phones support this, some don't. > usepeerdns > # ppp compression: > # ppp compression may be used between the phone and the pppd, but the > # serial connection is usually not the bottleneck in GPRS, so the > # compression is useless (and with some phones need to disabled before > # the LCP negotiations succeed). > novj > nobsdcomp > novjccomp > nopcomp > noaccomp > noccp > > # The phone is not required to authenticate: > noauth > > # Username and password: > # If username and password are required by the APN, put here the username > # and put the username-password combination to the secrets file: > # /etc/ppp/pap-secrets for PAP and /etc/ppp/chap-secrets for CHAP > # authentication. See pppd man pages for details. > user "rlnet" > password "internet" > > # > mtu 1500 > mru 1500 > > asyncmap 0xa > > > plain text document attachment (elisa-connect-chat) > #!/bin/sh > exec chat \ > TIMEOUT 5 \ > ECHOON \ > ABORT '\nBUSY\r' \ > ABORT '\nERROR\r' \ > ABORT '\nNO ANSWER\r' \ > ABORT '\nNO CARRIER\r'\ > ABORT '\nNO DIALTONE\r' \ > ABORT '\nRINGING\r\n\r\nRINGING\r'\ > '' AT \ > OK ATH \ > OK ATE1\ > OK 'AT+CGDCONT=1,"IP","internet","0.0.0.0",0,0' \ > OK ATD*99# \ > TIMEOUT 22 \ > CONNECT "" > > > plain text document attachment (elisa-disconnect-chat) > #!/bin/sh > exec /usr/sbin/chat -V -s -S \ > ABORT "BUSY" \ > ABORT "ERROR" \ > ABORT "NO DIALTONE" \ > SAY "\nSending break to the modem\n" \ > "" "K" "" "K" "" "K" "" \ > "+++ATH" "" "+++ATH" "" "+++ATH" > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-l
Mobile broadband and carriers
Hello, I noticed that Ubuntu 8.10 with NetworkManager Applet 0.7.0 correctly suggests the "mobile broadband" option when I plug in my gprs phone. However, the connection fails. I can use my phone's gprs connection with ppp and scripts from http://wiki.ubuntu-fi.org/Matkapuhelin_modeemina (Finnish Ubuntu documentation). The page is in Finnish, but the relevant part is that those scrips work. The attachment "elisa" is from /etc/ppp/peers/ and the connect/disconnect scripts are from /etc/ppp/. Can these be incorporated in network manager? I'm willing to do some testing (not an expert, though...). Best Regards, Janne # Most GPRS phones don't reply to LCP echo's lcp-echo-failure 0 lcp-echo-interval 0 # Keep pppd attached to the terminal: # Comment this to get daemon mode pppd nodetach # Debug info from pppd: # Comment this off, if you don't need more info debug # Show password in debug messages show-password # Connect script: # scripts to initialize the GPRS modem and start the connection, connect /etc/ppp/elisa-connect-chat # Disconnect script: # AT commands used to 'hangup' the GPRS connection. disconnect /etc/ppp/elisa-disconnect-chat # Serial device to which the GPRS phone is connected: #/dev/ttyUSB0# USB /dev/ttyACM0# Data cable device file #/dev/rfcomm0# Bluetooth device file # Serial port line speed 115200 # fast enough #57600 # Hardware flow control: # Use hardware flow control with cable, Bluetooth and USB but not with IrDA. crtscts # serial cable, Bluetooth and USB, on some occations with IrDA too #nocrtscts # IrDA # Ignore carrier detect signal from the modem: local # IP addresses: # - accept peers idea of our local address and set address peer as 10.0.0.1 # (any address would do, since IPCP gives 0.0.0.0 to it) # - if you use the 10. network at home or something and pppd rejects it, # change the address to something else 0.0.0.0:0.0.0.0 # pppd must not propose any IP address to the peer! noipdefault # Accept peers idea of our local address ipcp-accept-local # Add the ppp interface as default route to the IP routing table defaultroute # DNS servers from the phone: # some phones support this, some don't. usepeerdns # ppp compression: # ppp compression may be used between the phone and the pppd, but the # serial connection is usually not the bottleneck in GPRS, so the # compression is useless (and with some phones need to disabled before # the LCP negotiations succeed). novj nobsdcomp novjccomp nopcomp noaccomp noccp # The phone is not required to authenticate: noauth # Username and password: # If username and password are required by the APN, put here the username # and put the username-password combination to the secrets file: # /etc/ppp/pap-secrets for PAP and /etc/ppp/chap-secrets for CHAP # authentication. See pppd man pages for details. user "rlnet" password "internet" # mtu 1500 mru 1500 asyncmap 0xa #!/bin/sh exec chat \ TIMEOUT 5 \ ECHOON \ ABORT '\nBUSY\r' \ ABORT '\nERROR\r' \ ABORT '\nNO ANSWER\r' \ ABORT '\nNO CARRIER\r'\ ABORT '\nNO DIALTONE\r' \ ABORT '\nRINGING\r\n\r\nRINGING\r'\ '' AT \ OK ATH \ OK ATE1\ OK 'AT+CGDCONT=1,"IP","internet","0.0.0.0",0,0' \ OK ATD*99# \ TIMEOUT 22 \ CONNECT "" #!/bin/sh exec /usr/sbin/chat -V -s -S \ ABORT "BUSY" \ ABORT "ERROR" \ ABORT "NO DIALTONE" \ SAY "\nSending break to the modem\n" \ "" "K" "" "K" "" "K" "" \ "+++ATH" "" "+++ATH" "" "+++ATH" ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
