<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">HamWAN is not just a backbone. It's a
wide-area-coverage network with its own backbone as a necessity.
The health of PtP links is not at issue, but the PtMP layer is.
There are many examples, but here are a few:<br>
<br>
1) Configure the clients with the latest frequency scan lists so
that they can find sites<br>
2) Push new routes down to clients for re-announcement and usage
in home networks<br>
3) Update firmware on clients when critical problems are found<br>
<br>
--Bart<br>
<br>
<br>
On 2/28/2013 4:53 PM, Benjamin Krueger wrote:<br>
</div>
<blockquote
cite="mid:CAMcW5DrVyfE5PJFmQyX7ur-L3oS_VrCSScOOnPmCV5fR60WbqA@mail.gmail.com"
type="cite">
<div dir="ltr">Why do we need to manage end-clients in order to
maintain a solid backbone?</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Feb 28, 2013 at 4:16 PM, Bart
Kus <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:me@bartk.us" target="_blank">me@bartk.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Keeping the network and all client devices correctly
configured is no easy feat. These are complicated devices
with 100s of settings, which will need to change in
coordinated ways over time. To ensure correct operation, it
would make sense for the HamWAN network to push updates and
change settings on end-user modems. Almost all ISPs run
this way already. The difference is you can still login +
control your device, but any setting changes you make which
make the device non-compliant in ways HamWAN cares about
would be automatically overridden with a config update from
the network. If the network can't control and repair your
device settings, you would lose authorization onto the
network until the settings are fixed.<br>
<br>
I see this shared administration model as the only one
that's feasible in keeping a reliable network running.<br>
<br>
Please let me know if you are OK with it, if you object to
it, or if you have a better idea.<br>
<br>
Thanks,<br>
<br>
--Bart<br>
<br>
<br>
_______________________________________________<br>
PSDR mailing list<br>
<a moz-do-not-send="true" href="mailto:PSDR@hamwan.org"
target="_blank">PSDR@hamwan.org</a><br>
<a moz-do-not-send="true"
href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org"
target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Benjamin<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PSDR mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a>
<a class="moz-txt-link-freetext" href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
</body>
</html>