[MVMA] First Impressions

[Maurice Riggins]

> On Apr 28, 2018, at 06:29, N8JJ <n8jj at ameritech.net> wrote:
> 
> We do need to get all our nodes up to 3.16.1.1 before Hamvention

Yes, being a year out of date with a well promoted security update looks bad.

So does publishing an admin password, especially for vulnerable web cams 
that can be used to DoS nodes in the mesh. That’s what one of the security 
updates addresses. A restricted privilege user/viewer account should be 
created and published.

Others can see our mesh, not just during Hamvention but through N2MH.
What impression do we give?

It would also be good if we followed some other common AREDN practices. 

I’m going to use Chuck as an example of good practice. This makes him
look like he knows what he’s doing with AREDN mesh.


Note he uses the convention of naming attached devices in all lowercase
beginning with his call sign followed by a dash (also see N2MH who IMO 
went a bit far with all lowercase node name)

Note he uses dashes to separate words in the node/device names.
 
Note he publishes his channel/frequency and bandwidth in the Services
column instead of in the node name so if he has to change one, the whole 
mesh doesn’t wind up looking at a widely stretched page of 
new-node-name.local.mesh/old-node-name.local.mesh
 
Note he doesn’t tell others to dial *47 before a phone number—people
don’t have BasicTalk ATAs much anymore. Using dots in a phone # 
may be more common, but there’s nothing wrong with asterisks (*)
which are actually dialed—It certainly helps new meshers direct dial—
and I like that.

Note when he lists a phone, the number is lined up with the phone
instead of the node. There’s a pull down for selecting that.
 
Note he puts the node info on a server. Of course, this isn't possible 
at remote sites without one, where it’s better to use Services than
try to cram it all in a sentence-long node name.

Consistency also looks good. If you’re using “Login” on one Service
line, use the same on others (i.e. don’t use “Log In” on the next line).

How do your nodes look to other serious AREDN users?

It would look good if we were able to serve Hamvention with MIMO
on the DARA van, but that’s probably not going to happen this year.
We’re out of time to get the Rocket + AMO Omni off KAS in time for 
Tim to repair it if necessary. Maybe next year.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20180428/bb60e13a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2018-04-28 at 07.40.50.png
Type: image/png
Size: 47723 bytes
Desc: not available
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20180428/bb60e13a/attachment-0001.png>