Re: [44net] 44Net Digest, Vol 3, Issue 78

Steve, Part of the request for 44-IP space from Brian for the intent to advertise it on the Internet is a ISP who is already willing and offered to do this. If this hasn't already been done the IP space you have may not have Brian's approval for that type of use. (But rather used for just IP-in-IP tunnel service) So before you go down that path you may want to check with him first. Once that is completed and you have a LoA (Letter of Authority) from Brian stating you have his approval to advertise this space on the Internet you should be able to do the following. (Some ISP's ask for a LoA, and most should ask). Also note the other requirements that one agrees too: http://www.ampr.org/tos.txt 1) Once you've already discussed this with yoru ISP and they are willing to do this, let the ISP know the IP space and send them the LoA. They will need this so that they can setup the required configs, notify their upstreams, and setup routing of that block to your router. This could take a couple of days, and unless they are HAM friendly (this really helps) or you also purchase a lot of services form them, I would have to guess they may charge for this service. 2) Have your ISP advertise the 44 space assigned to you using their existing BGP ASN and then have them route you your 44 block to your router. 3) This is probably why no one has written this because each person setup will be different depending on how you will use the space. But for yours (with not having any details at all) I will assume you have a router that connects to your ISP with three interfaces. One interface will connect to your ISP and that interface will have a external public routable IP, one interface will point to your internal network with perhaps a 192.168.0.1/24 IP running NAT on that interface. The 3rd interface will be a DMZ network where the 44-net addresses will live. Perhaps a switch plugs into this interface and a different switch plugs into your Internet NAT interface. (don't mix the two within the same logical network/switch/vlan). NOTE: This is only one very simplified example. https://www.osburn.com/ampr_network-140420-1.0.0-example_network.jpg Tim Osburn www.osburn.com W7RSZ On Mon, 21 Apr 2014, Steve Wright wrote: > Date: Mon, 21 Apr 2014 09:22:02 +1200 > From: Steve Wright <stevewrightnz(a)gmail.com> > Reply-To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > To: 44net(a)hamradio.ucsd.edu > Subject: Re: [44net] 44Net Digest, Vol 3, Issue 78 > > (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. >