[nos-bbs] RIP

[kd6oat]

Using a more verbose setting of tcpdump it appears that data is being sent
(hence the length:504 in the packets below). So it would seem that
something is preventing the data portion of the packet from getting
through. Getting warmer.

On Fri, Mar 30, 2012 at 10:28 PM, kd6oat <kd6oat at gmail.com> wrote:

> Typical activity using 'tcpdump -n -i tun0' (timestamp deleted)
>
> IP 169.228.66.251.520 > 192.168.4.120.58537: RIPv2, Response, length: 504
> IP 192.168.4.120 > 169.228.66.251: 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:
>>
>>> Ken,
>>>
>>>
>>>  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 224.0.0.9
>>>  rip ttl 43200
>>>  start rip
>>>  rip accept 44.0.0.1
>>>
>>> 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.
>>>
>>>
>>> Maiko
>>>
>>>
>>> ______________________________**_________________
>>> nos-bbs mailing list
>>> nos-bbs at tapr.org
>>> https://www.tapr.org/cgi-bin/**mailman/listinfo/nos-bbs<https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20120331/efce9e81/attachment.html>