network manager ppp timeout

This is how it works on my main machine (not flawless because disconnect does not work):
---------------------
Jun 28 12:20:55 wb kernel: [13850.192111] usb 2-3: new high speed USB device using ehci_hcd and address 6
Jun 28 12:20:55 wb kernel: [13850.336128] usb 2-3: configuration #1 chosen from 1 choice
Jun 28 12:20:55 wb kernel: [13850.338593] usb-storage: probe of 2-3:1.0 failed with error -5
Jun 28 12:20:55 wb kernel: [13850.338969] usb-storage: probe of 2-3:1.1 failed with error -5
Jun 28 12:20:55 wb kernel: [13850.340580] usb-storage: probe of 2-3:1.2 failed with error -1
Jun 28 12:20:55 wb kernel: [13850.342759] usb-storage: probe of 2-3:1.3 failed with error -1
Jun 28 12:20:55 wb kernel: [13850.662531] usbcore: registered new interface driver usbserial
Jun 28 12:20:55 wb kernel: [13850.662559] USB Serial support registered for generic
Jun 28 12:20:55 wb kernel: [13850.662678] usbcore: registered new interface driver usbserial_generic
Jun 28 12:20:55 wb kernel: [13850.662683] usbserial: USB Serial Driver core
Jun 28 12:20:55 wb kernel: [13850.675874] USB Serial support registered for GSM modem (1-port)
Jun 28 12:20:55 wb kernel: [13850.675977] option 2-3:1.0: GSM modem (1-port) converter detected
Jun 28 12:20:55 wb kernel: [13850.676873] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0
Jun 28 12:20:55 wb kernel: [13850.676897] option 2-3:1.1: GSM modem (1-port) converter detected
Jun 28 12:20:55 wb kernel: [13850.676990] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB1
Jun 28 12:20:55 wb kernel: [13850.677042] usbcore: registered new interface driver option
Jun 28 12:20:55 wb kernel: [13850.677046] option: v0.7.2:USB Driver for GSM modems
Jun 28 12:20:56 wb NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Jun 28 12:20:56 wb nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0, iface: (null)): iface not found
Jun 28 12:20:56 wb NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:GSM)
Jun 28 12:20:56 wb NetworkManager: <info> (ttyUSB0): new Modem device (driver: 'option')
Jun 28 12:20:56 wb NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0
Jun 28 12:21:01 wb NetworkManager: <info> (ttyUSB0): device state change: 1 -> 2
Jun 28 12:21:01 wb NetworkManager: <info> (ttyUSB0): deactivating device (reason: 2).
Jun 28 12:21:01 wb NetworkManager: <info> Policy set 'rsb' (wlan0) as default for routing and DNS.
Jun 28 12:21:01 wb NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Jun 28 12:21:01 wb NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Jun 28 12:21:01 wb NetworkManager: <info> (ttyUSB0): device state change: 2 -> 3
Jun 28 12:21:01 wb NetworkManager: <info> Activation (ttyUSB0) starting connection 'Yesss'
Jun 28 12:21:01 wb NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
Jun 28 12:21:01 wb NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jun ...

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in network-manager.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please open a terminal and execute: apport-collect 393094 ? It will attach the necessary information to this report. Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

with the network manager form

http://ppa.launchpad.net/network-manager/trunk/ubuntu karmic main

works fine

the alternative to conect is configure the conection with pppoeconf

Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
IfupdownConfig: Error: [Errno 13] Permission denied: '/etc/network/interfaces'
IpRoute:
 200.63.148.91 dev ppp0 proto kernel scope link src 201.254.74.85
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default dev ppp0 scope link
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=es_AR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
RfKill:

Uname: Linux 2.6.31-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
WpaSupplicantLog:

with ubuntu 9.04 works fine also

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

Is this still an issue for anyone in 12.04/14.04 or newer?

I just read the syslog excerpt above.

I recently had a similar issue in 15.10 and want to share my experience:

The symptoms: Timeouts and connection termination after some minutes. I used openconnect vpn connector.

After several experiments I figured the source of the problem being that my home network is a class A network (10.x.x.x) and the destination network is a class A network (10.x.x.x) as well.

Keep alive packets follow the routing table and in my case, this included the default route pointing to my router.
The router tunnels the vpn connection but does not route it which means that keep alives will not reach the remote endpoint and the connection runs into timeouts.

I found no solution to this issue other than using an alternative network connection (using mobile modem which issues a different home IP address 172.16.x.x). Now the connection is stable and keep alives are forwarded correctly.

Note: Even static routes do not help as the endpoint of the vpn tunnel has rolling IP addresses.

Why do I believe there is a connection?

see:
Jun 28 11:30:06 xb pppd[3306]: Cannot determine ethernet address for proxy ARP
Jun 28 11:30:06 xb pppd[3306]: local IP address 10.113.214.1 <========================
Jun 28 11:30:06 xb pppd[3306]: remote IP address 10.64.64.64 <========================

I hope this helps

Thanks for sharing! If that is the underlying issue, I'm not sure there is anything we can do to fix it in Ubuntu...

I could verify this situation with a Windows client. I doubt there is anything that can be done. If two networks share the same IP range with two different default gateways and different dns name spaces, not even static routes can solve this.

Thanks for your efforts though.

@war-rsb
Thanks for your analysis! I'm going to go ahead and close the case since there is no way to fix this.