LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 01-31-2008, 02:59 PM   #1
pbhj
Member
 
Registered: Dec 2002
Location: UK
Distribution: Slackware 12; Ubuntu 7.10
Posts: 358

Rep: Reputation: 31
Unhappy flaky adsl, can you explain this /var/log/messages output?


My ADSL usually works fine but sometimes I get a whole day when all I get are entries in the logs like the following. Pings return typically a 60% failure rate over the period of such logs and a web page rarely returns the whole page before it hangs.

Basically it leaves the 'net connection near unusable. This connection is made via a USB Speedtouch 330 ADSL modem.

Code:
user@bridgeflap:/usr/share/inkscape/palettes$ tail -f /var/log/messages
Jan 31 20:37:32 bridgeflap kernel: [ 7420.870605] ATM dev 0: ADSL line is down
Jan 31 20:37:35 bridgeflap kernel: [ 7422.295012] ATM dev 0: ADSL line is synchronising
Jan 31 20:37:45 bridgeflap kernel: [ 7427.052567] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:38:01 bridgeflap kernel: [ 7435.625181] ATM dev 0: DSL line goes down
Jan 31 20:38:01 bridgeflap kernel: [ 7435.631839] ATM dev 0: ADSL line is down
Jan 31 20:38:05 bridgeflap kernel: [ 7437.688031] ATM dev 0: ADSL line is synchronising
Jan 31 20:38:15 bridgeflap kernel: [ 7442.445532] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:38:29 bridgeflap kernel: [ 7449.052748] ATM dev 0: DSL line goes down
Jan 31 20:38:29 bridgeflap kernel: [ 7449.059407] ATM dev 0: ADSL line is down
Jan 31 20:38:30 bridgeflap kernel: [ 7449.582733] ATM dev 0: ADSL line is synchronising
Jan 31 20:38:45 bridgeflap kernel: [ 7456.718986] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:38:58 bridgeflap kernel: [ 7462.708686] ATM dev 0: DSL line goes down
Jan 31 20:38:58 bridgeflap kernel: [ 7462.715345] ATM dev 0: ADSL line is down
Jan 31 20:39:00 bridgeflap kernel: [ 7463.853819] ATM dev 0: ADSL line is synchronising
Jan 31 20:39:10 bridgeflap kernel: [ 7468.611320] ATM dev 0: ADSL line is up (1120 kb/s down | 288 kb/s up)
Jan 31 20:39:27 bridgeflap kernel: [ 7476.349400] ATM dev 0: DSL line goes down
Jan 31 20:39:27 bridgeflap kernel: [ 7476.356060] ATM dev 0: ADSL line is down
Jan 31 20:39:30 bridgeflap kernel: [ 7478.126326] ATM dev 0: ADSL line is synchronising
Jan 31 20:39:40 bridgeflap kernel: [ 7482.884782] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:39:55 bridgeflap kernel: [ 7490.005316] ATM dev 0: DSL line goes down
Jan 31 20:39:55 bridgeflap kernel: [ 7490.011978] ATM dev 0: ADSL line is down
Jan 31 20:39:55 bridgeflap kernel: [ 7490.027201] ATM dev 0: ADSL line is blocked?
Jan 31 20:40:00 bridgeflap kernel: [ 7492.398810] ATM dev 0: ADSL line is synchronising
Jan 31 20:40:10 bridgeflap kernel: [ 7497.155821] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:40:23 bridgeflap kernel: [ 7503.356757] ATM dev 0: DSL line goes down
Jan 31 20:40:24 bridgeflap kernel: [ 7503.363418] ATM dev 0: ADSL line is down
Jan 31 20:40:25 bridgeflap kernel: [ 7504.620323] ATM dev 0: ADSL line is synchronising
Jan 31 20:40:40 bridgeflap kernel: [ 7513.116329] ATM dev 0: ADSL line is up (1056 kb/s down | 288 kb/s up)
Jan 31 20:40:52 bridgeflap kernel: [ 7520.418184] ATM dev 0: DSL line goes down
Jan 31 20:40:52 bridgeflap kernel: [ 7520.432167] ATM dev 0: ADSL line is down
Jan 31 20:40:55 bridgeflap kernel: [ 7523.222187] ATM dev 0: ADSL line is synchronising
Jan 31 20:41:05 bridgeflap kernel: [ 7527.979707] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:41:28 bridgeflap kernel: [ 7539.277790] ATM dev 0: DSL line goes down
Jan 31 20:41:28 bridgeflap kernel: [ 7539.284449] ATM dev 0: ADSL line is down
Jan 31 20:41:30 bridgeflap kernel: [ 7540.522838] ATM dev 0: ADSL line is synchronising
Jan 31 20:41:40 bridgeflap kernel: [ 7545.280341] ATM dev 0: ADSL line is up (1120 kb/s down | 288 kb/s up)
Jan 31 20:41:50 bridgeflap pppd[7568]: No response to 4 echo-requests
Jan 31 20:41:50 bridgeflap pppd[7568]: Serial link appears to be disconnected.
Jan 31 20:41:50 bridgeflap pppd[7568]: Connect time 20.0 minutes.
Jan 31 20:41:50 bridgeflap pppd[7568]: Sent 34214 bytes, received 45855 bytes.
Jan 31 20:41:56 bridgeflap pppd[7568]: Connection terminated.
Jan 31 20:41:56 bridgeflap pppd[7568]: Modem hangup
Jan 31 20:42:06 bridgeflap kernel: [ 7557.242132] ATM dev 0: DSL line goes down
Jan 31 20:42:06 bridgeflap kernel: [ 7557.248791] ATM dev 0: ADSL line is down
Jan 31 20:42:10 bridgeflap kernel: [ 7559.552848] ATM dev 0: ADSL line is synchronising
Jan 31 20:42:20 bridgeflap kernel: [ 7564.310823] ATM dev 0: ADSL line is up (1120 kb/s down | 288 kb/s up)
Jan 31 20:42:26 bridgeflap pppd[7568]: Using interface ppp0
Jan 31 20:42:26 bridgeflap pppd[7568]: Connect: ppp0 <--> 0.38
Jan 31 20:42:26 bridgeflap pppd[7568]: CHAP authentication succeeded: CHAP authentication success, unit 1951
Jan 31 20:42:26 bridgeflap pppd[7568]: CHAP authentication succeeded
Jan 31 20:42:27 bridgeflap pppd[7568]: local  IP address 91.1XX.145.125
Jan 31 20:42:27 bridgeflap pppd[7568]: remote IP address 91.1XX.128.1
Jan 31 20:42:27 bridgeflap pppd[7568]: primary   DNS address 1XX.36.79.100
Jan 31 20:42:27 bridgeflap pppd[7568]: secondary DNS address 1XX.36.79.101
Jan 31 20:42:34 bridgeflap kernel: [ 7570.684931] ATM dev 0: DSL line goes down
Jan 31 20:42:34 bridgeflap kernel: [ 7570.691589] ATM dev 0: ADSL line is down
Jan 31 20:42:35 bridgeflap kernel: [ 7571.446607] ATM dev 0: ADSL line is synchronising
Jan 31 20:42:50 bridgeflap kernel: [ 7578.868667] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:43:05 bridgeflap kernel: [ 7587.053632] ATM dev 0: DSL line goes down
Jan 31 20:43:05 bridgeflap kernel: [ 7587.060291] ATM dev 0: ADSL line is down
Jan 31 20:43:05 bridgeflap kernel: [ 7587.487517] ATM dev 0: ADSL line is synchronising
Jan 31 20:43:20 bridgeflap kernel: [ 7595.276607] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:43:33 bridgeflap kernel: [ 7601.344346] ATM dev 0: DSL line goes down
Jan 31 20:43:33 bridgeflap kernel: [ 7601.351011] ATM dev 0: ADSL line is down
Jan 31 20:43:35 bridgeflap kernel: [ 7602.410026] ATM dev 0: ADSL line is synchronising
Jan 31 20:43:45 bridgeflap kernel: [ 7607.167535] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:44:02 bridgeflap kernel: [ 7614.969847] ATM dev 0: DSL line goes down
Jan 31 20:44:02 bridgeflap kernel: [ 7614.976506] ATM dev 0: ADSL line is down
Jan 31 20:44:05 bridgeflap kernel: [ 7616.683030] ATM dev 0: ADSL line is synchronising
Jan 31 20:44:15 bridgeflap kernel: [ 7621.439590] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:44:31 bridgeflap kernel: [ 7629.243240] ATM dev 0: DSL line goes down
Jan 31 20:44:31 bridgeflap kernel: [ 7629.249902] ATM dev 0: ADSL line is down
Jan 31 20:44:35 bridgeflap kernel: [ 7631.602500] ATM dev 0: ADSL line is synchronising
Jan 31 20:44:45 bridgeflap kernel: [ 7636.360497] ATM dev 0: ADSL line is up (1088 kb/s down | 288 kb/s up)
Jan 31 20:44:59 bridgeflap kernel: [ 7642.868767] ATM dev 0: DSL line goes down
Jan 31 20:44:59 bridgeflap kernel: [ 7642.875426] ATM dev 0: ADSL line is down
Jan 31 20:45:00 bridgeflap kernel: [ 7643.496281] ATM dev 0: ADSL line is synchronising
Jan 31 20:45:15 bridgeflap kernel: [ 7650.633981] ATM dev 0: ADSL line is up (1024 kb/s down | 288 kb/s up)
Jan 31 20:45:33 bridgeflap kernel: [ 7662.372705] ATM dev 0: DSL line goes down
Jan 31 20:45:33 bridgeflap kernel: [ 7662.379364] ATM dev 0: ADSL line is down
Jan 31 20:45:35 bridgeflap kernel: [ 7663.330872] ATM dev 0: ADSL line is synchronising
Jan 31 20:45:50 bridgeflap kernel: [ 7670.467138] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:46:02 bridgeflap kernel: [ 7677.133329] ATM dev 0: DSL line goes down
Jan 31 20:46:02 bridgeflap kernel: [ 7677.139987] ATM dev 0: ADSL line is down
Jan 31 20:46:05 bridgeflap kernel: [ 7678.723294] ATM dev 0: ADSL line is synchronising
Jan 31 20:46:15 bridgeflap kernel: [ 7683.480821] ATM dev 0: ADSL line is up (1024 kb/s down | 288 kb/s up)
Jan 31 20:46:31 bridgeflap kernel: [ 7692.040485] ATM dev 0: DSL line goes down
Jan 31 20:46:31 bridgeflap kernel: [ 7692.047144] ATM dev 0: ADSL line is down
Jan 31 20:46:35 bridgeflap kernel: [ 7694.292692] ATM dev 0: ADSL line is synchronising
Jan 31 20:46:45 bridgeflap kernel: [ 7699.053070] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:46:59 bridgeflap kernel: [ 7705.666007] ATM dev 0: DSL line goes down
Jan 31 20:46:59 bridgeflap kernel: [ 7705.672669] ATM dev 0: ADSL line is down
Jan 31 20:47:00 bridgeflap kernel: [ 7706.190762] ATM dev 0: ADSL line is synchronising
Jan 31 20:47:15 bridgeflap kernel: [ 7713.324203] ATM dev 0: ADSL line is up (1088 kb/s down | 288 kb/s up)
Jan 31 20:47:28 bridgeflap kernel: [ 7719.245859] ATM dev 0: DSL line goes down
Jan 31 20:47:28 bridgeflap kernel: [ 7719.252525] ATM dev 0: ADSL line is down
Jan 31 20:47:30 bridgeflap kernel: [ 7720.460447] ATM dev 0: ADSL line is synchronising
Jan 31 20:47:40 bridgeflap kernel: [ 7725.217950] ATM dev 0: ADSL line is up (1120 kb/s down | 288 kb/s up)
Jan 31 20:47:57 bridgeflap kernel: [ 7732.932282] ATM dev 0: DSL line goes down
Jan 31 20:47:57 bridgeflap kernel: [ 7732.938941] ATM dev 0: ADSL line is down
Jan 31 20:48:00 bridgeflap kernel: [ 7734.733005] ATM dev 0: ADSL line is synchronising
Jan 31 20:48:10 bridgeflap kernel: [ 7739.491530] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:48:25 bridgeflap kernel: [ 7746.994698] ATM dev 0: DSL line goes down
Jan 31 20:48:25 bridgeflap kernel: [ 7747.001356] ATM dev 0: ADSL line is down
Jan 31 20:48:26 bridgeflap kernel: [ 7747.279674] ATM dev 0: ADSL line is synchronising
Jan 31 20:48:26 bridgeflap pppd[7568]: No response to 4 echo-requests
Jan 31 20:48:26 bridgeflap pppd[7568]: Serial link appears to be disconnected.
Jan 31 20:48:26 bridgeflap pppd[7568]: Connect time 6.0 minutes.
Jan 31 20:48:26 bridgeflap pppd[7568]: Sent 49929 bytes, received 73056 bytes.
Jan 31 20:48:32 bridgeflap pppd[7568]: Connection terminated.
Jan 31 20:48:32 bridgeflap pppd[7568]: Modem hangup
Jan 31 20:48:40 bridgeflap kernel: [ 7754.412603] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:48:54 bridgeflap kernel: [ 7760.620198] ATM dev 0: DSL line goes down
Jan 31 20:48:54 bridgeflap kernel: [ 7760.626859] ATM dev 0: ADSL line is down
Jan 31 20:48:55 bridgeflap kernel: [ 7761.548865] ATM dev 0: ADSL line is synchronising
Jan 31 20:49:03 bridgeflap pppd[7568]: Using interface ppp0
Jan 31 20:49:03 bridgeflap pppd[7568]: Connect: ppp0 <--> 0.38
Jan 31 20:49:10 bridgeflap kernel: [ 7768.685154] ATM dev 0: ADSL line is up (1088 kb/s down | 288 kb/s up)
Jan 31 20:49:15 bridgeflap pppd[7568]: CHAP authentication succeeded: CHAP authentication success, unit 3498
Jan 31 20:49:15 bridgeflap pppd[7568]: CHAP authentication succeeded
Jan 31 20:49:15 bridgeflap pppd[7568]: local  IP address 91.1XX.161.102
Jan 31 20:49:15 bridgeflap pppd[7568]: remote IP address 91.1XX.128.1
Jan 31 20:49:15 bridgeflap pppd[7568]: primary   DNS address 1XX.36.79.101
Jan 31 20:49:15 bridgeflap pppd[7568]: secondary DNS address 1XX.36.79.100
Jan 31 20:49:22 bridgeflap kernel: [ 7774.306634] ATM dev 0: DSL line goes down
Jan 31 20:49:22 bridgeflap kernel: [ 7774.313293] ATM dev 0: ADSL line is down
Jan 31 20:49:25 bridgeflap kernel: [ 7775.821427] ATM dev 0: ADSL line is synchronising
Jan 31 20:49:35 bridgeflap kernel: [ 7780.616494] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:49:57 bridgeflap kernel: [ 7793.723537] ATM dev 0: DSL line goes down
Jan 31 20:49:57 bridgeflap kernel: [ 7793.733051] ATM dev 0: ADSL line is down
Jan 31 20:50:00 bridgeflap kernel: [ 7795.538542] ATM dev 0: ADSL line is synchronising
Jan 31 20:50:10 bridgeflap kernel: [ 7800.296593] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Jan 31 20:50:30 bridgeflap kernel: [ 7809.739441] ATM dev 0: DSL line goes down
Jan 31 20:50:30 bridgeflap kernel: [ 7809.746103] ATM dev 0: ADSL line is down
Jan 31 20:50:30 bridgeflap kernel: [ 7809.811280] ATM dev 0: ADSL line is blocked?
Jan 31 20:50:35 bridgeflap kernel: [ 7812.190090] ATM dev 0: ADSL line is synchronising
Jan 31 20:50:46 bridgeflap kernel: [ 7816.947644] ATM dev 0: ADSL line is up (1120 kb/s down | 288 kb/s up)
Jan 31 20:50:59 bridgeflap kernel: [ 7823.349802] ATM dev 0: DSL line goes down
Jan 31 20:50:59 bridgeflap kernel: [ 7823.356464] ATM dev 0: ADSL line is down
Jan 31 20:51:01 bridgeflap kernel: [ 7824.083410] ATM dev 0: ADSL line is synchronising
Jan 31 20:51:16 bridgeflap kernel: [ 7831.219666] ATM dev 0: ADSL line is up (1152 kb/s down | 288 kb/s up)
Please don't say "get a proper ethernet router / different ADSL connection" I don't have the resources to do this currently and it won't help fix the situation.

