> Not much details there. I see DNS updates are to be done by the
> coordinators. As they are volunteers, and as they may be very busy, this
> may not be compatible with a quick update required by a growing network
But you can be the volunteer yourself!
> Our plans were to get a subnet large enough for our island, and to
> manage the "internal" subnetting locally.
You have presented your plans before, and here everyone is wary that a network
on a comparatively small and rural territory like Corsica (330.000 inhabitants)
only used by radio amateurs is not likely to be as large as you picture it.
We all know about the difficulty in getting IPv4 space on internet, but using Net-44
space for a Wireless ISP that just happens to have a couple of radio amateurs in
its admin team is not the way to go.
So you will have to present convincing evidence that this is not what is going on.
> I'm wondering about what would be the best solution :
> - Use an independant domain name (ie, "radioamateur.tk")
> - Use a subdomain of ampr.org (ie, "corsica.ampr.org"), with a
> sub-delegation from the parent "ampr.org" domain
> In both solutions, we would have immediate access for local updates, on
> our local DNS servers.
Different networks prefer and use different solutions. Some use an independent
domain, some use sub-delegated subdomains, others are directly under ampr.org.
Each of them of course has advantages and disadvantages and each sees it in a
different way.
On the Dutch network we put our addresses directly under .ampr.org and use the main DNS
servers. For updating, I am using a script that automatically sends the updates
to the server based on a local hosts file I update with newly assigned addresses.
Whenever I run the script, which automatically happens once a day, the diff between
the current and previous version is made and all changes are sent to the robot by
mail, and appear in the global DNS some minutes later.
I also download the zone file and keep it locally for use when the internet connection
fails. Systems using our local resolvers (44.137.0.1 and 44.137.0.2)
still have .ampr.org resolution, for those addresses not sub-delegated.
This way I don't have to worry about providing DNS service on internet (which is a
can of worms...) and still everyone has access to our names. Reverse also works,
which is usually a problem on the independent networks.
Rob
> Tell that to Cisco that uses 1.1.1.1 as part of their default config for the wireless access points.
It appears that Cisco is well aware of the mistake that they made, and the default has been changed to 192.0.2.1
which is a properly reserved address for this.
I see recommendations to change this address dating back to 2010, so by now it should have been changed
by most active admins, and if not it will not really break anything unless users are using hardwired
DNS settings and use the new 1.1.1.1 service.
However, in wireless systems like this, users will likely use DHCP to set their DNS resolvers, and it will
work at least until the admin changes the DNS advertised via DHCP and does not realize that 1.1.1.1 is
already in use in their own system.
I tried reaching the 1.1.1.1 DNS service via 4 different ISPs here in the Netherlands and it works OK on
all of them. Apparently the use of 1.1.1.1 in routers is not too big of an issue.
Rob
Bill;
A few years back I went to configure my 44.44/16 local net so it included
44.44.44.44. The second it became live, my circuit lost link to it's
tiedown due to excessive botnet flood traffic. It seems as if they
like to use 44.44.44.44 as a test IP of sorts not knowing it's hitting
UCSD.
... just an FYI for ya. Happy Easter/Passover to who it pertains to.
---
73 de Brian, N1URO - supporting packet radio since 1995.
sent via axMail-FAX by N1URO.
Security by obscurity, works every time (for what is debatable :-)
Russ
k4ziv
On 3/30/2018 3:00 PM, 44net-request(a)mailman.ampr.org wrote:
> Send 44Net mailing list submissions to
> 44net(a)mailman.ampr.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mailman.ampr.org/mailman/listinfo/44net
> or, via email, send a message with subject or body 'help' to
> 44net-request(a)mailman.ampr.org
>
> You can reach the person managing the list at
> 44net-owner(a)mailman.ampr.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of 44Net digest..."
>
>
> Today's Topics:
>
> 1. 44net Archives Index (dean .)
> 2. 44net Archives Index (dean .)
> 3. 44net Archives Index (dean .)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 30 Mar 2018 14:38:56 +0000
> From: "dean ." <remodelguy(a)live.com>
> To: "44net(a)mailman.ampr.org" <44net(a)mailman.ampr.org>
> Subject: [44net] 44net Archives Index
> Message-ID:
> <SN1PR15MB0509073EEA669EA64578BF2BB0A10(a)SN1PR15MB0509.namprd15.prod.outlook.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello everyone,
>
> I'm pleased such a community exists. I requested an allocation about three weeks ago and am excited about getting connected!
>
> The last couple of weekends I put two sdr receivers and a couple of websites up on the public internet for a quick migration to the 44 network when a gateway is received and configured correctly.
>
> In preparation for things to come, I've looked at the 44net archives, absorbing what I could. In trying to find info about using PFSense and other subjects, I realized how tedious it was to manually open each archive to search every time an answer or guidance was needed - so an index was made. I wrote a script to sort the subjects, etc. Also, each month was dl'd, expanded, and all put into one folder for ease of searching. Now I can search the index or grep all the files with one command. Maybe this exists elsewhere - I couldn't find it. If anyone is interested, here's the index and expanded files through mid-March contained in one folder:
>
> http://174.71.72.143:8885/files/44archiveMidMar18.tar.xz
>
> Thank you and 73,
> Dean
> K4DIN
>
>
>
