Fwd: [44Net] gateway updates - HIGHSPEED HAMNET
don at 00100100.net
Tue Mar 23 23:25:58 PDT 2010
It is the next logical progression after they enabled RIP routing on
44net. But it may be overkill right now considering they just turned on
BGP by the way stands for Border Gateway Protocol. It's mainly used
between ISP's and Carrier level internet routers to say "Hi, I'm
Amprnet! You can reach me by these BGP neighbors" As opposed to
RIP/OSPF which goes through and creates huge tables of network subnet
Unless most of these guys are ISP's or have some extra cash laying
around, it's going to cost $$$ to get a public AS number which makes no
sense unless they are a multi-national company hopping between large
geographic areas and networks. They're better off setting up a private
AS number system. Most carrier level ISP's will do private BGP to
colocation/business clients. But having a comcast cable modem at home
probably couldn't get BGP unless it's via a VPN connection. If you
tried, comcast might say your running a server or something that would
violate the ToS.
Bill V WA7NWP wrote:
> Interesting notes...
> I found this for the Highspeed Hamnet... I'm not sure what it says
> but from all the acronyms I think I like it.
> Bill, WA7NWP
> ---------- Forwarded message ----------
> From: Jann Traschewski
> Date: Tue, Mar 23, 2010 at 2:08 PM
> Subject: Re: [44Net] gateway updates
> To: 44Net at cows.net
> Brian wrote:
>>> What would "Proxy BGP" do ?
>> Consider AMPRGW as a "route reflector", but more. Consolidate all
>> the various bits of AMPRNet routing information then announce those
>> consolidated routes to the larger internet so that the equivalent of
>> CIDR routing could be taking place without having dozens of individual
>> subnets announcing their own connectivity in an uncontrollable manner.
>> I'd like to be able to announce that an ampr subnet is reachable via a
>> specific gateway but also via the central gw (at a lower preference).
> I'm not into the ISP business. My friend owns 126.96.36.199/19 on AS13132.
> Would your desired announcements e.g. look like this:
> AS 7377:
> 188.8.131.52/8 BGP-Next-Hop: <IP of your core router @AS7377>
> 184.108.40.206/24 BGP-Next-Hop: <IP of my friends core router @AS13132> ??
> We could give it a try and have a look what will happen as a first step.
> Could this work?
>> There are complications here in that route selection is often based on
>> traversing a chain of Autonomous Systems, and this doesn't quite work
>> right when the chains to be evaluated have multiple instances of the
>> same AS. It looks like a loop or worse.
> Hm, I didn't get this :/
>> We really can't expect every AMPR gw to get its own AS. Nor can we
>> expect to have any sort of influence over each ISP's announcements of
>> routes to pieces of the amprnet via their own AS.
> True. We need another way.
>> I don't know how to do what we want to do.
>> Perhaps there is something we could use in extended communities (RFC4360)?
>> Anyone got any ideas on how to do what we want without having to
>> re-engineer the entire internet or require unobtainable control/access
>> from network providers?
> Currently there is much activity in europe in building the highspeed HAMNET
> on RF using BGP4. I already connected it to the AMPRNet, but it should be
> more decentralized in the future. I'd like to spread my route informations
> in realtime to the other gateways. I didn't have the time to look at
> OpenNHRP, yet. Hopefully we will find a way without the need of much
> Seatcp mailing list
> Seatcp at wetnet.net
More information about the Seatcp