On Mon, Aug 5, 2013 at 6:26 PM, Marc, LX1DUC <lx1duc(a)rlx.lu> wrote:
- the route 44.0.0.0/8 via tunl0 should always point
to the UCSD router,
e.g. "ip route add 44/8 dev tunl0 via 169.228.66.251 onlink table 44
I've seen this claim several times, but I don't understand why exactly
such a route would be necessary. Could you elaborate a bit?
While running a rip44 setup, you're going to get all routes updated
within an hour of any changes. As Brian described, that's going to
happen quite precisely at the same time when the UCSD router loads the
updated routes:
"However, the updated routing table is only loaded at the top of the
hour so there is a delay of up to 1 hour before your change will be
reflected in the amprgw router and the rip44 data."
In the old days, when you manually updated your routes every month or
so, having a fallback /8 route back to UCSD might have helped you to
have a path to newly added gateways in the mean time. But these days,
with RIP44 or other relatively quick updates, I think it's just a
recipe for potential routing loops.
- Hessu, OH7LZB