Subject: ip fuzziness
To: None <port-mac68k@NetBSD.ORG>
From: brian wildasinn <bwildasi@csulb.edu>
List: port-mac68k
Date: 04/26/1998 00:38:21
--------------98C685CFB9FE26F54BAFF289
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Hi everybody!
Could someone take a look at this /var/log/messages for me? Any insight
or links to other faqs is appreciated! I apologize if this is a stupid
question: Is there a list of protocols for netbsd and ppp? how about the
other error message?
Apr 23 08:10:20 pppd[563]: pppd 2.3.1 started by root, uid 0
Apr 23 08:12:43 pppd[563]: Serial connection established.
Apr 23 08:12:44 pppd[563]: Using interface ppp0
Apr 23 08:12:44 pppd[563]: Connect: ppp0 <--> /dev/tty00
Apr 23 08:12:45 /netbsd: ppp0: bad protocol 820
Apr 23 08:12:48 pppd[563]: Remote message: Login Succeeded
Apr 23 08:12:48 pppd[563]: local IP address 134.139.23.129
Apr 23 08:12:48 pppd[563]: remote IP address 134.139.39.14
Apr 23 08:14:16 /netbsd: ppp0: packet too big
Apr 23 08:14:47 last message repeated 2 times
Apr 23 08:16:33 last message repeated 2 times
Apr 23 08:19:46 last message repeated 3 times
Apr 23 08:21:22 /netbsd: ppp0: bad fcs d69d
Apr 23 08:21:23 /netbsd: ppp0: packet too big
Apr 23 08:32:08 /netbsd: ppp0: bad fcs 2d9c
Apr 23 08:32:18 pppd[563]: appear to have received our own echo-reply!
Apr 23 08:32:37 pppd[563]: Terminating on signal 15.
Apr 23 08:32:37 pppd[563]: Connection terminated.
Apr 23 08:32:38 pppd[563]: Terminating on signal 15.
Apr 23 08:32:38 pppd[563]: disconnect script failed
Apr 23 08:32:40 pppd[563]: Exit.
Apr 23 08:32:43 pppd[617]: pppd 2.3.1 started by root, uid 0
Apr 23 08:35:06 pppd[617]: Serial connection established.
Apr 23 08:35:07 pppd[617]: Using interface ppp0
Apr 23 08:35:07 pppd[617]: Connect: ppp0 <--> /dev/tty00
Apr 23 08:35:08 /netbsd: ppp0: bad protocol 820
Apr 23 08:35:11 pppd[617]: Remote message: Login Succeeded
Apr 23 08:35:11 pppd[617]: local IP address 134.139.23.152
Apr 23 08:35:11 pppd[617]: remote IP address 134.139.39.14
Apr 23 08:37:25 /netbsd: ppp0: packet too big
Apr 23 08:41:24 /netbsd: ppp0: packet too big
Apr 23 08:41:33 /netbsd: ppp0: packet too big
Apr 23 08:47:45 /netbsd: ppp0: packet too big
Apr 23 08:49:13 /netbsd: ppp0: bad fcs 7180
Apr 23 08:49:17 /netbsd: ppp0: bad fcs 39dc
Apr 23 08:49:26 /netbsd: ppp0: bad fcs 232d
Apr 23 08:49:32 /netbsd: ppp0: bad fcs 3d9c
A
Here's what one of the NetBSD faq's says about packets:
> 2.2.12 : I'm having trouble with the networking code (specifically the PPP stuff to
> my ISP). How can I debug NetBSD's networking?
>
> Bring the PPP connection up again. Retry whatever-it-is that's failing.
>
> PPP includes a link-level checksum. Watch the packet counts in the netstat -I ppp? output over time. Check carefully
> to see whether the PPP driver is recording input errors (frames whose CRC failed.) Frames with bad checksums are
> counted in Ierr field. A non-zero count indicates _something_, possibly overruns, is in fact garbling your PPP traffic.
> If the packets are being discarded due to errors at the PPP level, they'll never even get as far as IP.
>
> Also, use netstat (or an SNMP daemon and monitor, if you prefer) to watch the rate of change of bad packets at the IP
> and TCP level. I run "netstat -p ip" "netstat -p tcp". One has to manually compute the rate of change; netstat's -i option
> means something different to, say, vmstat's. (Adding periodic sampling and rate-of-change to netstat would be a Cool
> Project.)
>
> At the IP level, the relevant statistics are
>
>
> 0 bad header checksums
> 0 with size smaller than minimum
> 0 with data size < data length
> 0 with header length < data size
> 0 with data length < header length
> 0 with bad options
>
My machine's problem may be at the ip level?
For example, Apr 23 08:32:08 /netbsd: ppp0: bad fcs 2d9c
> 0 with incorrect version number
> [...]
> 0 output packets dropped due to no bufs, etc.
>
> At the TCP level, look for, e.g.,
>
>
> 0 discarded for bad checksums
> 0 discarded for bad header offset fields
> 0 discarded because packet too short
>
Just the opposite for example: Apr 23 08:37:25 /netbsd: ppp0: packet
too big
>
> Any of these being non-zero would support the hypothesis of a bug in the PPP implementation. Unlikely, but one
> never knows.
>
> It could be that a TCP ack got munged or dropped by your PPP link; or possibly somewhere else in the Internet.
> That's not abnormal on busy links.
>
> What OS is your FTP peer running? Is it a pre-2.0.0 Linux or an older version of a commercial Unix? If so, have you
> tried turning off rfc1323 on your NetBSD machine??
>
It's a NeXT machine.
And here the /etc/ppp files making the ip connection possible:
#-----------------------> chap-secrets
login-name * password *
#-----------------------> options
passive
crtscts
defaultroute
lock
ipcp-accept-remote
ipcp-accept-local
lcp-echo-interval 30
lcp-echo-failure 10
netmask 255.255.0.0
domain csulb.edu
mtu 1500
user bwildasi
disconnect /etc/ppp/ppp-down
debug kdebug 1
#------------------------> pap-secrets
username * password
#------------------------> ppp-chat
ECHO ON
ABORT BUSY
ECHO OFF
SAY "Dialing your ISP ..."
ABORT "NO CARRIER"
ABORT "NO DIAL"
TIMEOUT 10
SAY "Waiting up to 2 minutes for connection ...\n"
"" ATZ OK AT&FE1V1Q0&A3&B1&H1&R2&D0&C1X4S0=0S7=90
OK ATDT$NUMBER
TIMEOUT 60
CONNECT ""
SAY "Connected, now logging in ...\0"
ECHO ON
me:-\r-me: $LOGIN
word: $PASSWD
SAY "Logged in okay ...\0"
ncs> ppp
#--------------------------> ppp-connect
#!/bin/sh
#
# usage: ppp-connect <number-list> <login> <template chat script>
if [ $# -ne 3 ]
then
echo 'usage: ppp-connect <number-list> <login> <template chat script>'
1>&2
exit 1
fi
#
stty clocal
umask 077
#
NUMBERLIST=`cat $1`
#
NUMBER=${NUMBERLIST%%:*}
NUMBERLIST=${NUMBERLIST#*:}:$NUMBER
#
#until (sed -e "s/\$NUMBER/$NUMBER/g" -f $2 $3 >/tmp/chat-script; chat
-v -f /tmp/chat-script)
until (sed -e "s/\$NUMBER/$NUMBER/g" -f $2 $3 >/tmp/chat-script; chat -r
/tmp/ppp-report -f /tmp/chat-script | tee xconsole )
do
NUMBER=${NUMBERLIST%%:*}
NUMBERLIST=${NUMBERLIST#*:}:$NUMBER
done
rm -f /tmp/chat-script
#-------------------------> ppp-debug
#! /bin/sh
#
# usage: ppp-debug [ on | off ]
#
if [ $# -eq 1 ]
then
if [ $1 = on ]
then
sed -e "s/+v/-v/g" < /etc/ppp/options > /etc/ppp/options
grep -v "local2.*" /etc/syslog.conf > /etc/syslog.conf.temp
echo "local2.* /dev/console" >> /etc/syslog.conf.temp
mv /etc/syslog.conf.temp /etc/syslog.conf
kill -HUP `cat /var/run/syslog.pid`
elif [ $1 = off ]
then
sed -e "s/-v/+v/g" < /etc/ppp/options > /etc/ppp/options
grep -v "local2.*" /etc/syslog.conf > /etc/syslog.conf.temp
mv /etc/syslog.conf.temp /etc/syslog.conf
kill -HUP `cat /var/run/syslog.pid`
else
echo "usage: ppp-debug [ on | off ]" 2>&1
fi
else
echo "usage: ppp-debug [ on | off ]" 2>&1
fi
#-----------------------> ppp-down
#!/bin/sh
p=`cd /proc; grep -l '^pppd' */status | sed 's,^\([0-9]*\)/.*$,\1,'`
#
if [ -n "$p" ]; then
echo -n killing pppd...
kill $p
echo done
else
echo ppp already is down 1>&2
fi
#---------------------> ppp-login
s/\$LOGIN/user_name/g
s/\$PASSWD/password/g
#---------------------> ppp-numbers
985-7777:985-7777:985-7777:985-8660
#---------------------> ppp-up
#!/bin/sh
# ppp-up - start pppd
#
PPPDIR=/etc/ppp
NUMBERLIST=$PPPDIR/ppp-numbers
LOGIN=$PPPDIR/ppp-login
CHATSCRIPT=$PPPDIR/ppp-chat
CONNECT=$PPPDIR/ppp-connect
#
# To change this file to work w/ tty01, just change all the tty00's
# to tty01's in this file (two immediately below, one on the pppd line)
# and in the ppp-down script.
#
ECHO ON
if [ -f /var/spool/lock/LCK..tty00 ]; then
p=`cat /var/spool/lock/LCK..tty00`
else
p=""
fi
#
if [ -n "$p" ]; then
echo -n pppd is already running...
else
echo -n starting the pppd daemon...
pppd /dev/tty00 19200 connect "$CONNECT $NUMBERLIST $LOGIN $CHATSCRIPT"
#pppd /dev/tty00 115200 connect "$CONNECT $NUMBERLIST $LOGIN
$CHATSCRIPT"
fi
echo done
#--------------------> resolv.conf.down
#
# Resolv.conf
#
#
nameserver 134.139.1.2
domain garuda.csulb.edu
nameserver ip.ad.dr.02
lookup file bind
#--------------------> there ain't no more files for /etc/ppp
Sorry this is soooo long, but it's all here in one nice neat place for
viewing by those knowledgeable about such things. Could it be the
kernel choking, since the errors mention /netbsd ppp0:? Or maybe the
data isn't being properly fragmented? Is there a way to fix this?
Thanks again for any tips. Sincerely,
bw
bwildasi@csulb.edu
Q700, netbsd-1.3, Bill Studenmund PPP Scripts
--------------98C685CFB9FE26F54BAFF289
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<HTML>
Hi everybody!
<BR>Could someone take a look at this /var/log/messages for me? Any
insight or links to other faqs is appreciated! I apologize if this is a
stupid question: Is there a list of protocols for netbsd and ppp? how about
the other error message?
<P>Apr 23 08:10:20 pppd[563]: pppd 2.3.1 started by root, uid 0
<BR>Apr 23 08:12:43 pppd[563]: Serial connection established.
<BR>Apr 23 08:12:44 pppd[563]: Using interface ppp0
<BR>Apr 23 08:12:44 pppd[563]: Connect: ppp0 <--> /dev/tty00
<BR>Apr 23 08:12:45 /netbsd: ppp0: bad protocol 820
<BR>Apr 23 08:12:48 pppd[563]: Remote message: Login Succeeded
<BR>Apr 23 08:12:48 pppd[563]: local IP address 134.139.23.129
<BR>Apr 23 08:12:48 pppd[563]: remote IP address 134.139.39.14
<BR>Apr 23 08:14:16 /netbsd: ppp0: packet too big
<BR>Apr 23 08:14:47 last message repeated 2 times
<BR>Apr 23 08:16:33 last message repeated 2 times
<BR>Apr 23 08:19:46 last message repeated 3 times
<BR>Apr 23 08:21:22 /netbsd: ppp0: bad fcs d69d
<BR>Apr 23 08:21:23 /netbsd: ppp0: packet too big
<BR>Apr 23 08:32:08 /netbsd: ppp0: bad fcs 2d9c
<BR>Apr 23 08:32:18 pppd[563]: appear to have received our own echo-reply!
<BR>Apr 23 08:32:37 pppd[563]: Terminating on signal 15.
<BR>Apr 23 08:32:37 pppd[563]: Connection terminated.
<BR>Apr 23 08:32:38 pppd[563]: Terminating on signal 15.
<BR>Apr 23 08:32:38 pppd[563]: disconnect script failed
<BR>Apr 23 08:32:40 pppd[563]: Exit.
<BR>Apr 23 08:32:43 pppd[617]: pppd 2.3.1 started by root, uid 0
<BR>Apr 23 08:35:06 pppd[617]: Serial connection established.
<BR>Apr 23 08:35:07 pppd[617]: Using interface ppp0
<BR>Apr 23 08:35:07 pppd[617]: Connect: ppp0 <--> /dev/tty00
<BR>Apr 23 08:35:08 /netbsd: ppp0: bad protocol 820
<BR>Apr 23 08:35:11 pppd[617]: Remote message: Login Succeeded
<BR>Apr 23 08:35:11 pppd[617]: local IP address 134.139.23.152
<BR>Apr 23 08:35:11 pppd[617]: remote IP address 134.139.39.14
<BR>Apr 23 08:37:25 /netbsd: ppp0: packet too big
<BR>Apr 23 08:41:24 /netbsd: ppp0: packet too big
<BR>Apr 23 08:41:33 /netbsd: ppp0: packet too big
<BR>Apr 23 08:47:45 /netbsd: ppp0: packet too big
<BR>Apr 23 08:49:13 /netbsd: ppp0: bad fcs 7180
<BR>Apr 23 08:49:17 /netbsd: ppp0: bad fcs 39dc
<BR>Apr 23 08:49:26 /netbsd: ppp0: bad fcs 232d
<BR>Apr 23 08:49:32 /netbsd: ppp0: bad fcs 3d9c
<BR>A
<P>Here's what one of the NetBSD faq's says about packets:
<BLOCKQUOTE TYPE=CITE>
<PRE>2.2.12 : I'm having trouble with the networking code (specifically the PPP stuff to
my ISP). How can I debug NetBSD's networking?
Bring the PPP connection up again. Retry whatever-it-is that's failing.
PPP includes a link-level checksum. Watch the packet counts in the netstat -I ppp? output over time. Check carefully
to see whether the PPP driver is recording input errors (frames whose CRC failed.) Frames with bad checksums are
counted in Ierr field. A non-zero count indicates _something_, possibly overruns, is in fact garbling your PPP traffic.
If the packets are being discarded due to errors at the PPP level, they'll never even get as far as IP.
Also, use netstat (or an SNMP daemon and monitor, if you prefer) to watch the rate of change of bad packets at the IP
and TCP level. I run "netstat -p ip" "netstat -p tcp". One has to manually compute the rate of change; netstat's -i option
means something different to, say, vmstat's. (Adding periodic sampling and rate-of-change to netstat would be a Cool
Project.)
At the IP level, the relevant statistics are
0 bad header checksums
0 with size smaller than minimum
0 with data size < data length
0 with header length < data size
0 with data length < header length
0 with bad options</PRE>
</BLOCKQUOTE>
My machine's problem may be at the ip level?
<BR>For example, Apr 23 08:32:08 /netbsd: ppp0: bad fcs 2d9c
<BLOCKQUOTE TYPE=CITE>
<PRE>
0 with incorrect version number
[...]
0 output packets dropped due to no bufs, etc.
At the TCP level, look for, e.g.,
0 discarded for bad checksums
0 discarded for bad header offset fields
0 discarded because packet too short</PRE>
</BLOCKQUOTE>
Just the opposite for example: Apr 23 08:37:25 /netbsd: ppp0: packet
too big
<BLOCKQUOTE TYPE=CITE>
<PRE>
Any of these being non-zero would support the hypothesis of a bug in the PPP implementation. Unlikely, but one
never knows.
It could be that a TCP ack got munged or dropped by your PPP link; or possibly somewhere else in the Internet.
That's not abnormal on busy links.
What OS is your FTP peer running? Is it a pre-2.0.0 Linux or an older version of a commercial Unix? If so, have you
tried turning off rfc1323 on your NetBSD machine??</PRE>
</BLOCKQUOTE>
It's a NeXT machine.
<P>And here the /etc/ppp files making the ip connection possible:
<BR>#-----------------------> chap-secrets
<BR>login-name * password *
<BR>#-----------------------> options
<BR>passive
<BR>crtscts
<BR>defaultroute
<BR>lock
<BR>ipcp-accept-remote
<BR>ipcp-accept-local
<BR>lcp-echo-interval 30
<BR>lcp-echo-failure 10
<BR>netmask 255.255.0.0
<BR>domain csulb.edu
<BR>mtu 1500
<BR>user bwildasi
<BR>disconnect /etc/ppp/ppp-down
<BR>debug kdebug 1
<BR>#------------------------> pap-secrets
<BR>username * password
<BR>#------------------------> ppp-chat
<BR>ECHO ON
<BR>ABORT BUSY
<BR>ECHO OFF
<BR>SAY "Dialing your ISP ..."
<BR>ABORT "NO CARRIER"
<BR>ABORT "NO DIAL"
<BR>TIMEOUT 10
<BR>SAY "Waiting up to 2 minutes for connection ...\n"
<BR>"" ATZ OK AT&FE1V1Q0&A3&B1&H1&R2&D0&C1X4S0=0S7=90
<BR>OK ATDT$NUMBER
<BR>TIMEOUT 60
<BR>CONNECT ""
<BR>SAY "Connected, now logging in ...\0"
<BR>ECHO ON
<BR>me:-\r-me: $LOGIN
<BR>word: $PASSWD
<BR>SAY "Logged in okay ...\0"
<BR>ncs> ppp
<BR>#--------------------------> ppp-connect
<BR>#!/bin/sh
<BR>#
<BR># usage: ppp-connect <number-list> <login> <template chat
script>
<BR>if [ $# -ne 3 ]
<BR>then
<BR> echo 'usage: ppp-connect <number-list> <login> <template
chat script>' 1>&2
<BR> exit 1
<BR>fi
<BR>#
<BR>stty clocal
<BR>umask 077
<BR>#
<BR>NUMBERLIST=`cat $1`
<BR>#
<BR>NUMBER=${NUMBERLIST%%:*}
<BR>NUMBERLIST=${NUMBERLIST#*:}:$NUMBER
<BR>#
<BR>#until (sed -e "s/\$NUMBER/$NUMBER/g" -f $2 $3 >/tmp/chat-script; chat
-v -f /tmp/chat-script)
<BR>until (sed -e "s/\$NUMBER/$NUMBER/g" -f $2 $3 >/tmp/chat-script; chat
-r /tmp/ppp-report -f /tmp/chat-script | tee xconsole )
<BR>do
<BR> NUMBER=${NUMBERLIST%%:*}
<BR> NUMBERLIST=${NUMBERLIST#*:}:$NUMBER
<BR>done
<BR>rm -f /tmp/chat-script
<BR>#-------------------------> ppp-debug
<BR>#! /bin/sh
<BR>#
<BR># usage: ppp-debug [ on | off ]
<BR>#
<BR>if [ $# -eq 1 ]
<BR>then
<BR> if [ $1 = on ]
<BR> then
<BR> sed -e "s/+v/-v/g" < /etc/ppp/options > /etc/ppp/options
<BR> grep -v "local2.*" /etc/syslog.conf > /etc/syslog.conf.temp
<BR> echo "local2.* /dev/console" >> /etc/syslog.conf.temp
<BR> mv /etc/syslog.conf.temp /etc/syslog.conf
<BR> kill -HUP `cat /var/run/syslog.pid`
<BR> elif [ $1 = off ]
<BR> then
<BR> sed -e "s/-v/+v/g" < /etc/ppp/options > /etc/ppp/options
<BR> grep -v "local2.*" /etc/syslog.conf > /etc/syslog.conf.temp
<BR> mv /etc/syslog.conf.temp /etc/syslog.conf
<BR> kill -HUP `cat /var/run/syslog.pid`
<BR> else
<BR> echo "usage: ppp-debug [ on | off ]" 2>&1
<BR> fi
<BR>else
<BR> echo "usage: ppp-debug [ on | off ]" 2>&1
<BR>fi
<BR>#-----------------------> ppp-down
<BR>#!/bin/sh
<BR>p=`cd /proc; grep -l '^pppd' */status | sed 's,^\([0-9]*\)/.*$,\1,'`
<BR>#
<BR>if [ -n "$p" ]; then
<BR> echo -n killing pppd...
<BR> kill $p
<BR> echo done
<BR>else
<BR> echo ppp already is down 1>&2
<BR>fi
<BR>#---------------------> ppp-login
<BR>s/\$LOGIN/user_name/g
<BR>s/\$PASSWD/password/g
<BR>#---------------------> ppp-numbers
<BR>985-7777:985-7777:985-7777:985-8660
<BR>#---------------------> ppp-up
<BR>#!/bin/sh
<BR># ppp-up - start pppd
<BR>#
<BR>PPPDIR=/etc/ppp
<BR>NUMBERLIST=$PPPDIR/ppp-numbers
<BR>LOGIN=$PPPDIR/ppp-login
<BR>CHATSCRIPT=$PPPDIR/ppp-chat
<BR>CONNECT=$PPPDIR/ppp-connect
<BR>#
<BR># To change this file to work w/ tty01, just change all the tty00's
<BR># to tty01's in this file (two immediately below, one on the pppd line)
<BR># and in the ppp-down script.
<BR>#
<BR>ECHO ON
<BR>if [ -f /var/spool/lock/LCK..tty00 ]; then
<BR> p=`cat /var/spool/lock/LCK..tty00`
<BR>else
<BR> p=""
<BR>fi
<BR>#
<BR>if [ -n "$p" ]; then
<BR> echo -n pppd is already running...
<BR>else
<BR> echo -n starting the pppd daemon...
<BR>pppd /dev/tty00 19200 connect "$CONNECT $NUMBERLIST $LOGIN $CHATSCRIPT"
<BR>#pppd /dev/tty00 115200 connect "$CONNECT $NUMBERLIST $LOGIN $CHATSCRIPT"
<BR>fi
<BR>echo done
<BR>#--------------------> resolv.conf.down
<BR>#
<BR># Resolv.conf
<BR>#
<BR>#
<BR>nameserver 134.139.1.2
<BR>domain garuda.csulb.edu
<BR>nameserver ip.ad.dr.02
<BR>lookup file bind
<BR>#--------------------> there ain't no more files for /etc/ppp
<BR>
<BR>Sorry this is soooo long, but it's all here in one nice neat place
for viewing by those knowledgeable about such things. Could it be
the kernel choking, since the errors mention /netbsd ppp0:? Or maybe the
data isn't being properly fragmented? Is there a way to fix this?
<P>Thanks again for any tips. Sincerely,
<P>bw
<BR>bwildasi@csulb.edu
<BR>Q700, netbsd-1.3, Bill Studenmund PPP Scripts</HTML>
--------------98C685CFB9FE26F54BAFF289--