IMHO ax25rtd is only helpful for tcp/ip nodes which are accessed by users
via digipeaters (i.e. the digipeaters are not known a-priori and probably change
with time). There may be other applications, but I don't recommend it for client
machines.
For the case mentioned in the original message, the following actions should be
enough:
* Add an IP route for the host you want to talk to on the right interface
(this seems to be already ok, since ARP broadcasts are going out).
* Add an ARP entry for the host you want to talk to (otherwise your machine has
to
use ARP broadcasts to find out the callsign, which doesn't work over
digipeaters).
The hw address type must be ax25.
The callsign/ssid must be the one of the host you want to reach, NOT the one
of the
digipeater. For now, let's call it HOST-1:
arp -H ax25 1.2.3.4 HOST-1
* Add an ax25 route to HOST-1 via digipeater DIGI-1:
axparms -route add ax0 HOST-1 DIGI-1
I'm not 100% sure about the syntax, please check the man pages.
73 de Klaus OE1KIB