Re: axports & ax25d.conf
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Sun, 13 Mar 2011, echicken wrote:
In the "ax25d not hearing ..." thread, when you say:The connection packet itself doesn't specify the upper-level protocol being used, therefore there's nothing to send to the application at that point. Send a blank packet immediately after the connect packet which should pass a LF or a CRLF off to aprsd. Aprsd should then respond.Do you mean that the client should be sending a blank packet to my server? Is there anything more to accomplishing this than simply sending a CRLF from the remote / connecting side? I've tried to do this to no avail.
I remember from waaaayyyyy back when I used to do a lot of tcp/ip over ax.25 here in the Seattle area that it would just sit there after the connect until you sent some packet. This may have been fixed somehow since then, but that's what I recall. The good news is that I'm getting back into tcp/ip over RF. I'm messing with YAM modems and 9600-baud TNC's here, and just came up on 220 9600-baud friday night. Eventually I plan to have both a 220 and a 440 port on 9600-baud as well as the 1200-baud AX.25 port running APRS. This should keep me more up-to-date on the issues than I have been for the last bunch of years. We plan to have a 220 9600-baud full-duplex bit-regen repeater up and running sometime this year too, to replace our aging 1200-baud repeater that doesn't work so well anymore. That should get our area buzzing again. Literally! -- Curt, WE7U. http://www.eskimo.com/~archer The world DOES revolve around me: I picked the coordinate system!"