Supplier is Orange - they say "there's no errors at the moment". I get the same problem on Windows Vista, but wonder if some guru had an idea of what Orange need to do or if some "options" could help.
 
Old 01-31-2008, 03:16 PM   #2
ARC1450
Member
 
Registered: Jun 2005
Location: Odenton, MD
Distribution: Gentoo
Posts: 290

Rep: Reputation: 30
Looks like what's called "flapping".

The circuit jumps up and down either because of misconfiguration of one endpoint or bad equipment at one endpoint. Judging by your download varying on each tear down/negotiation, I'd almost say it's a misconfiguration.

Have you tried calling your tech support exactly when this happens and tried talking to someone other than a script-reading tech? Like Level 2 or Level 3? They can probably tell you why the circuit flaps based on what's supposed to be configured for your particular internet connection and the such.
 
Old 02-01-2008, 07:04 PM   #3
pbhj
Member
 
Registered: Dec 2002
Location: UK
Distribution: Slackware 12; Ubuntu 7.10
Posts: 358

Original Poster
Rep: Reputation: 31
Thanks for the pointer ... unfortunately tech support is 50p per minute and I've had a tech "support" call of 20 mins in the past when I knew the problem and only needed to get a CD sent out. 20 mins = 10.

Any thoughts on what the misconfiguration might be?

