Hi there,
I actually have a /32 IP. I plan to connect a few new machines to the network. So, I would need 3 or 4 new adresses. I went to the web page, the the network tab, and click on 44.0.0.0 / 8 https://portal.ampr.org/networks.php?a=request&id=1 Global link. the smallest block that I can request through this link is a /24. but I don't need a /24, only a /29
how can I send my request directly from the web site ?
thank you
On Wed, Jun 15, 2016 at 08:55:33AM +0200, Pierre-Philippe F4MZI wrote:
I went to the web page, the the network tab, and click on 44.0.0.0 / 8 https://portal.ampr.org/networks.php?a=request&id=1 Global link. the smallest block that I can request through this link is a /24. but I don't need a /24, only a /29
how can I send my request directly from the web site ?
You should probably click on "44.151.0.0/16 France" instead of 'Global'. - Brian
Le 15/06/2016 à 09:07, Brian Kantor a écrit :
(Please trim inclusions from previous messages) _______________________________________________ On Wed, Jun 15, 2016 at 08:55:33AM +0200, Pierre-Philippe F4MZI wrote:
I went to the web page, the the network tab, and click on 44.0.0.0 / 8 https://portal.ampr.org/networks.php?a=request&id=1 Global link. the smallest block that I can request through this link is a /24. but I don't need a /24, only a /29
how can I send my request directly from the web site ?
You should probably click on "44.151.0.0/16 France" instead of 'Global'.
- Brian
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Ok, I tried that, but then I get the list of actives IPs, but I cannot request a new block through this page.
May I try this on the 44.151.0.0/16 request allocation ?
On Wed, Jun 15, 2016 at 09:19:22AM +0200, Pierre-Philippe F4MZI wrote:
Ok, I tried that, but then I get the list of actives IPs, but I cannot request a new block through this page.
May I try this on the 44.151.0.0/16 request allocation ?
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@free.fr) and ask for help. - Brian
Le 15/06/2016 à 09:36, Brian Kantor a écrit :
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.
Minimum netmask size for BGP is /24.
If this doesn't work for you, write an email to the coordinator, Ludovic F5PBG (f5pbg@free.fr) and ask for help.
For personals reasons, I do not want to have any contact with this guy. Never more... That's why I try to handle it by myself.
Thank you
On Wed, Jun 15, 2016 at 09:53:39AM +0200, Pierre-Philippe F4MZI wrote:
Minimum netmask size for BGP is /24.
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
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:
Minimum netmask size for BGP is /24.
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@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On Wed, Jun 15, 2016 at 08:34:10AM -0600, Bill Buhler - AF7SJ via 44Net wrote:
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
I'm unclear on what you would be advertising via the RIP broadcasts. - 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
I'm unclear on what you would be advertising via the RIP broadcasts.
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
On Wed, Jun 15, 2016 at 10:47:16AM -0600, Bill Buhler - AF7SJ via 44Net wrote:
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.
Oh, I see. I always find routing to be confusing but I think I have it right.
The path back to you from the tunnel-connected host is problematic as your gateway would have a 44-net address. You can't have the gateway tunnel endpoint on the same network as it is advertising connectivity to as you reach a dead-end. If your 44-net gateway is serving OTHER subnets it could possibly work. Also it could work if the gateway being advertised is not on net-44.
Someone correct me if I have this wrong, please. - Brian
Oh, I see. I always find routing to be confusing but I think I have it
right.
The path back to you from the tunnel-connected host is problematic as your
gateway would have a 44-net address. You can't have the gateway tunnel
endpoint on the same network as it is advertising connectivity to as you
reach a dead-end. If your 44-net gateway is serving OTHER subnets it could possibly
work. Also it could work if the gateway being advertised is not on
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
-
Bill Buhler - AF7SJ -
Brian Kantor -
Pierre-Philippe F4MZI