27 Mar
2013
27 Mar
'13
10:10 p.m.
Marc,
I do not suggest removing the 169.228.66.251 route. It was discussed a
few weeks ago that removing the route on my standard Ubuntu machine
causes RIP44 to fail (no longer receive RIP44 announcements). No
resolution was reached in that discussion. ONE of the following routes
must be manually added before RIP44 is operational:
ip route add default dev tunl0 via 169.228.66.251 onlink table 44
If you do not wish to have your subnet accessible from the Public
Internet., use the following instead:
ip route add 44.0.0.1 dev tunl0 via 169.228.66.251 onlink table 44
window 840
Further, 44.0.0.1 via 169.228.66.251 IS indeed a valid allocation on
AMPR, it happens to be the Main AMPRGW.
- Lynwood
KB3VWG
On 03/27/2013 10:40 AM, marius(a)yo2loj.ro wrote:
I simply add 169.228.66.251 to the hosts to be ignored (option -a
169.228.66.251 ) so that route doesn't make it into the machine...