Quote:
# /etc/ppp/options
#
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
#
# To quickly see what options are active in this file, use this command:
# egrep -v '#|^ *$' /etc/ppp/options

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
# ms-dns 192.168.1.1
# ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
# ms-wins 192.168.1.50
# ms-wins 192.168.1.51

# Run the executable or shell command specified after pppd has
# terminated the link. This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it. 0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
#auth
noauth
# ... Unfortunately, fixing this properly in the peers file
# (/etc/ppp/peers/ppp0, typically) is apparently incompatible with the
# paradigm used by gnome-system-tools and system-tools-backend for
# managing the peers files. So in Ubuntu Feisty we change the default.

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff

# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map). The characters to be escaped are
# specified as a list of hex numbers separated by commas. Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified. The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff

# Don't use the modem control lines.
#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
hide-password

# When logging the contents of PAP packets, this option causes pppd to
# show the password string in the log message.
#show-password

# Use the modem control lines. On Ultrix, this option implies hardware
# flow control, as for the crtscts option. (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128. The default MRU value is 1500. A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 542

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
#noipdefault

# Enables the "passive" option in the LCP. With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
#passive

# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent

# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all

# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach

# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in
# an options file).
#-ip

# Disable IPCP negotiation and IP communication. This option should
# only be required if the peer is buggy and gets confused by requests
# from pppd for IPCP negotiation.
#noip

