20 Apr
2017
20 Apr
'17
12:42 a.m.
Hi!
I would suggest you rename "peoplesopen.net" to "peoplesopen.net slow"
and "peoplesopen.net 5GHz" to "peoplesopen.net". Then those people who
can see both 5 Ghz and 2.4 GHz will choose a non-slow one, and those who
can see only slow will select that one.
5 GHz and 2.4 GHz does not really have much semantic meaning to most people.
Mitar
i think it's perfect with the numbers, and I
DON'T think it should be
obfuscated with dictionary words or emojis or something.
in fact i think the entire router IP address should be in there!
people need to learn more about networking, it's not that hard, and this
is a
perfect opportunity for that. it's really important that people start
to see
IP addresses, especially if we want people to put up web services on the
mesh
itself! it's really exciting.
peoplesopen.net 10.64.2.1
peoplesopen.net 5GHz 10.64.2.1
-jake
PS i was an early whiner about the same-SSID roaming problems :)
--
http://mitar.tnode.com/
https://twitter.com/mitar_m
We finally have unique SSIDs for the nodes.
Instead of them all being named "peoplesopen.net" they will now have the
last three parts of the IPv4 address added to the name. E.g. for a home
node with the IP 100.64.2.1 the SSIDs will be:
2.4 Ghz: "peoplesopen.net 64.2.1"
5 GHZ: "peoplesopen.net fast 64.2.1"
An extender node with the IP 100.64.2.2 will have the SSID
"peoplesopen.net
64.2.2" even if it is a 5 GHz node. Extender nodes always only have one
radio, so this is fine.
This only applies to home nodes configured after this change and extender
nodes flashed with the latest (not yet downloadable) build.
I moved builds.sudomesh.org to be hosted on the VPS running the
peoplesopen.net website and will grant Grant access as soon as I have his
SSH key so he can upload the latest builds.
We should later upgrade this to map the scary numbers to either nice
simple
english language words (or why limit to english? give an option of
spanish)
or emojis.
For those of you who are not read up on this issue, the nodes need to
have
unique SSIDs because they we do not have layer 3 roaming working, so
when a
client device is connected to a node's "peoplesopen.net" wifi network and
auto-roams to a different node's wifi network also called
"peoplesopen.net"
then it will suddenly be on a new subnet but it will not ask for a new
DHCP
lease, since clients assume that multiple access points with the same
name
are on the same layer 2 networs / subnet. The result is that people
who are
sitting approximately between two mesh nodes will have their internet
intermittently stop working for minutes at a time.
--
marc/juul
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/mesh