16 Jul
2013
16 Jul
'13
7:37 p.m.
Makes it a lot easier when you and your upstream are both Amateurs..
We get our biggest drama from the USA carriers, as they demand written
approval
We have been luck so far with the response from Brian - but have been warned
they should be signed and on a letter head...
----- Original Message -----
From: "Antonio Querubin" <tony(a)lavanauts.org>
To: <lholcomb(a)clearqualitygroup.com>om>; "AMPRNet working group"
<44net(a)hamradio.ucsd.edu>
Sent: Tuesday, July 16, 2013 8:21 AM
Subject: Re: [44net] Re Networks in OZ
(Please trim inclusions from previous messages)
_______________________________________________
On Mon, 15 Jul 2013, Lin Holcomb wrote:
We are not really planing on doing both inside
the same IP ranges in
Georgia(US) the north Atlanta LAN will still be on 44.36 and the BGP
space
will be on 44.37 per Brian. (As soon as our ISP completes its upstream
provider switch.) mooching hobby type stuff comes last on The list of
things to do for them. We can add the functionality I guess, but
wouldn't
it just be better for the routing directly to these addresses instead of
going in and out and sideway.
Of course it is but not everyone can convince their upstream to route
their net-44 prefixes in their route tables and announce them via BGP. If
that were easy, we wouldn't have the encap table we have today.
Antonio Querubin
e-mail: tony(a)lavanauts.org
xmpp: antonioquerubin(a)gmail.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html