Just further info.<br clear="all"><br>syslog info from the time of the disconnects. <br><br>May 23 14:20:45 ANDO-GTWY pppd[3146]: LCP terminated by peer<br>May 23 14:20:45 ANDO-GTWY pppd[3146]: Connect time 225.7 minutes.<br>
May 23 14:20:45 ANDO-GTWY pppd[3146]: Sent 12774257 bytes, received 143418836 bytes.<br>May 23 14:20:45 ANDO-GTWY NetworkManager: <info> (ttyUSB0): device state change: 8 -> 7<br>May 23 14:20:45 ANDO-GTWY pppd[3146]: Modem hangup<br>
May 23 14:20:45 ANDO-GTWY pppd[3146]: Connection terminated.<br>May 23 14:20:45 ANDO-GTWY NetworkManager: <info> (ttyUSB0): device state change: 7 -> 9<br>May 23 14:20:46 ANDO-GTWY NetworkManager: <WARN> monitor_cb(): Could not read ppp stats: No such device<br>
May 23 14:20:46 ANDO-GTWY pppd[3146]: Terminating on signal 15<br>May 23 14:20:46 ANDO-GTWY pppd[3146]: Exit.<br>May 23 14:20:46 ANDO-GTWY NetworkManager: <debug> [1243102846.080345] nm_serial_device_close(): Closing device 'ttyUSB0'<br>
May 23 14:20:46 ANDO-GTWY NetworkManager: <info> Marking connection 'Alltel EVDO' invalid.<br>May 23 14:20:46 ANDO-GTWY NetworkManager: <info> Activation (ttyUSB0) failed.<br>May 23 14:20:46 ANDO-GTWY NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3<br>
May 23 14:20:46 ANDO-GTWY NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).<br>May 23 14:20:46 ANDO-GTWY NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed<br>
May 23 14:20:46 ANDO-GTWY NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed<br>May 23 14:20:47 ANDO-GTWY nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.<br>
May 23 14:20:48 ANDO-GTWY NetworkManager: <debug> [1243102848.005926] ensure_killed(): waiting for ppp pid 3146 to exit<br>May 23 14:20:48 ANDO-GTWY NetworkManager: <debug> [1243102848.006176] ensure_killed(): ppp pid 3146 cleaned up<br>
May 23 14:21:56 ANDO-GTWY console-kit-daemon[2632]: WARNING: Unable to activate console: No such device or address<br><br><br><br>And the contents of /etc/ppp/options<br><br># /etc/ppp/options<br># <br># Originally created by Jim Knoble <<a href="mailto:jmknoble@mercury.interpath.net">jmknoble@mercury.interpath.net</a>><br>
# Modified for Debian by alvar Bray <<a href="mailto:alvar@meiko.co.uk">alvar@meiko.co.uk</a>><br># Modified for PPP Server setup by Christoph Lameter <<a href="mailto:clameter@debian.org">clameter@debian.org</a>><br>
#<br># To quickly see what options are active in this file, use this command:<br># egrep -v '#|^ *$' /etc/ppp/options<br><br># Specify which DNS Servers the incoming Win95 or WinNT Connection should use<br># Two Servers can be remotely configured<br>
# ms-dns 192.168.1.1<br># ms-dns 192.168.1.2<br><br># Specify which WINS Servers the incoming connection Win95 or WinNT should use<br># ms-wins 192.168.1.50<br># ms-wins 192.168.1.51<br><br># Run the executable or shell command specified after pppd has<br>
# terminated the link. This script could, for example, issue commands<br># to the modem to cause it to hang up if hardware modem control signals<br># were not available.<br>#disconnect "chat -- \d+++\d\c OK ath0 OK"<br>
<br># async character map -- 32-bit hex; each bit is a character<br># that needs to be escaped for pppd to receive it. 0x00000001<br># represents '\x01', and 0x80000000 represents '\x1f'.<br>asyncmap 0<br>
<br># Require the peer to authenticate itself before allowing network<br># packets to be sent or received.<br># Please do not disable this setting. It is expected to be standard in<br># future releases of pppd. Use the call option (see manpage) to disable<br>
# authentication for specific peers.<br>#auth<br>noauth<br># ... Unfortunately, fixing this properly in the peers file<br># (/etc/ppp/peers/ppp0, typically) is apparently incompatible with the<br># paradigm used by gnome-system-tools and system-tools-backend for<br>
# managing the peers files. So in Ubuntu Feisty we change the default.<br><br># Use hardware flow control (i.e. RTS/CTS) to control the flow of data<br># on the serial port.<br>#crtscts<br><br># Use software flow control (i.e. XON/XOFF) to control the flow of data<br>
# on the serial port.<br>#xonxoff<br><br># Specifies that certain characters should be escaped on transmission<br># (regardless of whether the peer requests them to be escaped with its<br># async control character map). The characters to be escaped are<br>
# specified as a list of hex numbers separated by commas. Note that<br># almost any character can be specified for the escape option, unlike<br># the asyncmap option which only allows control characters to be<br># specified. The characters which may not be escaped are those with hex<br>
# values 0x20 - 0x3f or 0x5e.<br>#escape 11,13,ff<br><br># Don't use the modem control lines.<br>#local<br><br># Specifies that pppd should use a UUCP-style lock on the serial device<br># to ensure exclusive access to the device.<br>
lock<br><br># Don't show the passwords when logging the contents of PAP packets.<br># This is the default.<br>hide-password<br><br># When logging the contents of PAP packets, this option causes pppd to<br># show the password string in the log message.<br>
#show-password<br><br># Use the modem control lines. On Ultrix, this option implies hardware<br># flow control, as for the crtscts option. (This option is not fully<br># implemented.)<br>modem<br><br># Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd<br>
# will ask the peer to send packets of no more than <n> bytes. The<br># minimum MRU value is 128. The default MRU value is 1500. A value of<br># 296 is recommended for slow links (40 bytes for TCP/IP header + 256<br>
# bytes of data).<br>#mru 542<br><br># Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"<br># notation (e.g. 255.255.255.0).<br>#netmask 255.255.255.0<br><br># Disables the default behaviour when no local IP address is specified,<br>
# which is to determine (if possible) the local IP address from the<br># hostname. With this option, the peer will have to supply the local IP<br># address during IPCP negotiation (unless it specified explicitly on the<br>
# command line or in an options file).<br>#noipdefault<br><br># Enables the "passive" option in the LCP. With this option, pppd will<br># attempt to initiate a connection; if no reply is received from the<br># peer, pppd will then just wait passively for a valid LCP packet from<br>
# the peer (instead of exiting, as it does without this option).<br>#passive<br><br># With this option, pppd will not transmit LCP packets to initiate a<br># connection until a valid LCP packet is received from the peer (as for<br>
# the "passive" option with old versions of pppd).<br>#silent<br><br># Don't request or allow negotiation of any options for LCP and IPCP<br># (use default values).<br>#-all<br><br># Disable Address/Control compression negotiation (use default, i.e.<br>
# address/control field disabled).<br>#-ac<br><br># Disable asyncmap negotiation (use the default asyncmap, i.e. escape<br># all control characters).<br>#-am<br><br># Don't fork to become a background process (otherwise pppd will do so<br>
# if a serial device is specified).<br>#-detach<br><br># Disable IP address negotiation (with this option, the remote IP<br># address must be specified with an option on the command line or in<br># an options file).<br>#-ip<br>
<br># Disable IPCP negotiation and IP communication. This option should<br># only be required if the peer is buggy and gets confused by requests<br># from pppd for IPCP negotiation.<br>#noip<br><br># Disable magic number negotiation. With this option, pppd cannot<br>
# detect a looped-back line.<br>#-mn<br><br># Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.<br># 1500).<br>#-mru<br><br># Disable protocol field compression negotiation (use default, i.e.<br># protocol field compression disabled).<br>
#-pc<br><br># Require the peer to authenticate itself using PAP.<br>#+pap<br><br># Don't agree to authenticate using PAP.<br>#-pap<br><br># Require the peer to authenticate itself using CHAP [Cryptographic<br># Handshake Authentication Protocol] authentication.<br>
#+chap<br><br># Don't agree to authenticate using CHAP.<br>#-chap<br><br># Disable negotiation of Van Jacobson style IP header compression (use<br># default, i.e. no compression).<br>#-vj<br><br># Increase debugging level (same as -d). If this option is given, pppd<br>
# will log the contents of all control packets sent or received in a<br># readable form. The packets are logged through syslog with facility<br># daemon and level debug. This information can be directed to a file by<br># setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If<br>
# pppd is compiled with extra debugging enabled, it will log messages<br># using facility local2 instead of daemon).<br>#debug<br><br># Append the domain name <d> to the local host name for authentication<br># purposes. For example, if gethostname() returns the name porsche,<br>
# but the fully qualified domain name is <a href="http://porsche.Quotron.COM">porsche.Quotron.COM</a>, you would<br># use the domain option to set the domain name to Quotron.COM.<br>#domain <d><br><br># Enable debugging code in the kernel-level PPP driver. The argument n<br>
# is a number which is the sum of the following values: 1 to enable<br># general debug messages, 2 to request that the contents of received<br># packets be printed, and 4 to request that the contents of transmitted<br># packets be printed.<br>
#kdebug n<br><br># Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer<br># requests a smaller value via MRU negotiation, pppd will request that<br># the kernel networking code send data packets of no more than n bytes<br>
# through the PPP network interface.<br>#mtu <n><br><br># Set the name of the local system for authentication purposes to <n>.<br># This is a privileged option. With this option, pppd will use lines in the<br>
# secrets files which have <n> as the second field when looking for a<br># secret to use in authenticating the peer. In addition, unless overridden<br># with the user option, <n> will be used as the name to send to the peer<br>
# when authenticating the local system to the peer. (Note that pppd does<br># not append the domain name to <n>.)<br>#name <n><br><br># Enforce the use of the hostname as the name of the local system for<br># authentication purposes (overrides the name option).<br>
#usehostname<br><br># Set the assumed name of the remote system for authentication purposes<br># to <n>.<br>#remotename <n><br><br># Add an entry to this system's ARP [Address Resolution Protocol]<br># table with the IP address of the peer and the Ethernet address of this<br>
# system.<br>proxyarp<br><br># Use the system password database for authenticating the peer using<br># PAP. Note: mgetty already provides this option. If this is specified<br># then dialin from users using a script under Linux to fire up ppp wont work.<br>
# login<br><br># If this option is given, pppd will send an LCP echo-request frame to the<br># peer every n seconds. Normally the peer should respond to the echo-request<br># by sending an echo-reply. This option can be used with the<br>
# lcp-echo-failure option to detect that the peer is no longer connected.<br>#lcp-echo-interval 0<br><br># If this option is given, pppd will presume the peer to be dead if n<br># LCP echo-requests are sent without receiving a valid LCP echo-reply.<br>
# If this happens, pppd will terminate the connection. Use of this<br># option requires a non-zero value for the lcp-echo-interval parameter.<br># This option can be used to enable pppd to terminate after the physical<br>
# connection has been broken (e.g., the modem has hung up) in<br># situations where no hardware modem control lines are available.<br>#lcp-echo-failure 0<br><br># Set the LCP restart interval (retransmission timeout) to <n> seconds<br>
# (default 3).<br>#lcp-restart <n><br><br># Set the maximum number of LCP terminate-request transmissions to <n><br># (default 3).<br>#lcp-max-terminate <n><br><br># Set the maximum number of LCP configure-request transmissions to <n><br>
# (default 10).<br>#lcp-max-configure <n><br><br># Set the maximum number of LCP configure-NAKs returned before starting<br># to send configure-Rejects instead to <n> (default 10).<br>#lcp-max-failure <n><br>
<br># Set the IPCP restart interval (retransmission timeout) to <n><br># seconds (default 3).<br>#ipcp-restart <n><br><br># Set the maximum number of IPCP terminate-request transmissions to <n><br># (default 3).<br>
#ipcp-max-terminate <n><br><br># Set the maximum number of IPCP configure-request transmissions to <n><br># (default 10).<br>#ipcp-max-configure <n><br><br># Set the maximum number of IPCP configure-NAKs returned before starting<br>
# to send configure-Rejects instead to <n> (default 10).<br>#ipcp-max-failure <n><br><br># Set the PAP restart interval (retransmission timeout) to <n> seconds<br># (default 3).<br>#pap-restart <n><br>
<br># Set the maximum number of PAP authenticate-request transmissions to<br># <n> (default 10).<br>#pap-max-authreq <n><br><br># Set the maximum time that pppd will wait for the peer to authenticate<br># itself with PAP to <n> seconds (0 means no limit).<br>
#pap-timeout <n><br><br># Set the CHAP restart interval (retransmission timeout for<br># challenges) to <n> seconds (default 3).<br>#chap-restart <n><br><br># Set the maximum number of CHAP challenge transmissions to <n><br>
# (default 10).<br>#chap-max-challenge<br><br># If this option is given, pppd will rechallenge the peer every <n><br># seconds.<br>#chap-interval <n><br><br># With this option, pppd will accept the peer's idea of our local IP<br>
# address, even if the local IP address was specified in an option.<br>#ipcp-accept-local<br><br># With this option, pppd will accept the peer's idea of its (remote) IP<br># address, even if the remote IP address was specified in an option.<br>
#ipcp-accept-remote<br><br># Disable the IPXCP and IPX protocols.<br># To let pppd pass IPX packets comment this out --- you'll probably also<br># want to install ipxripd, and have the Internal IPX Network option enabled<br>
# in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.<br>noipx<br><br># Exit once a connection has been made and terminated. This is the default,<br># unless the `persist' or `demand' option has been specified.<br>
#nopersist<br><br># Do not exit after a connection is terminated; instead try to reopen<br># the connection.<br>#persist<br><br># Terminate after n consecutive failed connection attempts.<br># A value of 0 means no limit. The default value is 10.<br>
#maxfail <n><br><br># Initiate the link only on demand, i.e. when data traffic is present. <br># With this option, the remote IP address must be specified by the user on<br># the command line or in an options file. Pppd will initially configure<br>
# the interface and enable it for IP traffic without connecting to the peer. <br># When traffic is available, pppd will connect to the peer and perform<br># negotiation, authentication, etc. When this is completed, pppd will<br>
# commence passing data packets (i.e., IP packets) across the link.<br>#demand<br><br># Specifies that pppd should disconnect if the link is idle for <n> seconds.<br># The link is idle when no data packets (i.e. IP packets) are being sent or<br>
# received. Note: it is not advisable to use this option with the persist<br># option without the demand option. If the active-filter option is given,<br># data packets which are rejected by the specified activity filter also<br>
# count as the link being idle.<br>#idle <n><br><br># Specifies how many seconds to wait before re-initiating the link after<br># it terminates. This option only has any effect if the persist or demand<br># option is used. The holdoff period is not applied if the link was<br>
# terminated because it was idle.<br>#holdoff <n><br><br># Wait for up n milliseconds after the connect script finishes for a valid<br># PPP packet from the peer. At the end of this time, or when a valid PPP<br># packet is received from the peer, pppd will commence negotiation by<br>
# sending its first LCP packet. The default value is 1000 (1 second).<br># This wait period only applies if the connect or pty option is used.<br>#connect-delay <n><br><br># Packet filtering: for more information, see pppd(8)<br>
# Any packets matching the filter expression will be interpreted as link<br># activity, and will cause a "demand" connection to be activated, and reset<br># the idle connection timer. (idle option)<br># The filter expression is akin to that of tcpdump(1)<br>
#active-filter <filter-expression><br><br># ---<End of File>---<br><br>