[wplug] dialup connectivity problem - disconnects
Zach
netrek at gmail.com
Wed Jan 24 07:34:39 EST 2007
Morning everyone,
I am having a very vexing problem in Debian (testing). In Windoze I
can connect to the Internet and even if left unattended with no
upload/download activity it will stay connected for exactly 5 hours
before the ISP automatically disconnects. However in Linux even when I
am uploading/downloading (such as running "apt-get upgrade", or even
IRCing or browsing the web) it will run usually disconnect me much
sooner than 5 hours. More often than not it will disconnect after just
1-2 hours. This morning in fact It disconnected 3 times in a 90 minute
period (18 minutes connected, 15 minutes connect, 50 minutes
connected). This is really perplexing. I cannot find any explanation
or error message in /var/log to explain this behavior. I am using a
SupraExpress 56 SP serial modem (also I wonder why the max download
transfer rate I get is around 30KB/s whereas in Windoze I can get
50KB/s). Here is all I could
find in the logfiles:
netrek:~# pon isp.com
(I setup my dialup connection using pppconfig. It connects using PAP,
and there is no idle-timeout set on my end.)
>From /var/log/messages:
Jan 13 15:55:09 netrek pppd[16083]: pppd 2.4.4 started by root, uid 0
Jan 13 15:55:09 netrek chat[16084]: abort on (BUSY)
Jan 13 15:55:09 netrek chat[16084]: abort on (NO CARRIER)
Jan 13 15:55:09 netrek chat[16084]: abort on (VOICE)
Jan 13 15:55:09 netrek chat[16084]: abort on (NO DIALTONE)
Jan 13 15:55:09 netrek chat[16084]: abort on (NO DIAL TONE)
Jan 13 15:55:09 netrek chat[12971]: abort on (NO ANSWER)
Jan 13 15:55:09 netrek chat[12971]: abort on (DELAYED)
Jan 13 15:55:09 netrek chat[12971]: send (ATZ^M)
Jan 13 15:55:09 netrek chat[12971]: expect (OK)
Jan 13 15:55:09 netrek chat[12971]: ATZ^M^M
Jan 13 15:55:09 netrek chat[12971]: OK
Jan 13 15:55:09 netrek chat[12971]: -- got it
Jan 13 15:55:09 netrek chat[12971]: send (ATDT4123085032^M)
Jan 13 15:55:10 netrek chat[12971]: expect (CONNECT)
Jan 13 15:55:10 netrek chat[12971]: ^M
Jan 13 15:55:34 netrek chat[12971]: ATDT4123085032^M^M
Jan 13 15:55:34 netrek chat[12971]: CONNECT
Jan 13 15:55:34 netrek chat[12971]: -- got it
Jan 13 15:55:34 netrek chat[12971]: send (\d)
Jan 13 15:55:35 netrek pppd[12970]: Serial connection established.
Jan 13 15:55:35 netrek pppd[12970]: Using interface ppp0
Jan 13 15:55:35 netrek pppd[12970]: Connect: ppp0 <--> /dev/ttyS0
Jan 13 15:55:37 netrek pppd[12970]: PAP authentication succeeded
Jan 13 15:55:37 netrek pppd[12970]: local IP address 69.72.13.212
Jan 13 15:55:37 netrek pppd[12970]: remote IP address 209.163.112.40
Jan 13 16:22:37 netrek -- MARK --
Jan 13 16:42:37 netrek -- MARK --
Jan 13 17:02:37 netrek -- MARK --
Jan 13 17:22:37 netrek -- MARK --
Jan 13 17:28:57 netrek pppd[12970]: Hangup (SIGHUP)
Jan 13 17:28:57 netrek pppd[12970]: Modem hangup
Jan 13 17:28:57 netrek pppd[12970]: Connect time 93.4 minutes.
Jan 13 17:28:57 netrek pppd[12970]: Sent 2439708 bytes, received
14941908 bytes.Jan 13 17:28:57 netrek pppd[12970]: Connection
terminated.
Jan 13 17:28:58 netrek pppd[12970]: Exit.
>From /var/log/syslog:
Jan 13 17:28:57 netrek pppd[12970]: Hangup (SIGHUP)
Jan 13 17:28:57 netrek pppd[12970]: Modem hangup
Jan 13 17:28:57 netrek pppd[12970]: Connect time 93.4 minutes.
Jan 13 17:28:57 netrek pppd[12970]: Sent 2439708 bytes, received
14941908 bytes\.
Jan 13 17:28:57 netrek pppd[12970]: Script /etc/ppp/ip-down started (pid 15027)
Jan 13 17:28:57 netrek pppd[12970]: Connection terminated.
>From /var/log/debug:
Jan 13 17:28:57 netrek pppd[12970]: Script /etc/ppp/ip-down started (pid 15027)
Jan 13 17:28:58 netrek pppd[12970]: Script /etc/ppp/ip-down finished
(pid 15027\), status = 0x0
Here is my /etc/syslog/conf, any modifcations you would suggest for
increased logging? I looked through literally every logfile in
/var/log and could find no cause for the disconnects. Can provide PPP
setup files if needed.
/etc/syslog.conf:
# /etc/syslog.conf Configuration file for syslogd.
#
# For more information see syslog.conf(5)
# manpage.
#
# First some standard logfiles. Log by facility.
#
auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none -/var/log/syslog
#cron.* /var/log/cron.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
lpr.* -/var/log/lpr.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
uucp.* /var/log/uucp.log
#
# Logging for the mail system. Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info -/var/log/mail.info
mail.warn -/var/log/mail.warn
mail.err /var/log/mail.err
# Logging for INN news system
#
news.crit /var/log/news/news.crit
news.err /var/log/news/news.err
news.notice -/var/log/news/news.notice
#
# Some `catch-all' logfiles.
#
*.=debug;\
auth,authpriv.none;\
news.none;mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages
#
# Emergencies are sent to everybody logged in.
#
*.emerg *
#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;\
# news.=crit;news.=err;news.=notice;\
# *.=debug;*.=info;\
# *.=notice;*.=warn /dev/tty8
# The named pipe /dev/xconsole is for the `xconsole' utility. To use it,
# you must invoke `xconsole' with the `-file' option:
#
# $ xconsole -file /dev/xconsole [...]
#
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
# busy site..
#
daemon.*;mail.*;\
news.crit;news.err;news.notice;\
*.=debug;*.=info;\
*.=notice;*.=warn |/dev/xconsole
############ BASTILLE ADDITIONS BELOW : #################
# Log all kernel messages to the new file /var/log/kernel
kern.* /var/log/kernel
# Log all logins to /var/log/loginlog
auth.*;user.*;daemon.none /var/log/loginlog
# Log additional data to the Alt-F7 and Alt-F8 screens (Pseudo TTY 7 and 8)
*.info;mail.none;authpriv.none /dev/tty7
authpriv.* /dev/tty7
*.warn;*.err /dev/tty7
kern.* /dev/tty7
mail.* /dev/tty8
*.* /dev/tty12
########## BASTILLE ADDITIONS CONCLUDED : ###############
Regards,
Zach
More information about the wplug
mailing list