<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Might as well chime in, it's been over a day and a half, heard
nothing (on list) ...</p>
<br>
<blockquote type="cite"
cite="mid:E123100F-0F15-45EB-909E-7D5A2E4AFDD4@aa6ax.us">
<div class=""><b class=""><br>
SCENARIO #1 an AX25 client connecting via JNOS</b></div>
<div class=""><br class="">
</div>
<div class="">Can JNOS “publish” an AX25 service that other apps
on the computer could connect to and use?<br>
Just a service available on a unix port would be perfect.<br>
<br>
</div>
</blockquote>
<br>
I've thought of a handshake system where apps could negotiate with
JNOS to auto configure<br>
available AX25 ports, but never got to it, not sure if that even
exists with any ham radio software,<br>
and if so, what RFC (or standard) is in use for universality ?<br>
<br>
In the literal context, I would say no. We only have ax25 over ip,
ax25 over udp, which<br>
requires manual setup on both ends. It would be nice to see what
others say on this.<br>
<blockquote type="cite"
cite="mid:E123100F-0F15-45EB-909E-7D5A2E4AFDD4@aa6ax.us">
<div class=""><br>
This would let JNOS control the TNC and not have to share<br>
<br>
</div>
</blockquote>
<p>Understood.</p>
<blockquote type="cite"
cite="mid:E123100F-0F15-45EB-909E-7D5A2E4AFDD4@aa6ax.us">
<div class=""><br>
a third-party app to connect to JNOS to get to and from the
radio. So I could use Pat or Outpost and just<br>
configure that app to know where to find the AX25 interface.<br>
<br>
</div>
</blockquote>
That almost implies Pat or Outpost has a means of asking for an ax25
interface. Can you give<br>
specifics on how it does this ?<br>
<br>
<blockquote type="cite"
cite="mid:E123100F-0F15-45EB-909E-7D5A2E4AFDD4@aa6ax.us"><br>
<div class=""><b class="">SCENARIO #2 write a WINLINK client that
uses JNOS</b></div>
<div class=""><br class="">
</div>
<div class="">I know I could write Python scripts to connect to
JNOS, authenticate and send/receive WINLINK protocol. My current
Python scripts do that in a sense, as they connect to JNOS on
192.168.2.2 and then use JNOS to connect to a remote BBS and
send and receive mail. My system does this dozens of times every
day. Writing a WINLINK client in Python would take me a few
days, but I wonder what other people think of this approach. (I
have already tested connecting to 192.168.2.2 JNOS and then
issuing commands to talk to a WINLINK station and issue
commands, and all of that works just fine.)<br>
<br>
</div>
</blockquote>
<p>You do realize JNOS has a Winlink (CMS Service) Client already
and supports multiple 'accounts' ?</p>
<p>What is it in Python you need JNOS to do then ?</p>
<p>Maiko / VE4KLM<br>
<br>
<br>
</p>
</body>
</html>