[Xastir] dual port TNC
Tom Russo
russo at bogodyn.org
Tue Jun 16 13:58:11 EDT 2009
On Tue, Jun 16, 2009 at 11:15:13AM -0600, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
[TNC sharing]
>
> I have been trying to figure out ways to do this without ldsped, and they
> all seem to revolve around "kissnetd" and remserial.
>
> The thing that's missing is a simple program that can tie together two
> ax.25 network ports. Digi_ned's web page describes a way of doing it with
> digi_ned, but since I don't really want to do any digipeating that seems the
> wrong approach.
>
> Here's what I've thought might do the trick if that one piece were available:
>
>
>
>
> +--- ax25bridge---+ 2 3 4
> | | pty pty pty
> ax25p1 ax25p2 | | |
> | | | | |
> KISS TNC PTY1 | | |
> | | | |
> +--kissnetd--+---+---+
>
> That is, there's an AX.25 kernel interface to a real tnc, bridged simply
> to a second ax.25 interface that talks KISS on a PTY. kissnetd creates
> a fake network of PTYs that all talk KISS to one-another. The ptys can be
> attached to applications, or to remserial. Obviously, the PTYs are really
> pairs of devices, I'm just showing them as one for simplicity of the figure.
[...]
>
> It's that simple bridge that doesn't seem to exist.
[...]
Someone here just mentioned socat in this thread. I've never used it, but
it appears that it could possibly be exactly the tool for the job:
socat INTERFACE:ax25p1 INTERFACE:ax25p2
Has anyone used socat to connect interfaces directly this way? If it works
then perhaps the little ugly ascii graphic above can be implemented trivially
with existing tools (socat, kissnetd, remserial, and ax.25 kernel networking).
--
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM
In some cultures what I do would be considered normal.
-- Ineffective daily affirmation
More information about the Xastir
mailing list