Hello Everyone,
I finally found some free time and have been working on the Portal code today:
Fixed a few bugs that have been reported to me; Altered the wording on the emails that are sent out following feedback; Removed validation checks for co-ordinators rejecting IP allocation requests; Removed strict control over what networks can be added to gateways.
The last point probably requires further explanation: I added a filter that only allowed gateway owners to link networks to their gateways that were a) allocated and b) owned by them. This caused some issues as some people have their networks announced by gateways controlled by other people.
So now, anyone can add any network to their gateway that a) has been allocated, and b) has the "connection type” field set to “TUNNEL”. You just select which network you want to add from the drop down box.
If the network you wanted to add doesn’t appear in the drop down box, please check that it has been allocated and that it’s connection type is set to “TUNNEL”.
Any problems, bugs, etc, please let me know.
Thanks, Chris
Hi Chris
THANK YOU. Added subnet OK. Much appreciated 73 de Paul g4apl
Chris.
Good news! Thank you very much.
Best regards.
On Wed, Mar 11, 2015 at 9:27 AM, Chris chris@g1fef.co.uk wrote:
So now, anyone can add any network to their gateway that a) has been allocated, and b) has the "connection type” field set to “TUNNEL”. You just select which network you want to add from the drop down box.
Can you help me understand how this "connection type" field works? For example, we have a network (44.24.240.0/20) that is connected via radio, BGP, and tunnel. BGP is to support the majority of the Internet; tunnel for other AMPR networks that can't announce themselves directly (those with residential ISPs, no BGP); and the radio connection is the whole point of using AMPR addresses. The "connection type" dropdown only allows one selection at a time, so what do we select in our case? And what behavior does this influence on the backend that we should be aware of?
Tom KD7LXL
Hi Tom,
So now, anyone can add any network to their gateway that a) has been allocated, and b) has the "connection type” field set to “TUNNEL”. You just select which network you want to add from the drop down box.
Can you help me understand how this "connection type" field works? For example, we have a network (44.24.240.0/20) that is connected via radio, BGP, and tunnel. BGP is to support the majority of the Internet; tunnel for other AMPR networks that can't announce themselves directly (those with residential ISPs, no BGP); and the radio connection is the whole point of using AMPR addresses. The "connection type" dropdown only allows one selection at a time, so what do we select in our case? And what behavior does this influence on the backend that we should be aware of?
This is an issue that has cropped up before and was on my TODO list: as you quite rightly point out, some networks are connected via multiple means, e.g. BGP and Tunnels, etc.
So today I have crossed off one more item from my TODO list, networks now have three separate checkboxes for connection type and you can check more than one (or leave them all unchecked if the network is not yet connected).
The changes involved several processes so if anyone finds any bugs that have crept in, please let me know.
Also, for anyone that has an allocated network, please ensure that the correct box(es) are ticked for your network(s).
Thanks, Chris
On Thu, Mar 12, 2015 at 12:12 PM, Chris chris@g1fef.co.uk wrote:
So today I have crossed off one more item from my TODO list, networks now have three separate checkboxes for connection type and you can check more than one (or leave them all unchecked if the network is not yet connected).
Great, thanks!
I'm still curious: what do these boxes actually do? What do they affect? e.g., If we don't check "tunnel", will our gateway and route disappear from the encap?
Tom KD7LXL
Hi Tom,
So today I have crossed off one more item from my TODO list, networks now have three separate checkboxes for connection type and you can check more than one (or leave them all unchecked if the network is not yet connected).
Great, thanks!
I'm still curious: what do these boxes actually do? What do they affect? e.g., If we don't check "tunnel", will our gateway and route disappear from the encap?
At this point existing networks that did not have “tunnel” ticked will not be removed, in fact I have done a mass “tick” on the database for all existing networks that are announced via tunnels, so we are synch. From now on though, you will not be able to add a network to a gateway unless the network has the tunnel box ticked.
It’s mainly to ensure accuracy of the data, at some point the database will be opened (in part) to the public via a whois server so it does need to be accurate. This is particularly important for BGP announced networks. The “radio” box is just for information at this stage and does nothing else.
Regards, Chris
Chris;
Any problems, bugs, etc, please let me know.
Keep up the fine work. Unfortunately we've been conditioned to a world where if someone clicks on a pretty picture, everything is supposed to work perfectly as of yesterday.
Your contributions to the hobby are appreciated.
Here, here!!
Mitch On Mar 11, 2015 9:08 PM, "Brian" n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ Chris;
Any problems, bugs, etc, please let me know.
Keep up the fine work. Unfortunately we've been conditioned to a world where if someone clicks on a pretty picture, everything is supposed to work perfectly as of yesterday.
Your contributions to the hobby are appreciated.
-- The most difficult egg to beat is one that is hard boiled.
73 de Brian Rogers - N1URO email: (see above) Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Brian -
Chris -
Mitch Winkle -
Paul Lewis -
SP2L -
Tom Hayward