Xref: utzoo rec.ham-radio.packet:3389 comp.protocols.tcp-ip.ibmpc:2582
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!texbell!bellcore!ka9q.bellcore.com!karn
From: karn@ka9q.bellcore.com (Phil Karn)
Newsgroups: rec.ham-radio.packet,comp.protocols.tcp-ip.ibmpc
Subject: Re: "Bad Header!" message in ka9q
Keywords: Bad Header, ka9q, AX25, Net
Message-ID: <21137@bellcore.bellcore.com>
Date: 21 Mar 90 08:45:22 GMT
References: <638@ncelvax.UUCP>
Sender: news@bellcore.bellcore.com
Reply-To: karn@ka9q.bellcore.com (Phil Karn)
Organization: Secular Humanists for No-Code
Lines: 9


The message "Bad Header!" from NET (I assume you have trace turned on)
means exactly what it says: that the host computer received a frame
from the TNC that has a bad AX.25 header. This is usually due to character
loss in the link between the TNC and the host computer. There is no
flow control in the KISS TNC protocol, so this problem can happen if you
run the link too fast. Try slowing it down to 4800 or 2400 baud.

Phil