S56WMN to Brian
Dear Sir;
I'm writing to you since you are listed in the ARIN database as the
contact person for 44.0.0.0/8 network. I am one of the Slovenian AMPR
system administrators.
I would like to ask you if it would be possible to arrange with you that
our local internet uplink provider [arnes.si] would advertise the
44.150.0.0/16 prefix so we would actually get our internet traffic.
Sincerely yours,
Metod Novak, S56WMN
Brian to S56wmn
> I would like to ask you if it would be possible to arrange with you that
> our local internet uplink provider [arnes.si] would advertise the
> 44.150.0.0/16 prefix so we would actually get our internet traffic.
I'm sorry, that is not possible. The 44 network is disjoint but
advertised as a whole, with a single gateway and connecting tunnels.
Each section of the network is joined to the whole using IP-IP
tunneling.
More information can be found at
http://www.ampr-gateways.org/
http://www.fuller.net/Gateways/index.html
ftp://ftp.fuller.net/hamradio/gateways/newgate.txt
Mailing list
gateways@cows.net
Best wishes.
- Brian
S56WMN to Brian
> I'm sorry, that is not possible. The 44 network is disjoint but
> advertised as a whole, with a single gateway and connecting tunnels.
> Each section of the network is joined to the whole using IP-IP
> tunneling.
I already have read the FAQs regarding AMPR gateways. The problem is:
currently our backbone [http://lea.hamradio.si/~s53m/map/index.html]
runs at 1.2Mbps (per link). We will be upgrading it to 11, 22 and 33Mbps
next year. Besides, the average hop count from my computer to your
server is more than 30. Since we generate quite some local traffic it
would be rather 'expensive' to route it practically arround the world.
That's why we've been trying to come up with a solution and I think
there would be no _technical_ problems if we implemented my idea -
internet routers do have to match the most speciffic prefix first - so
the functionality regarding 44.0.0.0/8 traffic would be the same while
at the same time providing us with far more flexible and reasonable
routing, smaller packets and no need for a tunnel setup.
Regards,
Metod Novak, S56WMN
Brian to S56wmn
If the reason for AMPRNet were to provide free chunks of address
space that would become standalone subnets connected to the backbone,
what you propose to do would be reasonable.
Or you could just get a block of addresses from an ISP and do
the same thing. Some ham groups have done so, not many.
However, I am still of the opinion that the purpose of the 44/8
allocation to AMPRNet is what it was when I took over management
of it - the project is to build a internally-connected worldwide
network using amateur radio.
Rather than building a spiffy metropolitan lan, which could use any
convenient chunk of address space, we're building a world-wide
network that spans the globe, just like other traditional ham radio modes.
As a single whole network with contiguous address space, 44/8 is
irreplaceable. Once it gets carved up in a manner that is visible
exterior to the network, we will NEVER be able to get its like again.
I have no objection to non-advertised local shortcut routes, but I
feel it is extremely important for 44/8 to appear monolithic to the
rest of the internet, and that means no subnet advertisements.
- Brian
S56WMN to Brian
I quite agree with your viewpoint (that's why I don't like the idea of
getting a provider aggregated IP block) ... but my idea isn't about
"carving up" the 44.0.0.0 network; it still retains its "black box"
status as far as the rest of the world is concerned - it just gets
another internet uplink with statically set up routes that can be torn
down in a matter of seconds if necessary. (AMPR wouldn't happen to have
an ASN?) Then it's up to the route metrics to make sure as much traffic
goes over the air as possible (eg. to every reachable european node).
Kind regards,
Metod Novak
PS: It's not a "metropolitan network". It has an extensive country-wide
coverage with many access nodes.
NO REPLY
Stvari raje ne bom komentiral