If I recall Brian set up the rip announcements to be less frequent to a host if it has previously returned an unreachable code.

Else if ones public IP changes, it seems like unfriendly ddos traffic from UCSD to now, some non hams IP address.

A lot of the UCSD gw was documented in a flowchart image.  I'd have to look to see if I still have that.



On Thu, May 2, 2024, 2:18 PM Dan Cross via 44net <44net@mailman.ampr.org> wrote:
On Thu, May 2, 2024 at 2:23 PM Barry Bahrami via 44net
<44net@mailman.ampr.org> wrote:
> This is common to prevent flapping interfaces from causing problems with the routing table through constant updates. Although an hour is a bit high. I wonder if there is a typo in the config.  Just a thought

That's reasonable. I wonder how it's implemented? As far as I know,
creation or tear-down of an IPENCAP tunnel does not, by itself,
generate any traffic: an interface could conceivably flap and nothing
on the distant end would notice. I suppose if the interface flaps, an
upstream router could send an ICMP host unreachable message to the
UCSD router for anything being sent through the tunnel regularly? I
could see that triggering some kind of quenching logic, though an
hour-ish timeout seems excessive.

        - Dan C.
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org