[nos-bbs] RIP

[jerome schatten]

Don is correct; I see the same problem with RIP here plus another that seems to be jnos2.0k related:

From time to time 2.0k stops broadcasting nodes; that is, when nodetimer reaches the point where the broadcast should occur, jnos is mute (does nothing on any interface). It will respond to a poll however. 2.0k also fails to execute a nodes broadcast from the command 'jnos> net bcn (interface)’.  Sometimes it works OK, sometimes not, and sometimes it quits broadcasting nodes after an hour or so of working OK. 

I’m using exactly the same files as I use in 2.0j7 and 2.0j7 works fine.  Config.h is the default for both binaries. I’d be interested in running some tests with someone else that is running 2.0k. Perhaps we can set up an axip link if we don’t have one already and talk on Skype.

73’
jerome - ve7ass
Vancouver

> On Sep 29, 2016, at 12:09, Don Moore <ve3zda at gmail.com> wrote:
> 
> I along with others noticed an interesting phenomenon and are confident that it's unique to version K...
> Shortly after the gateway broadcasts the RIP data the station(s) running K sends data encapping his Internet address instead of his 44 address.  It will remain that way for a while and then recovers until the next broadcast when it repeats the above mentioned process.
> As a result, it's not long before the quality of the axip link to that station begins to drop.  I have one currently whose quality has dropped to 23% and others that too are dropping.
> Of course along with axip, stuff like SMTP etc. Also stop communicating because of the incorrect route.
> 
> Is there a fix for this or do these stations go back to downloading the encap.txt file or using an earlier version of Jnos?
> 
> 73,
> Don - ve3zda
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs