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:

1) Configure the clients with the latest frequency scan lists so that they can find sites
2) Push new routes down to clients for re-announcement and usage in home networks
3) Update firmware on clients when critical problems are found

--Bart

On 2/28/2013 4:53 PM, Benjamin Krueger wrote:

Why do we need to manage end-clients in order to maintain a solid backbone?

On Thu, Feb 28, 2013 at 4:16 PM, Bart Kus <me@bartk.us> wrote:

Hello,

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.

I see this shared administration model as the only one that's feasible in keeping a reliable network running.

Please let me know if you are OK with it, if you object to it, or if you have a better idea.

Thanks,

--Bart

_______________________________________________
PSDR mailing list
PSDR@hamwan.org
http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org

--

Benjamin
_______________________________________________
PSDR mailing list
PSDR@hamwan.org
http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org