my thought is we need more people working on finishing the portal first.
What exactly is that going to DO?
Here I am sitting on my hands trying to figure out how to get my (already allocated MONTHS AGO) /24 connected to the flamin internet. No one seems focussed on making a wiki entry about THAT. Rather, they'd be happier tunneling their little private network to someone elses'. It seems that many other groups have been waiting YEARS for this assistance or documentation, and MANY other groups who have just given up in disgust.
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? 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.
Thank you.
Though I have yet to get my /24 directly connected, the procedure seems well documented in the TOS found here:
Basicly, do this:
find one or more AS willing to announce your block via BGP and route it to you. Execute the agreement as outlined in the TOS. Anyone who already has an AS running BGP on the internet ought easily understand what is being asked for in the TOS. basicly, you are bringing address space with you. It's kinda the internet version of porting your phone number. If you're looking for an exact list of what to buy to set this up you are not going to find one because that list will vary with tour exact setup. What you will find, again in the TOS is an outline of what that hardware must do. It either needs to at present set up a tunnel mesh or it needs to speak BGP and exactly what equipment speaks BGP is between you and your service provider as it may end up that especially if you're not multihomed they may very well just drop you a point to point link that is your /24 that you can then subnet at will on your end of the link. First things first, find a service provider willing to take you on and talk to them about it. much easier than futzing with all the tunnel mesh stuff.
Eric AF6EP
On Sun, Apr 20, 2014 at 2:22 PM, Steve Wright stevewrightnz@gmail.comwrote:
(Please trim inclusions from previous messages) _______________________________________________
my thought is we need more people working on finishing the portal first.
What exactly is that going to DO?
Here I am sitting on my hands trying to figure out how to get my (already allocated MONTHS AGO) /24 connected to the flamin internet. No one seems focussed on making a wiki entry about THAT. Rather, they'd be happier tunneling their little private network to someone elses'. It seems that many other groups have been waiting YEARS for this assistance or documentation, and MANY other groups who have just given up in disgust.
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? 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.
Thank you.
I've summarized Eric's explanation and added an entry to the wiki.
http://wiki.ampr.org/index.php/Announcing_your_allocation_directly
-Neil
On Sun, Apr 20, 2014 at 5:21 PM, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Though I have yet to get my /24 directly connected, the procedure seems well documented in the TOS found here:
Basicly, do this:
find one or more AS willing to announce your block via BGP and route it to you. Execute the agreement as outlined in the TOS. Anyone who already has an AS running BGP on the internet ought easily understand what is being asked for in the TOS. basicly, you are bringing address space with you. It's kinda the internet version of porting your phone number. If you're looking for an exact list of what to buy to set this up you are not going to find one because that list will vary with tour exact setup. What you will find, again in the TOS is an outline of what that hardware must do. It either needs to at present set up a tunnel mesh or it needs to speak BGP and exactly what equipment speaks BGP is between you and your service provider as it may end up that especially if you're not multihomed they may very well just drop you a point to point link that is your /24 that you can then subnet at will on your end of the link. First things first, find a service provider willing to take you on and talk to them about it. much easier than futzing with all the tunnel mesh stuff.
Eric AF6EP
On Sun, Apr 20, 2014 at 2:22 PM, Steve Wright stevewrightnz@gmail.comwrote:
(Please trim inclusions from previous messages) _______________________________________________
my thought is we need more people working on finishing the portal first.
What exactly is that going to DO?
Here I am sitting on my hands trying to figure out how to get my (already allocated MONTHS AGO) /24 connected to the flamin internet. No one seems focussed on making a wiki entry about THAT. Rather, they'd be happier tunneling their little private network to someone elses'. It seems that many other groups have been waiting YEARS for this assistance or documentation, and MANY other groups who have just given up in disgust.
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? 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.
Thank you.
On Apr 20, 2014, at 5:22 PM, Steve Wright stevewrightnz@gmail.com wrote:
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
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_allocatio...
-Neil
On Sun, Apr 20, 2014 at 6:55 PM, Javier Henderson (javier) javier@cisco.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
On Apr 20, 2014, at 5:22 PM, Steve Wright stevewrightnz@gmail.com wrote:
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@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
The easiest solution might be to just get a cheap server at OVH, have them announce your subnet (one time fee of €100 / subnet), and then route it back over a vpn tunnel to you. They have datacenters in France and Canada. Ofcourse, the question is if this is better then doing ipip mesh :)
For 44.144.0.0/16 we announce this entire subnet in a datacenter in Antwerp, Belgium via a commercial carrier-grade ISP (www.verixi.be), and have 5ghz ubnt antenna's on the roof to inject the ip space in the "hamnet/hamwan" variant in belgium (see http://44.144.0.14/on7lr/ for pictures) Other users (like myself tbh) use vpn tunnels to the datacenter since we don't have LOS to one of the 5ghz nodes.
I think it would be harder to get a cable/dsl ISP to route a subnet for me and route it back to me.
Our local NREN network was also willing to do this, so if you work at a school/college/university that is connected to internet2 or another NREN, you can ask them, they are pretty willing. There is a precedent in sweden (44.140.0.0/16).
Make sure you get a route object in one of the databases like ARIN, RIPE, or the free ones (don't know their names), so all the major carriers allow your subnet through their filters, otherwise only direct peers of your ISP are able to see your subnet. eg: https://apps.db.ripe.net/search/lookup.html?source=ripe&key=44.144.0.0/1...
73s Robbie
On Mon, Apr 21, 2014 at 2:33 AM, Neil Johnson neil.johnson@erudicon.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ 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_allocatio...
-Neil
On Sun, Apr 20, 2014 at 6:55 PM, Javier Henderson (javier) javier@cisco.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
On Apr 20, 2014, at 5:22 PM, Steve Wright stevewrightnz@gmail.com wrote:
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@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- Neil Johnson http://erudicon.com
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Eric Fort -
Javier Henderson (javier) -
Neil Johnson -
Robbie De Lise -
Steve Wright