Wow!

Nice and elegant solution !!

I did it that way, it works !

route lookup shows now correct despicte amprgw sets wider route.

Thanks!!!

73, lu7abf, Pedro

On Mon, May 19, 2014 at 3:26 AM, Steve Fraser sfraser@sky.apana.org.au wrote:

...

Hi Pedro

(oops, typo)

I think if you have two static routes that are smaller (more specific) than the amprgw route (e.g. /24) then they should take priority over the /23 amprgw route.

So add routes to 44.153.0.0/24 and 44.153.1.0/24 , to your default.

regards

Steve, vk5asf

On 19/05/14 15:16, Pedro Converso wrote:

...

(Please trim inclusions from previous messages) _______________________________________________ Hello fellow crew aboard this 44 ship,

I receive ok every 5 min update routes from amprgw in my jnos2 using rip2.

Along with all gateways my own gateway is included affecting my local route that should be pointing to my default route, not to my gw internet IP.

Question is: how I can avoid receive/load my own gateway entry ? or else how I can drop this entry coming from amprgw from my route table ? or how to make a permanent route that is not overlaid ?

I tried with an at command: at 15 "route drop 44.153.0.0/23 encap+" but in less than 5 minutes the route is again overlaid with my gw entry from amprgw.

Appreciate any suggestion/advice, Tks in advance lu7abf, Pedro Converso

73, lu7abf, Pedro _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net