geoff@ncelvax.UUCP (Geoff Dann) (03/22/90)
I'm posting this in case it helps someone else: I posted a request for help: >Often I get the message "AX25 Receive:" > "Bad Header!" Two responses helped me solve the problem: From Phil Karn ka9q: 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 And from James Dugal n5knx: I've seen this happen in two situations: 1. Running DoubleDos with a 4.77 MHz PC, with trace enabled, and the serial port to the tnc running at 9600 baud. It can't keep up with the data coming in, and the dropped chars yield a bad packet. 2. Somehow my transmitted packets seem to be heard by the TNC (a 1274 also) particularly when I use an indoor antenna and perhaps a too-wide deviation (I have to adjust the mike gain downward for packet). But the heard packet is not perfect, leading to error msgs in the trace. 73 & good luck, -- James I cranked down the audio output of my TNC (R76 - It's a many-turn pot (50???) (on a MFJ-1274)) and that seems to have solved the problem. I still have other problems, but....... Thanks................Geoff