From: Charles E. Gelm (tnohvgr@tallink.fi)
Date: Thu Oct 05 2000 - 16:26:02 EEST
Hi, James:
I've seen this event in DOS and it might be the same in linux.
The TNC's SENDPAC character is the carriage return, ASCII 13 (0dh).
The terminal software carriage return is carriage return + line feed.
The TNC is sending the data in front of the carriage return and
leaving the line feed character in its text buffer.
The first data transmission is fine as it does not contain a
leading line feed (ASCII 10, 0ah), each subsequent transmission
has a line feed as the first character, confusing the pBBS application.
You may need to change the TNC parameters or the terminal settings
to deal with the line feeds.
HTH, Chuck nc8q
James McBride wrote:
>
> Hi
> I currently have been trying to get a RedHat 6 based system with a Kernel
> 2.2.17 upgrade working with a KISS TNC and it is all configured okay, but
> for some reason after an initial connect, each time I send some plain text,
> the packet appears to have another 2 characters appended to it after an
> end-of-line, so if for instance I enter a command like 'B' to my local BBS
> here, it appears at the other end to be something like 'UB' and is not
> understood. The 'B' is still there, but the extra characters in the packet
> cause it to have a frame problem.... the next few times you enter 'B', you
> get a response for say 'UB', ':B','YB' and 'TB' or something afterwhich the
> sequence repeats starting with 'UB'... To me it looks like the kernel is
> sending out a checksum or something that it shouldn't, but I am not a C
> source expert by any means - far from it.
>
> Also if someone connects to me, axspawn runs here, but they get a frame
> error sent back to them (probably with the extra characters!) and can't
> login properly. I receive all packets okay.
>
> An AXIP ping also seems to work once after a fresh restart of the system,
> but will not generate a response afterwards. My 'listen' screen shows an ARP
> received once from the other station, but then it just doesn't respond.
>
> I don't know if there is enough information here, but does anyone recognise
> this symptom?
>
> I have kernel 2.2.17, libax25-0.0.7, ax25-tools-0.0.5, ax25-apps-0.0.4 on a
> Pentium 100, with KISS on serial port compiled into the kernel (not a
> module).
>
> I also haven't got the OSS sound modules to load properly yet and don't seem
> to find a kernel configuration entry for '/dev/dsp and /dev/audio' support
> like there was in the 2.0.34/2.0.35 kernels. I have only ever had a 9600bps
> soundcard based modem running on kernel 2.0.35 with a SoundBlasterPro card.
> I am yet to try the new drivers (when the sound config works) and also the
> NewQPSK mode.
>
> Alot of interesting things in this newsgroup though... and for those in West
> Australia, see you at the Hamfest on Oct 29.
>
> Regards
> James McBride VK6FJA
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to tscvuu@mercadolatinoinc.com
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to terhi.victor@logonet.com
This archive was generated by hypermail 2b29 : Thu Oct 05 2000 - 16:22:22 EEST