27 Aug
2013
27 Aug
'13
1:23 a.m.
The default route to 169.228.66.251 is in most munge scripts I have seen.
The motivation was that you are reachable in that way if a new gateway
pops up and you don't refresh your ipip routes at a regular basis.
73,
VE3TOK
On 13-08-26 04:27 AM, Demetre SV1UY wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Brian,
My munge script adds a route command to 169.228.66.251 as a last line.
It does not look right to me but if you say it does not matter then it
is OK by me.
Is everyone else using a munge script? if yes could someone publish it
here so that I can compare it with the one I use! Maybe I use an
outdated one here.
73 de SV1UY
On Sun, Aug 25, 2013 at 2:33 PM, Brian Kantor <Brian(a)ucsd.edu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Destination Gateway Genmask
Flags Metric Ref Use Iface
44.0.0.0 169.228.66.251 255.0.0.0 UG 0 0 0 tunl0
I
think you probably shouldn't have this route as amprgw (169.228.66.251) isn't
really
a default route for the rest of AMPRNet -- there isn't one. AMPRNet is fully
routed by the entries in the encap table and any subnet which isn't in the table
is by definition not reachable. But I don't think it'll do any harm.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html