One possibility is the following.
If you are attempting to connect to the remote AXIP system using a
callsign other than the one assigned to the axip port, packets will
fall into the bit bucket.
For example, if the axip port has the call W8APR and I log into the
system using N8UR (via node, or via an associated callsign, I will not
be able to make a connection to the remote end of the axip link.
This is because the outbound packet has the source callsign of the user
(in the example, N8UR) instead of the axip port (W8APR). The other end
will receive the packet, and issue a response, but the response will be
addressed to the user call, not the axip call. It will travel back to
the W8APR machine, but when it gets there will be dropped, because
W8APR has no idea where a packet for N8UR should go.
Another message mentioned Bob's version of ax25ipd that learns routes
-- I haven't played with it yet to see if that solves this problem, but
it very well might. Another alternative, though a yuckey and evil one,
is to use NetRom as the internode transport rather than plain AX.25 --
that way, the AX.25 will be encapsulated in NetROM packets that contain
source addresses the system understands.
Hope I haven't sent you off on a goose chase with this, but we
encountered this problem here a year or so ago and it caused a lot of
head scratching.
73,
John N8UR
[EMAIL PROTECTED]
> I have been trying every trick up my sleeve to get a link working
> between a Tnos machine and another Linux machine hosting ax25-utils,
> xFBB and Tnos. Bob, I am using the binary you mentioned and it is
> gathering routes. The following is a list of test results using tcpdump
>
> ------------
> Start Tnos axip testa from Original Tnos box to a
> second Tnos box that also hosts the ax25ipd app.
>
> Open axip port to Tnos
> 07:25:44.778343 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 17
> 07:25:44.908681 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> 07:25:44.910983 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 40
> 07:25:44.912495 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 17
> Got "CONNECTED" Prompt
>
> Close axip port to Tnos
> 07:27:53.278846 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 20
> 07:27:53.280248 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> 07:27:53.430021 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 180
> 07:27:53.432286 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 17
> 07:27:53.912622 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> 07:27:53.914266 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 17
> Finish Tnos test with axip connect
>
> Another test from the Tnos interface (on the same box as ax25ipd
> to the original Tnos box (aa6qn.ampr.org)
> 08:49:46.578963 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> 08:49:46.578963 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> 08:49:51.489144 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 20
> 08:49:51.490778 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 17
> 08:49:51.588520 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 180
> Close the "Connected connection"
> 08:49:51.591197 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> 08:49:52.087571 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 17
> 08:49:52.089655 44.8.4.14 > aa6qn.ampr.org: ip-proto-93 17
> Finish test
> #
> # From TNOS too TNOS it works like a champ
>
> Start AX25IPD axip test from command line on first Tnos box
> too ax25ipd on second box
>
> 07:41:26.204689 aa6qn.ampr.org > axip.kc6ike.ampr.org: ip-proto-93 17
> 07:41:26.206564 www.aa6qn.ampr.org > aa6qn.ampr.org: ip-proto-93 17
> (no link made from axip.kc6ike.ampr.org [44.8.4.11]
> #
> Log output during connect attempt
> from_ip: AX25: (l= 68) AA6QN2 -> MAIL
> from_ip: AX25: (l= 15) AA6QN -> KC6IKE-3
> from_kiss: AX25: (l= 15) KC6IKE-3 -> AA6QN
> from_ip: AX25: (l= 15) AA6QN -> KC6IKE-3
> from_ip: AX25: (l= 15) AA6QN -> KC6IKE-3
> from_kiss: AX25: (l= 15) KC6IKE-3 -> AA6QN
> #
> Print out of 'L' command while in node
> SAW:KC6IKE-3 AX.25 Link Status:
> Port Remote Local State Unack T1 Retr Rtt Snd-Q
> Rcv-Q
> axip AA6QN-0 KC6IKE-3 Connected 00/02 000/010 00/10 5 0 0
> # I see a Connected at one end but not the other end of the pipe
> #
> Another test using the CALL feature 'call axip aa6qn-1 ' from second
> box hosting ax25ipd to the first Tnos box
>
> 08:34:12.541610 www.aa6qn.ampr.org > aa6qn.ampr.org: ip-proto-93 17
> 08:34:12.545761 www.aa6qn.ampr.org > aa6qn.ampr.org: ip-proto-93 17
> 08:34:12.546375 www.aa6qn.ampr.org > aa6qn.ampr.org: ip-proto-93 17
> [no link from ax25ipd 44.8.4.11 to aa6qn axip]
>
> ## Below are UI broadcast from the Tnos box during tcpdump
> 08:35:12.145280 aa6qn.ampr.org > axip.kc6ike.ampr.org: ip-proto-93 51
> 08:35:12.145583 aa6qn.ampr.org > axip.kc6ike.ampr.org: ip-proto-93 70
> 08:35:12.145840 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 51
> 08:35:12.146118 aa6qn.ampr.org > 44.8.4.14: ip-proto-93 70
> #
> ---------------------------
> Settings on ax25ipd are:
>
> Socket ip
> Mode tnc
> Device /dev/ttyqd
> Speed 9600
> Loglevel 3
> Route AA6QN-* 44.8.0.32 d
>
> As before, I get a connect at the ax25ipd application but the Tnos
> machine, at the other end of the pipe, does not see the answers.
>
> Sorry for the long email,
> Seasons Greetings, 73, John
