6 Jan
2015
6 Jan
'15
3:21 a.m.
Subject:
Re: [44net] Tunnel mesh is (mostly) down
From:
Brian Kantor <Brian(a)UCSD.Edu>
Date:
01/05/2015 07:26 PM
To:
AMPRNet working group <44net(a)hamradio.ucsd.edu>
On Mon, Jan 05, 2015 at 02:27:18PM +0200, Marius Petrescu wrote:
Note that those transmissions were sent to a seemingly random destination port
number,
which made them kind of hard to use. The source port number was always 520.
I don't know if that was a bug or a feature, but it puzzled me when I was trying to
receive
them and could not get the encapsulated transmission working in ampr-ripd.
(an issue that I later located and Marius made a change that fixed that)
Rob
>Let me get this right... You are talking
about the encapsulated RIP
>transmissions originating from 169.228.66.251 to each public gateway IP?
>
>-----Original Message-----
>On Behalf Of Rob Janssen
>Sent: Monday, January 05, 2015 11:11
>To: Brian Kantor
>Cc:44net@hamradio.ucsd.edu
>Subject: Re: [44net] Tunnel mesh is (mostly) down
>
>Maybe something else you can do is drop the extra transmission of RIP
>packets from the public IP
>address. I think nobody is really using those (if not because of the funny
>destination port number), and
>they only add to this problem by putting even more data in the queue.
Up until
a few minutes ago, the amprgw system was sending the RIP data
twice - once UNencapsulated to the public gateway IP, once encapsulated.
Since to the best of my knowledge, no one was using the UNencapsulated RIP
for anything, I've discontinued sending it.
If I'm wrong and someone is using it for something, I'll turn it back on.
- Brian