Greetings;
On Mon, 2014-01-27 at 15:49 -0800, K7VE - John spake:
Just my <$0.02>
If the BGP is in a 'hardened' data center then
its probability of going
down is greatly reduced over the random tunnel server running on a 20 year
old computer in somebody's basement.
This isn't a single tunnel going to a single tunnel, our current design
is that each point on the 44/8 network is a direct point to point route.
The fastest route from here to there is a direct line, no matter where
on 44/8 I go since I'm using a tunnel.
We have already suffered (key word!) outages because of BGP or the like
based issues where areas have suffered from various reasonings (router
gone bad, route fat-fingered, etc). In the commercial world this works
very well but we keep insisting we're a glorified ISP here and we're
servicing commercial based IP sites.
While I agree, any new piece of hardware in a "hardened" data
center/NOC/etc would be a great place to house something, I'm extremely
confused as to how BGP will fix/reboot/replace that old PC in someone's
basement that's gone down. Will someone -=please=- explain this to me?
Now if the issue is an old gateway that's servicing a larger block
running some of the high speed wifi, then it's already a flaw of those
creating this network by allowing inferior equipment to host their
network rather than creating a gateway at a "hardened" data center...
not the fault of a tunnel.
BGP'ed regional networks provide more portals into
the larger Internet and
can support smaller networks via VPN and Tunnels.
My upstream already supplies BGP routes for me. If ABC internet becomes
my 44-net "portal", and the path to them from my ISP goes from new
england to virginia (mae east) and back up again, that's only adding a
multitude of points of failure for me, where as my tunnel is more
direct. [don't be surprised, a lot of that happens in this part of the
country - mainly politically motivated for business competition]
IMHO our current tunnelled system with RIP is the best system we've had
in the 20ish years I've been with the amprnet.
--
73 de Brian Rogers - N1URO
email: <n1uro(a)n1uro.ampr.org>
Web:
http://www.n1uro.net/
Ampr1:
http://n1uro.ampr.org/
Ampr2:
http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, Pennsylvania,
Rhode Island, and Vermont.