On Sun, 4 Jul 1999, John Ackermann wrote:
> I discovered something in trying to configure a simple axip gateway
> setup that I'd like help with.
>
> Here is the scenario:
>
> Station A is configured to run with the callsign K8MK-3 on the VHF
> port, and K8MK-14 on the AXIP link. It has a single AXIP route, to
> W8APR at xxx.xxx.xxx.xxx.
>
> W8APR has a similar configuration, with an AXIP route to K8MK at
> xxx.xxx.xxx.xxx.
>
> Either station can use the call command ("call axip W8APR) to initiate
> a connect to the other, and will get the other station's node prompt.
> And, if K8MK-0 connects to the K8MK-3 node and then does a "c axip
> W8APR" command, he will get connected to the node at W8APR.
>
> However, if a user with another callsign logs in to the node and issues
> the same command, it will fail. For example, if N8UR connects to
> K8MK-3 and then issues "c axip W8APR" from the node prompt, K8MK-3 will
> attempt the connection, but W8APR will not respond.
>
> The listen command shows that K8MK uses the node user's callsign, not
> its own, as the source call in this case. So, the connect request goes
> out over the axip link with a source address of N8UR and W8APR doesn't
> respond, since its config file doesn't include N8UR but only K8MK.
>
> So, the question is this -- is there any way to configure things so
> that any user can connect to the node, and then issue a connect via
> axip to the remote node, regardless of that user's callsign?
John,
I had a terrible time figuring the Linux axip. It is somewhat explained
in the file located in your ax25-utils source tree as:
ax25-utils-2.1.42a/ax25ipd/README.ax25ipd
I first scanned this file, and didn't see anything particular, until I read
it again. There is so much mumbo-jumbo in the Overview section, but pay
particular attention to the last paragraph of the Overview section, and the
next section, Modes and Routing. Read and read again the second paragraph
and see if there is anyway this scenario is applicable to your system.
The symptom you describe seems to indicate this.
On your last question, perhaps you need an explicit route or a user
permission. Who knows, I played with this a lot, and as long as the axip
link was the "destination" it seemed to work. I'm wondering if there is a
need for more than one axip port as we are familiar with in Jnos. That is,
one port for each axip destination... I flunked it. Jnos works too well
in this area to change to something that makes me laugh, or cuss!
> Thanks!
>
> 73,
> John N8UR
> [EMAIL PROTECTED]
>
--
73, Ronnie.
[EMAIL PROTECTED]
