15 Feb
2016
15 Feb
'16
6:38 a.m.
Hi,
Le 15/02/2016 11:37, Marius Petrescu a écrit :
The Hamnet uses private 16 (legacy) and 32 bit AS and
is not related
in any way to the world wide BGP announcements so no need to wait for
anything, since we are doing it inside the 44net address space.
Sorry, but I don't understand that. I never used BGP before.
Here's a example. Please correct if I'm misunderstading something :
- Let's assume I'm managing the 44.151.20.0/24 subnet locally in my area
- Let's assume 44.151.20.1 is a web server located in my local
datacenter, in a DMZ : HamNet users with 44.x IPs can access it; but I
want it to be accessible also from Internet
Actually, I'm using an IP-IP tunnel. The actual route from Internet to
44.151.20.1 is via amprgw.sysnet.ucsd.edu, in California.
Then, an user on Internet located just near me, that wants to reach my
web server, has to go to ucsd (via Internet), then back to me (via IP-IP
tunnel). This implies a 350ms latency !!!
The purpose of BGP would be to announce the 44.151.20.0/24 locally from
my datacenter. This would be a world wide BGP announcement, on Internet.
Then, people from Internet needing to reach my web server, would get a
shorter path, without having to transit via California.
Did i miss, or misunderstand something ?
See also:
http://en.wikipedia.org/wiki/Mobile_country_code
on how the ASN are proposed to be used
Sorry, this link is about "mobile country code"...