11 Apr
2014
11 Apr
'14
5:56 a.m.
On 11/04/2014 00:18, Bart Kus wrote:
I suspect the router does indeed speak BGP and OSPF
and RIP, it's just
probably not powerful enough to store the entire Internet routing
table. Luckily, to solve this problem, it doesn't need to! UCSD IT can
feed that router with an extremely partial BGP feed. This feed would
only contain 44.0.0.0/8 Internet BGP-announced routes. We have such a
feed right now on our Seattle edge router for HamWAN. Here is the
entirety of the 44net routing table on the Internet:
Alot of gear at UCSD probably doesn't do anything else than static
routing. You also need to consider that such routers will require
maintenance. The process may crash, hang or whatever (read
https://labs.ripe.net/Members/erik/ripe-ncc-and-duke-university-bgp-experim…)
and will need to be monitored, eventually upgrades will need to be
applied etc. Who will pay for the time spent?
73 de Marc