On Wed, Jun 15, 2016 at 09:19:22AM +0200, Pierre-Philippe F4MZI wrote: There are a LOT of entries on that page but at the very bottom of the list you will see "you may request an allocation from the parent network by clicking here: 44.151.0.0/16" Click on that. Select a netmask of /29. Enter a description - probably your callsign. Set Type to "end user". Check either the Radio or Tunnel boxes as appropriate (Do NOT check the Direct box!). Put any relevant comments in the Notes box (you should mention your existing 44.151.59.1 allocation and that you are requesting additional addresses) and click on Send. If this doesn't work for you, write an email to the coordinator, Ludovic F5PBG (f5pbg(a)free.fr) and ask for help. - Brian

On Wed, Jun 15, 2016 at 09:53:39AM +0200, Pierre-Philippe F4MZI wrote: Correct. - Brian

Hi Brian, You've made me curious. I just stood up a 44 net BGP connection (thank you!). Wouldn't it improve the performance of the 44net traffic (not the internet exchanged traffic) if I also setup RIP over tunnels to the tunneled sections of the network? Thanks, Bill Buhler AF7SJ -----Original Message----- From: 44Net [mailto:44net-bounces+af7sj=buhlerfamily.org@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Wednesday, June 15, 2016 7:55 AM To: AMPRNet working group Subject: Re: [44net] block allocation (Please trim inclusions from previous messages) _______________________________________________ On Wed, Jun 15, 2016 at 09:53:39AM +0200, Pierre-Philippe F4MZI wrote: Correct. The operators of the networks which make up the Internet backbone have chosen not to accept BGP advertisements that are narrower than a /24, possibly to minimize the number of entries in the global routing table, so if you choose DIRECT (BGP) as your subnet connection method, the portal adjusts your netmask up to a /24 if you have chosen something smaller. Note that to have a BGP-advertised subnet, you must have arranged with your Network Service Provider that they will in fact supply you with a connection based on their advertising your subnet to the Internet backbone as being CIDR-routed. It is unusual for NSPs to do this; many won't and others charge a significant amount for the service. You should NOT select Direct in a portal allocation request unless you have arranged for this service from your NSP. In any case, your subnet will be connected to the Internet by at most ONE method: Radio, Tunnel, or Direct, and might not be connected at all, so select at most ONE of the connection method boxes in the allocation request. (I have asked that these selections be changed to a pulldown list or radio buttons so that it is impossible to select more than one; until that happens, requests having more than one box checked are likely to be rejected.) - Brian _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

Hi Brian, Sorry if I'm unclear, so what I'm envisioning is setting up tunnels to the other participants of the 44 net who aren't directly internet routed and using RIP advertisement for them. Then traffic between me and them can bypass the main AMPR 44 net router, reducing latency and reducing bandwidth requirements at the root node. In other words, if anyone on my subnets access the internet it would route through our BGP connected uplink. If they were communicating with another subnet on the AMPRNet it would tunnel directly to them. What do you think? Bill Buhler AF7SJ

right. gateway would have a 44-net address. You can't have the gateway tunnel reach a dead-end. If your 44-net gateway is serving OTHER subnets it could possibly net-44. Yes, exactly. In my case the ISP has given me regular internet addresses as well that I can assign to the tunneling processes. 73, Bill Buhler AF7SJ