# Disable magic number negotiation. With this option, pppd cannot
# detect a looped-back line.
#-mn

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru

# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc

# Require the peer to authenticate itself using PAP.
#+pap

# Don't agree to authenticate using PAP.
#-pap

# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap

# Don't agree to authenticate using CHAP.
#-chap

# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj

# Increase debugging level (same as -d). If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form. The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
#debug

# Append the domain name <d> to the local host name for authentication
# purposes. For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>

# Enable debugging code in the kernel-level PPP driver. The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
#name <n>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont work.
# login

# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection. Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>

# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>

# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>

# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>

# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>

# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>

# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>

# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>

# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
#pap-max-authreq <n>

# Set the maximum time that pppd will wait for the peer to authenticate
# itself with PAP to <n> seconds (0 means no limit).
#pap-timeout <n>

# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>

# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge

# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option enabled
# in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
noipx

# Exit once a connection has been made and terminated. This is the default,
# unless the `persist' or `demand' option has been specified.
#nopersist

# Do not exit after a connection is terminated; instead try to reopen
# the connection.
#persist

# Terminate after n consecutive failed connection attempts.
# A value of 0 means no limit. The default value is 10.
#maxfail <n>

# Initiate the link only on demand, i.e. when data traffic is present.
# With this option, the remote IP address must be specified by the user on
# the command line or in an options file. Pppd will initially configure
# the interface and enable it for IP traffic without connecting to the peer.
# When traffic is available, pppd will connect to the peer and perform
# negotiation, authentication, etc. When this is completed, pppd will
# commence passing data packets (i.e., IP packets) across the link.
#demand

