[nos-bbs] RIP

[kd6oat]

If nothing else, I'm learning how to use tcpdump...

16:40:00.181198 IP (tos 0x0, ttl 47, id 46452, offset 0, flags [none],
proto UDP (17), length 232)
    169.228.66.251.520 > 192.168.4.120.6188: [udp sum ok]
RIPv2, Response, length: 204, routes: 10
  Simple Text Authentication data: pLaInTeXtpAsSwD
  AFI IPv4,      44.4.2.153/32, tag 0x0004, metric: 1, next-hop:
173.167.109.217
  AFI IPv4,      44.4.2.152/32, tag 0x0004, metric: 1, next-hop:
173.167.109.217
  AFI IPv4,       44.2.50.0/24, tag 0x0004, metric: 1, next-hop:
208.74.106.137
  AFI IPv4,     44.2.14.100/32, tag 0x0004, metric: 1, next-hop: 71.193.6.48
  AFI IPv4,       44.2.14.0/29, tag 0x0004, metric: 1, next-hop: 71.193.6.48
  AFI IPv4,       44.2.11.1/32, tag 0x0004, metric: 1, next-hop:
71.130.72.50
  AFI IPv4,       44.2.10.0/29, tag 0x0004, metric: 1, next-hop:
71.130.72.50
  AFI IPv4,      44.2.8.180/30, tag 0x0004, metric: 1, next-hop:
192.147.172.252
  AFI IPv4,       44.2.1.32/29, tag 0x0004, metric: 1, next-hop:
76.14.161.185

...so now to get data to jnos
On Sat, Mar 31, 2012 at 4:28 PM, kd6oat <kd6oat at gmail.com> wrote:

> 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/c8e85e05/attachment.html>