Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change to another mesh-ssid #2

Open
rubo77 opened this issue Jun 12, 2017 · 3 comments
Open

change to another mesh-ssid #2

rubo77 opened this issue Jun 12, 2017 · 3 comments

Comments

@rubo77
Copy link

rubo77 commented Jun 12, 2017

How many nodes do you have already in your net?

if not many, I would suggest to change the mesh-ssid to something cryptic, because it should not look like something the users want to connect to.

(https://github.com/pjodd/gluon-site/blob/master/site.conf#L56 and line 71)

Only your client SSID should contain the name "pjodd"

@quite
Copy link
Member

quite commented Jul 9, 2017

Would doing this change be doable when you roll out 2017.1.1 anyway (if you do), @karlwettin , or it would just break the network?

@karlwettin
Copy link
Contributor

Don't really have a plan for it, but I think that we should run 2017.1.1 for a little while before we attempt changing the mesh-ssid. Just to make sure it works fine for us. But it sure would break the network. I'm positive to change it though. Perhaps we should all talk about it and vote though.

We probably need to discuss the smartest way to go about it before we do the change, but I suppose the best way is to set all nodes we have physical access to non update update, upload new firmware to the auto update place and then hope for all other nodes to update, and then do it on the nodes we have access to, and then the nodes we have access to with internet access.

Finally we might have to walk around with portable nodes connected to the internet and sit around close those nodes waiting for them to auto update. I have no clue to how often they poll for new firmware, and I'm not sure how we're suppose to detect that they indeed did update when we're sitting there. Would be nice if we could code some notification thingy.

@rubo77
Copy link
Author

rubo77 commented Jul 9, 2017

How many nodes do you have already? Do you have a map? You could install hopglass server and the hopglass map.

You can see if a node updated on the satuspage of the node: http://[IP6]/ there you see the firmware version.

If the last update was long ago, then usually nodes try to find an update once every hour with a random factor:

The autoupdater checks for updates hourly (at a random minute of the hour), but usually only updates during its run between 4am and 5am, except when the whole GLUON_PRIORITY days and another 24 hours have passed.

Feel free to ask in the chat at https://riot.im/app/#/room/#gluon:irc.hackint.org or https://riot.im/app/#/room/#freemesh:irc.hackint.org

@rubo77 rubo77 changed the title change to another mess-ssid change to another mesh-ssid Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants