Re: axports & ax25d.conf

[echicken <echicken@xxxxxxxxxxxxxxxxxxxxxxxxx>]

> 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.

Interesting.  It may be that I'm misunderstanding something about how
this works.  I'm not actually trying to do tcp/ip over AX.25, exactly.
 I just want pure AX.25 clients to be able to connect, and then have
something forward their input to a particular TCP/IP service and
forward its output to them.

> 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!

Sounds fun.  I've been curious about all manner of digital modes for a
long time, and really enjoy packet, but I've only been licensed for
about a year, so I'm still making sense of it.

Derek
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html