[nos-bbs] Further development

[Maiko Langelaar (Personal)]

Thanks Gus,

Yes I agree, i have not looked at it for EONS :(

Charles actually sent me a link to some recent discussions on this very
topics of INP, sounds like Paula (of Xrouter fame) and others have been
talking about this in great depth, and the notes they provided will most
certainly be useful in 'fixing' ? the current implementation I have going.

Just when I was happy with releasing this, this very morning my AT code
started giving me that damn 'loop problem', which I have not seen since
some time in 2021, I suspect it happens when AT sources a *.nos file
that has any line entry greater then 80 bytes, but I am not 100%, so
testing that theory now. Also the ax25 load | save stuff is still giving
me some challenges as far as correct time stamps, but at least the
heard lists are kept going ...

What was really cool was picking up 1 (just 1) robust packet frame
from Southern Chile on 10 meters last month, direct to Winnipeg :

  Thu Apr 25 13:06:28 2024 - scsptc recv:
  KISS: Port 0 Data
  AX25: 6W7RV-10->APTSCS v RPN1-1 UI pid=Text
  0000  00 82 a0 a8 a6 86 a6 e0 6c ae 6e a4 ac 40 74 a4  .. (&.&`l.n$, at t$
  0010  a0 9c 62 40 40 63 03 f0 2f 31 38 30 32 33 30 68 .b@@c.p/180230h
  0020  2f 62 79 22 3e 3c 22 32 3f 52 3f 6d 57 4f 6e 20 /by"><"2?R?mWOn
  0030  74 68 65 20 72 6f 61 64 20 61 67 61 69 6e 2e 20  the road again.
  0040  37 33                                            73

How cool is that, as another ham put it, 'good catch', yup :]

Maiko

On 5/9/24 07:58, Gustavo Ponza wrote:
> Hi Maiko et al,
>
> at first, very TNX for all!
>
> Suggest, as further development of JNOS2, a completion of INP3
> feature and, possibly, to fit the FlexNet protocol, too :)
>
> Netrom in general as of today is a new Babylon specially, as I can
> understand, with the introduction of hundreds of, *worst manned*,
> emerging nodes, which generate about 800 of false/dead unreachable
> targets... the aim should be that to protect the JNOS2 :)
>
> TNX!
>