<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 2014-03-30 23:46, Bart Kus wrote:<br>
<blockquote cite="mid:53390F53.8010201@bartk.us" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix"><br>
BTW, I believe this is the longest email I've written in over a
year. Gotta knock that off. :)<br>
<br>
--Bart<br>
</div>
</blockquote>
<br>
Yep, and it's getting nearly too long to be read, so in this eMail,
I'll address snippets here, and in a separate eMail, address
evangelization.<br>
<br>
<blockquote cite="mid:53390F53.8010201@bartk.us" type="cite">
<div class="moz-cite-prefix">On 3/30/2014 5:42 PM, Dean Gibson
AE7Q wrote:<br>
</div>
<blockquote cite="mid:5338BA10.8040105@ae7q.net" type="cite">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<b>...</b><font color="#3333ff"><b> Hopefully, things are not
going to be so dynamic in HamWAN that hamwan.net DNS servers
are going to be constantly on the move.</b></font> </blockquote>
<br>
No need to worry about changes here. HamWAN authoritative DNS
servers shall forever and always(*) be on 44.24.244.2 and
44.24.245.2. These are anycast IPs from 2 different anycast
ranges.</blockquote>
<br>
Good!<br>
<br>
<blockquote cite="mid:53390F53.8010201@bartk.us" type="cite"><br>
... The BIND choice isn't about scalability, it's about
stability. I can take you through some awesome BIND failures I've
seen over the years. Let's do that not-in-this-email though.<br>
</blockquote>
<br>
No need; I've multiple Windows and Linux systems, and the only
successful attack I've ever experienced was in 1991, in BIND. I was
just mentioning BIND because I've familiar with its capabilities
with regard to DDNS (direct/manual, or via the DHCP server).
Hopefully any replacement has the same capabilities. <br>
<br>
<blockquote cite="mid:53390F53.8010201@bartk.us" type="cite"> ...
To help users cope with all the changes and exposed complexity
happening right now, we're suggesting the shared administration
model. Since you chose not to participate in that, you need to
keep up on your own. I would also point out that you allow
Comcast or whoever your ISP is to manage your modem, since they
don't even give you a choice.</blockquote>
<br>
Frontier (was Verizon), but the same issue. That's why I run a
DMZ. Exterior administrative access (whether Comcast, Frontier, or
HamWAN) is always a giant target.<br>
<br>
<blockquote cite="mid:53390F53.8010201@bartk.us" type="cite"> ...
You've also made it harder on yourself by disallowing remote
access for network operator folks. That's a personal choice
you're of course free to make with your hardware, but I think it's
safe to say we're not gonna stop pushing for our goals to keep the
complexity you're chosen to take on, low.<br>
<br>
... What are we blocking in your tinkering? The two examples you
mentioned (DNS and static IP) we can address right now. DNS we
can do by hand, and static IP is fairly static for you even with
just DHCP. ...<br>
<br>
What kind of tinkering are you thinking of doing? Perhaps some of
that information might drive some inputs to our design plans. I'd
like to know how people use the network in general.<br>
</blockquote>
<br>
What do you mean, "What kind of tinkering are you thinking of
doing?"? I have no real idea; that's why we call it "tinkering"
!!!<br>
<br>
Probably the first thing I'd do, would be to set up another amateur
radio oriented web site; that's one reason for a DNS hostname
served off of a 44.x.x.x DNS server. I have three web sites now
that are devoted to amateur radio (<a class="moz-txt-link-abbreviated" href="http://www.ae7q.com">www.ae7q.com</a>, <a class="moz-txt-link-abbreviated" href="http://www.ae7q.net">www.ae7q.net</a>, and
<a class="moz-txt-link-abbreviated" href="http://www.dstardb.com">www.dstardb.com</a>). I received
<a class="moz-txt-link-freetext" href="http://www.yasme.org/news_release/2013-12-18.pdf">http://www.yasme.org/news_release/2013-12-18.pdf</a> ($1000) for the
first web site. These web sites need to be available to the general
amateur population (hence remaining where they are on the Internet),
but I might set up a more specialized one on the 44.x.x.x network.
I'd suspect this would be a common interest in HamWAN. Right now,
anyone setting up a web site on the 44.24.240.x network is subject
to IP address changes without a hostname being used to hide the
issue.<br>
<br>
There's no rush in solving this; I need to move ae7q.net content
(and a number of eMail addresses) over to ae7q.com in preparation
for using ae7q.net on 44.x.x.x anyway.<br>
<br>
</body>
</html>