Hi Mike,
today would be the "r2-nina" day! all is just uploaded to /test
directory.
In order to test this new revision you have to edit the file "/etc/
config/general" for the nodes you want test. Open that file and change
the line:
option upgd_srv '
www.open-mesh.com/firmware/mr3201a/'
in:
option upgd_srv '
www.open-mesh.com/firmware/mr3201a/test/'
(be carefull to the ending "/")
Using this option the nodes will upgrade from the uploaded test
directory, you must wait until the network becomes stable that is all
nodes did upgrade and have same ESSID.
Now the changes.
0) I experienced better connections than previous, using Linux and
Windows pc with non breaks
1) Nodes now broadcast "spaced" ESSIDs but update-server has to send
ESSID which contains the symbol "*" as space: so, in order to
broadcast an ESSID like "funny mesh" you must send "funny*mesh" in
update reply
2) If checked, Nodes can now enable WPA-PSK in AP#1 and/or disable
AP#2
3) Secondary management server is now enabled, default (if secondary
isn't setted) is
www.open-mesh.com. To enable the secondary, update-
server has to send:
#@#config management
enable.update 1
#@#config general
services.updt_srv www.something.domain
in its update reply.
4) Node DHCPd offers "sticky" leases to clients
5) /sbin/watchout4node would be now more robust (hopefully)
6) MAC-based ACL is implemented but not deeply tested!
7) WifiDog: next revision (surely soon)
...we have also a little problem coming from previous 292!
I saw that the mixed-files bug (some days ago) have also caused wrongs
in assembling the patch which had to be sent to upgrade server, while
the local patch (that for the pc) was correctly assembled. Assuming
that the two tarballs were equal (as they have to be), I just checked
only the local one and not what was to be uploaded.
So, /sbin/upgrade (in c292) has a wrong line which fortunately is
easily removable without re-flash devices. Get /sbin/upgrade from svn/
trunk and when associated with a node, copy this file into /sbin
directory of the node itself. That's all.
I'm very sorry, but it's caused by the previous wrong!
I assure you that I spent the last six days to clean and re-write all
single directory and file in svn and found only this problem. Now
patches and upgrader files have been rewritten and well tested.
Thanks for your patience, I always try to do my best!
Antonio