On 6/17/13 2:04 AM, kb9mwr@gmail.com wrote:
Many gateway opperators only allow inbound 44-net IP addresses.
Maintain a local route table alleviates bandwith issues at ucsd, and the single point of failure.
Thanks, this is good info. I think I can change the "munge" script to generate a working 44/net config. Cisco/etc is going to need a tunnel interface for each destination, but I think it will work. Perhaps a template interface might be the best way.
I'll post my results back here.
I'd ask, why only one gateway to 44/8? Why not setup some tunnel/peering points globally?
Bryan, here the modified rip44d script (of course anyone can try it...). Running on my system for almost 1 year now.
http://www.yo2loj.ro/hamprojects/rip44d2.zip
73s de Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Bryan Fields Sent: Monday, June 17, 2013 15:58 To: AMPRNet working group Subject: Re: [44net] Cisco/juniper configs?
(Please trim inclusions from previous messages) _______________________________________________ On 6/17/13 2:04 AM, kb9mwr@gmail.com wrote:
Many gateway opperators only allow inbound 44-net IP addresses.
Maintain a local route table alleviates bandwith issues at ucsd, and the single point of failure.
Thanks, this is good info. I think I can change the "munge" script to generate a working 44/net config. Cisco/etc is going to need a tunnel interface for each destination, but I think it will work. Perhaps a template interface might be the best way.
I'll post my results back here.
I'd ask, why only one gateway to 44/8? Why not setup some tunnel/peering points globally?
-- Bryan Fields
727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
-
Bryan Fields -
Marius Petrescu