Jerome, for what it is worth, here is an excerpt from a rip.log file recorded earlier today pointing to each of your three 44 gateways<div><br></div><div><div>Sat Nov 10 17:05:00 2012 - Proxy rip pointing to [24.84.213.209]</div>
<div>Sat Nov 10 17:05:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:05:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:10:00 2012 - Proxy rip pointing to [24.84.213.209]</div>
<div>Sat Nov 10 17:10:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:10:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:15:00 2012 - Proxy rip pointing to [24.84.213.209]</div>
<div>Sat Nov 10 17:15:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:15:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:20:00 2012 - Proxy rip pointing to [24.84.213.209]</div>
<div>Sat Nov 10 17:20:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div>Sat Nov 10 17:20:00 2012 - Proxy rip pointing to [24.84.213.209]</div><div><br></div><br><div class="gmail_quote">On Sat, Nov 10, 2012 at 4:32 PM, jerome schatten <span dir="ltr"><<a href="mailto:romers@shaw.ca" target="_blank">romers@shaw.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Don...<br>
<br>
Yep... it's the F9 screen I've been watching. 0311 on encap certainly<br>
increases the detail, but at any level, there just ain't no RIP packets.<br>
It behaves exactly as if rip has not started, but it has as near as I<br>
can tell. How can you tell? rip staus returns the same thing (all zeros)<br>
even after 'stop rip'.<br>
<span class="HOEnZb"><font color="#888888">j.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Sat, 2012-11-10 at 17:48 -0500, Don Moore wrote:<br>
> I should mention that <ctrl> c will stop the trace activity in lunux.<br>
><br>
> On Sat, Nov 10, 2012 at 5:46 PM, Don Moore <<a href="mailto:ve3zda@gmail.com">ve3zda@gmail.com</a>> wrote:<br>
> If you are watching the trace within jnos you should see that<br>
> activity on the F9 screen. Also try using trace 0311 for more<br>
> detail.<br>
> Or from linux try this command and watch the activity..<br>
> tcpdump -n -i tun0<br>
><br>
><br>
> On Sat, Nov 10, 2012 at 5:22 PM, jerome schatten<br>
> <<a href="mailto:romers@shaw.ca">romers@shaw.ca</a>> wrote:<br>
> On Sat, 2012-11-10 at 15:31 -0600, Maiko Langelaar<br>
> wrote:<br>
> > Is your JNOS doing the encap or your linux ?<br>
><br>
><br>
> JNOS<br>
><br>
> > Are is your JNOS running on a linux box behind a<br>
> firewall ?<br>
><br>
><br>
> Nope<br>
><br>
> ><br>
> > IF you are a *registered* gateway, then you should<br>
> be seeing<br>
> > some type of RIP packets to both your 44 and your<br>
> commercial<br>
> > side IP address.<br>
><br>
><br>
> As far as I can tell, I am a registered gateway:<br>
> Details of gatewayTitle<br>
> Gateway IP <a href="tel:24.84.213.209" value="+12484213209">24.84.213.209</a><br>
> Subnet <a href="tel:44.135.160.32" value="+14413516032">44.135.160.32</a> / 32<br>
> Subnet <a href="tel:44.135.160.40" value="+14413516040">44.135.160.40</a> / 32<br>
> Subnet 44.135.172.130 / 32<br>
> Notes<br>
> Gateway Area: Vancouver,BC,Canada<br>
><br>
><br>
> > There's a hint, run a trace on your encap<br>
> > or your tun0 (to file), see if the RIPS are showing<br>
> there.<br>
><br>
><br>
> How to do this? Can I simply pipe the output in<br>
> autoexec.nos? trace tun0<br>
> 0111 > /path/filename ?<br>
><br>
> I've got trace tun0 0111 engaged and have been<br>
> watching it -- nada RIPs;<br>
> I see nothing but conventional activity.<br>
><br>
> jerome<br>
><br>
><br>
><br>
><br>
><br>
><br>
> > > Where to go from here?<br>
> ><br>
> > This makes me want to create a command that I can<br>
> get the sysop<br>
> > to run which will generates a map of how a system is<br>
> setup. Many<br>
> > times it's hard to diagnose something when you don't<br>
> even know<br>
> > how the JNOS is configured (physical network layout<br>
> included).<br>
><br>
><br>
> Good Idea!<br>
><br>
> Best,<br>
> jerome<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > nos-bbs mailing list<br>
> > <a href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</a><br>
> ><br>
> <a href="https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> nos-bbs mailing list<br>
> <a href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</a><br>
> <a href="https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> nos-bbs mailing list<br>
> <a href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</a><br>
> <a href="https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</a><br>
<br>
<br>
<br>
_______________________________________________<br>
nos-bbs mailing list<br>
<a href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</a><br>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</a><br>
</div></div></blockquote></div><br></div>