20 Apr
2014
20 Apr
'14
8:33 p.m.
Since this keeps coming up, I've added a section to the wiki
explaining (or at least attempting to) ISP Ingress filtering, or why
you can't just route your AMPRNet allocation yourself.
http://wiki.ampr.org/index.php/Why_can%27t_I_just_route_my_AMPRNet_allocati…
-Neil
On Sun, Apr 20, 2014 at 6:55 PM, Javier Henderson (javier)
<javier(a)cisco.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Apr 20, 2014, at 5:22 PM, Steve Wright <stevewrightnz(a)gmail.com> wrote:
--
Neil Johnson
http://erudicon.com
Would the people who ACTUALLY HAVE a properly
connected (live to the
internet) 44 subnet that they openly brag about, kindly document the bloody
thing in the wiki so I can do it as well?
I added my 44net /24 to the list of prefixes I announce. Then I told my upstreams about
it so they could update their filters.
This isn't a dick measuring
group, its a networking group. You know what you're doing, so write it up
so mere mortals can achieve a positive result as well.
There needs to be a sample equipment list with DIY workarounds for those
with time but not money, and there needs to be a VERY well written
document-set to hand to my ISP so I don't scare them into just plain
refusing my request, or unduly taxing their tech team.
Announcing prefixes is an ISP’s bread and butter, they shouldn’t need a very well written
document, just the prefix you want them to announce, and maybe a letter of authorization
(LoA) from Brian Kantor allowing your ISP to do such announcement.
Sample equipment list? “A router that speaks BGP”, but your ISP already has that.
73,
-jav k4jh
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net