Hi All,
I remember seeing a list of hardware router that would work with the 44 network. Anyone know where this list is located??
If I remember there was a list of Ubiquiti Edgerouters .
Thanks.
As you know, Brian Kantor, WB6CYT passed away suddenly on November 21,
2019. We will hold a memorial service for Brian on Saturday, Feb 1 2020
at 1:30 PM in La Jolla, CA (part of San Diego). Please see this link for
details:
https://www.evite.com/event/0135NF64ATPRMYGRMEPKGPM2G3LMLQ/rsvp?utm_campaig…
Please bring any photos, mementos and (above all) stories and anecdotes
about Brian to share. Brian wasn't exactly a highly formal person who
stood on ceremony, so we'll keep this informal. If you have a story to
tell, it's up to you whether you stand up and relate it to the whole
group or just a few others at a time. There will be plenty of time for both.
Everyone who knew Brian is welcome. His friendships spanned at least
three distinct social circles, and I know he'd be very happy to see
everyone meet and enjoy everyone else's company. Even if he'd be a
little embarrassed that we were doing it in his honor.
Free snacks and refreshments will be provided, so please RSVP through
the evite link so we can tell the hotel how much to make available. If
you have special dietary needs, please say so; the hotel has a menu we
can choose from.
Please forward this email to anyone you think might be interested. Hope
to see you on the 1st.
Phil Karn, KA9Q
Hello,
Am 05.01.2020 um 11:25 schrieb Rob Janssen via 44Net <44net(a)mailman.ampr.org>:
[..]
> After investigating it appeared that an invalid name has been added to DNS by someone:
>
> dhcp-44-149-72-.db0eif IN A 44.149.72.89
thank you for your open eyes.
It must have been a bug while doing cut+paste. The archive of the source of changes shows the correct entry.
I wish a bugfree new year ;)
vy 73,
- Thomas dl9sau
I noted that since a couple of days the updates to DNS have been stuck
and it caused
a problem with out local DNS server as well.
After investigating it appeared that an invalid name has been added to
DNS by someone:
dhcp-44-149-72-.db0eif IN A 44.149.72.89
Note the trailing minus sign in the name, which is not allowed.
Bind with (default) strict name checking will issue an error on this,
and (I think that is bad)
it will refuse to load or transfer the entire zone. So the previous
version of the zone will
remain active. This was version 2001012115, while the current version
is 2001050245 so
it has been stuck for a couple of days (the format used for the version
is YYMMDDHHMM).
For now I have deleted the bad name, but it would probably be prudent to
add:
check-names warn;
to the zone configurations of the bind daemons running the ampr.org zone
so that they
have the more reasonable behavior of just ignoring that single name
instead of the entire
zone.
Rob