kd6oat at gmail.com
Sat Mar 31 00:28:12 EDT 2012
Typical activity using 'tcpdump -n -i tun0' (timestamp deleted)
IP 126.96.36.199.520 > 192.168.4.120.58537: RIPv2, Response, length: 504
IP 192.168.4.120 > 188.8.131.52: ICMP 192.168.4.120 udp port 58537
unreachable, length 36
On Fri, Mar 30, 2012 at 9:50 PM, kd6oat <kd6oat at gmail.com> wrote:
> Right. The autoexec.nos is configured correctly. Nothing has changed since
> I compiled RIP and RIPAMPRGW into config.h last year. And I double checked
> to make sure the current config.h file complied with the whitepages was
> correct. It appears that the RIP functions in jnos are working fine. I'm
> just not receiving the broadcasts. Nothing being added to rip.log.
> On Fri, Mar 30, 2012 at 9:19 PM, Maiko Langelaar <maiko at pcs.mb.ca> wrote:
>> In the opposite direction however (my jnos back to ucsd), the protocol
>>> shows ICMP and Destination unreachable (Port unreachable).
>> That's normal, the AMPRnet system does not expect or care for a response,
>> like I said all you need to do is receive the information. You should have
>> the following (all lines) configured in your JNOS 2.0 autoexec.nos :
>> ip upstairs 184.108.40.206
>> rip ttl 43200
>> start rip
>> rip accept 220.127.116.11
>> IF you are missing the new 'ip upstairs' command above, JNOS will NOT
>> recognize the RIP broadcasts, make sure the above commands ALL exist.
>> and that something is blocking my return packets. I'm getting warm (I
>>> think). Still open to suggestions.
>> Nope, the return packets (if any) are not required. You just need to
>> receive the information which gets propogated into the route tables.
>> nos-bbs mailing list
>> nos-bbs at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nos-bbs