<head>
<title></title>
</head>
<body>
<div class="userStyles" style=" font-family: Arial; font-size: 12pt; color: #000000;">Maiko,<br>
<br>
In the past we had problems with JNOS to BPQ AXUDP netrom disconnecting sometimes from a few minutes to days. It seemed JNOS would initiate a disconnect request maybe based on an inactivity timer but there is no parameter I'm aware of. BPQ would initiate a reconnect but sometimes would take days.<br>
<br>
When BPQ switched to using INP3, there seemed to be a lot more traffic between nodes and I don't see JNOS initiating a disconnect. This workaround is doing well for us. XRouter AXIP using INP3 also stays connected. JNOS to JNOS AXIP is always connected.<br>
<br>
Jerry, N0MR
<footer class="replyforwardcontainer"><br>
<br>
<span>On Sat, 9 Jan 2021 11:49:58 -0600, M Langelaar <maiko@pcsinternet.ca> wrote:</span><br>
<br>
I got asked about a few things, so maybe this will help others ?<br>
<br>
> #undef J2_NETROM_REACHABILITY<br>
<br>
nope, it became very time consuming, then I kinda forgot about it.<br>
<br>
This was a project I wanted to do that would actively got out and<br>
make sure nodes in the netrom table were 'reachable', and if not<br>
they would be removed, kinda like a garbage collection of sorts.<br>
<br>
> #undef INP2011<br>
<br>
this is INP3, yes, still read only, but many have reported stability issues<br>
with it, and it too became very time consuming back then, the documentation<br>
was horrible with regard to the protocol, and I wrote it based on some<br>
linux code<br>
from before that time. I've always meant to go back to it, but ... you<br>
know ...<br>
<br>
It was quite technical, overwhelming to work on, I don't think it was ever a<br>
good implementation (read only just allowed JNOS to mingle with Xnet and<br>
other networks, it never wrote any INP3 back to the system, thank god).<br>
<br>
Feedback from people would be nice. I have received some from a few of<br>
the veterans on here, but just never got to it .. usual excuses ...<br>
<br>
> #define NRR /* NRR (Netrom Route Record) feature */<br>
<br>
Works for some systems (Xnet and JNOS that have it compiled in), examples :<br>
<br>
[JNOS-2.0m.5F-B1FHIM$]<br>
You have 101 messages - 81 new.<br>
(#6) ><br>
nrr ve3mch-8<br>
(#6) ><br>
*** route: VE4KLM-3 VE3MCH-8* VE4KLM-3<br>
<br>
If I telnet to Jack's system and I do the same to my NETROM call (that's<br>
important) :<br>
<br>
Telnet session 1 connected to aa6hf<br>
<br>
JNOS (aa6hf.ampr.org)<br>
<br>
login: ve4klm<br>
Password:<br>
[JNOS-2.0m.5C-B1FHIM$]<br>
><br>
nrr ve4klm<br>
><br>
nrr ve4klm-3<br>
><br>
*** route: AA6HF-4 VE4KLM-3* AA6HF-4<br>
<br>
Maiko / VE4KLM<br>
<br>
<br>
<br>
_______________________________________________<br>
nos-bbs mailing list<br>
nos-bbs@lists.tapr.org<br>
http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org<br>
</footer>
</div>
</body>