> Greetings all
Yo Robin
> I'm in the process of installing several full-duplex links which nearly
> all consist of a single TX and 2 or 3 RX at each site. I would like
> to experiment with using virtual circuit on these links but only one
> leg at each site will be using the TX & RX on the same physical port.
I think so :-)
I added something like that a while back ... since I am at work without
Linux, the following is from the top of my head, or worse.
> Is there a way of establishing an AX25 circuit where the RX may be
> coming back on a different port? I can do it using JNOS with a
> multiple port KISS TNC device by *not* attaching the second port
> whereby JNOS defaults to thinking any traffic on the unattached
> port is on the 'master' KISS port. Does Linux behave in a similar fashion?
> (not very likely methinks).
No it works in a much simpler (and cleaner) manner. Its called forwarding in
the kernel AX.25 code. I think I stole the name from John G8BPQ who also has
the same feature in his code.
You set up all three TNCs as normal with kissattach, set up your IP routes,
and all the rest for each port separately.
Then you use forwarding to merge two of the transmit ports into one port. It
used to be a command in axparms, but as I said the details are sketchy. I
think I added the feature for Martin G8IMB a few years ago.
In the kernel, each AX.25 device has a structure that has a pointer to another
device or NULL. If it is NULL (the default) then the port operates normally, but
if it is not NULL then all transmit packets are sent to the pointed to device
instead.
Does that make sense ?
> Cheers
>
> --
> 73 de Robin. G8ECJ Hub manager gb7ipd
Jonathan HB9/G4KLX