# Specifies that pppd should disconnect if the link is idle for <n> seconds.
# The link is idle when no data packets (i.e. IP packets) are being sent or
# received. Note: it is not advisable to use this option with the persist
# option without the demand option. If the active-filter option is given,
# data packets which are rejected by the specified activity filter also
# count as the link being idle.
#idle <n>

# Specifies how many seconds to wait before re-initiating the link after
# it terminates. This option only has any effect if the persist or demand
# option is used. The holdoff period is not applied if the link was
# terminated because it was idle.
#holdoff <n>

# Wait for up n milliseconds after the connect script finishes for a valid
# PPP packet from the peer. At the end of this time, or when a valid PPP
# packet is received from the peer, pppd will commence negotiation by
# sending its first LCP packet. The default value is 1000 (1 second).
# This wait period only applies if the connect or pty option is used.
#connect-delay <n>

# Packet filtering: for more information, see pppd(8)
# Any packets matching the filter expression will be interpreted as link
# activity, and will cause a "demand" connection to be activated, and reset
# the idle connection timer. (idle option)
# The filter expression is akin to that of tcpdump(1)
#active-filter <filter-expression>

# ---<End of File>---
 
  


Reply

Tags
adsl, ppp0


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Can anyone explain these /var/log/messages ErrorBound Linux - Kernel 6 03-04-2007 11:34 PM
Redirecting the kernel messages to file other than /var/log/messages jyotika_b83 Linux - General 3 04-28-2005 06:39 PM
No output to /var/log/messages or ~syslog eelriver Slackware 5 07-18-2004 05:13 AM
/var/log/messages full of these messages. Should I be concerned? mdavis Linux - Security 5 04-16-2004 10:08 AM
output of printk can NOT be found in /var/log/messages linshu Linux - Software 1 02-13-2004 09:06 AM


All times are GMT -5. The time now is 10:17 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration