<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Correct… I was trying to find a method of getting encap.txt capability for a friend by testing it on my system- sorry for the confusion. Are you saying I must first kill rip on my system to do that?<div>J<br id="lineBreakAtBeginningOfSignature"><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Jan 8, 2025, at 18:32, Lee D Bengston <kilo5dat@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Please correct me if I am wrong, but the way I'm interpreting this is that JNOS is running RIP so that there is no need for ampr-ripd. That would explain why there's no directory and file as described.</div><div><br></div><div>73,</div><div>Lee<br></div><div><br></div><div><br></div><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Jan 8, 2025 at 8:26 PM jerome schatten <<a href="mailto:romers@shaw.ca">romers@shaw.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Bob I made the directory as you suggested and then rebooted jnos. After ‘route’ showed the entire list, I looked in ‘ampr-ripd’ and it was still empty. So obviously I failed to understand you properly. <br>
n<br>
Sent from my iPhone<br>
<br>
> On Jan 8, 2025, at 17:21, Boudewijn (Bob) Tenty <<a href="mailto:bob@tenty.ca" target="_blank">bob@tenty.ca</a>> wrote:<br>
> <br>
> Jerome,<br>
> <br>
> I don't know what version of ampr-ripd you are using but I vaguely remember that older versions didn't create the ampr-ripd directory automatically in /var/lib/ ,<br>
> so in that case you always can create it manually and restart the daemon afterwards.<br>
> <br>
> Bob VE3TOK<br>
> <br>
> can always create it manually.<br>
> <br>
> On 1/8/25 19:50, jerome schatten wrote:<br>
> > Bob…. I don’t seem to have a<br>
> > ‘ampr-ripd ’ directory anywhere on my jnos machine.<br>
> > j<br>
> > Sent from my iPhone<br>
> ><br>
> >> On Jan 8, 2025, at 13:37, Boudewijn (Bob) Tenty <<a href="mailto:bob@tenty.ca" target="_blank">bob@tenty.ca</a>> wrote:<br>
> >><br>
> >> Jerome,<br>
> >><br>
> >> The ampr-ripd daemon running in Linux stores the encap.txt in the /var/lib/ampr-ripd/ sub-directory.<br>
> >> It is in the format what directly can be read by jnos. He is better off of course downloading if from the wiki<br>
> >> a couple of times a day with a crontab entry and converting it from the json format to the jnos format.<br>
> >><br>
> >> Boudewijn (Bob) VE3TOK<br>
> >><br>
> >> On 1/8/25 14:38, jerome schatten wrote:<br>
> >>> Many long year ago, around the year of the flood, one used to be able to go to the portal and download the latest encap.txt file, or sign up to have it e-mailed. Grousing around the new ‘improved' portal, that feature seems to no longer be available. Is this the case, or is it just that I can’t find it? There are folks that need that service as they can’t receive the rip broadcasts.<br>
> >>><br>
> >>> I’m not bothered by this as I receive the broadcasts just fine, but one of my forwarding partners is not able to receive the broadcasts and that makes his jnos system somewhat useless these days.<br>
> >>><br>
> >>> It appears to me that the rip stuff is not a file on my system, but rather resident in memory after receiving the broadcasts. Can I force the dumping of the rip info on my system to a file that can be sourced by my unfortunate friend?<br>
> >>><br>
> >>> He has had this problem across the years, and many different modems, and even across different isp’s.<br>
> >>><br>
> >>> We could use some advice….<br>
> >>><br>
> >>><br>
> >>> jerome<br>
> >>> _______________________________________________<br>
> >>> nos-bbs mailing list<br>
> >>> <a href="mailto:nos-bbs@lists.tapr.org" target="_blank">nos-bbs@lists.tapr.org</a><br>
> >>> <a href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a><br>
> >> --<br>
> >> There is nothing permanent except change<br>
> >> -Heraclitus<br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> nos-bbs mailing list<br>
> >> <a href="mailto:nos-bbs@lists.tapr.org" target="_blank">nos-bbs@lists.tapr.org</a><br>
> >> <a href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a><br>
> > _______________________________________________<br>
> > nos-bbs mailing list<br>
> > <a href="mailto:nos-bbs@lists.tapr.org" target="_blank">nos-bbs@lists.tapr.org</a><br>
> > <a href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a><br>
> <br>
> --<br>
> There is nothing permanent except change<br>
> <br>
> -Heraclitus<br>
> <br>
> <br>
> _______________________________________________<br>
> nos-bbs mailing list<br>
> <a href="mailto:nos-bbs@lists.tapr.org" target="_blank">nos-bbs@lists.tapr.org</a><br>
> <a href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a><br>
_______________________________________________<br>
nos-bbs mailing list<br>
<a href="mailto:nos-bbs@lists.tapr.org" target="_blank">nos-bbs@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a><br>
</blockquote></div></div>
</div></blockquote></div></body></html>