16 Jun
2015
16 Jun
'15
11:09 a.m.
I'm on a plane, sorry for the top post.
Brian, how much traffic does the current AMPRnet gw handle peak?
Would it be possible to aggregate some of these routes selectivily or have some people
volunteer to move ip? In the greater scheme of things 350 prefixes is not huge.
My concern would be on the routing db and filter side. But this could be automated via
rpsl.
On June 16, 2015 12:00:09 PM EDT, Brian Kantor <Brian(a)ucsd.edu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Tue, Jun 16, 2015 at 07:09:45AM -0700, Cory (NQ1E) wrote:
--
Bryan Fields
727-409-1194
http://bryanfields.net
Do we have a rough idea on how many /24s that
would amount to?
After summarizing the smaller routes at the /24 level, the number of
subnet routes that would have to be advertised is about 350. If we
summarize at the /16 level, there would have to be about 12.
We *know* that most of the approx 475 gateways in the database are no
longer active. These are still contributing to this total.
Despite multiple requests by Chris, so far no one with PHP programming
experience has stepped forward to help write the program that is
necessary
to clear them out. I would wager that the number of subnet routes
necessary would drop precipitously if we were to eliminate the inactive
gateways.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net