FreezeBox

back to http://scratchpad.wikia.com/wiki/Sasecurity

I am running 20 node mesh, all runnning dev88 except one ehich runs on dev 85, no major problem as yours. the biggest problem we face up to day is frozen boxes which still we do not know the exact reason. Node is alive, you see the signal with sigspy, even sometime you can ping to it but neither customers can connect nor we can ssh into to reboot it. Now we have over 300 hundred users authenticated by their MAC addresses only. We do not use VPN or WEP, only clear connection. We guess our problems cause from the RAMs we use. They 128MB, and when there are heavy traffic and user activity, memory is not enough during  swap/unzip or whatever it does, we think. But this is the assumption only, no certain evidence. Second major problem we have faced again, though not often as first, is boxes that return to default settings. When it defaulted, essid changes to Locustworld at channel 1, lost mesh connection and we cannot reach it remotely. So we have to climb to reach it physically. We have changed default settings file so it gets our essid and channel in such cases but still no solution to this. As you see system is in an acceptable reliability even though there are problems that is unacceptable in a paid environement. I recommend you to get professional support from one of the experienced guys near to you. Since you run on bank credit, you have to be very carefull in your operation, I think. Hope you find a quick fix to your problems. In US, Tom Sharples is one of the experts that might off help to you.

> So that we might avoid same, can you let us know what hardware are you > using ? > > We took the decision early on to stick with proprietary off the shelf > equipment in an attempt to minimise the variables i.e. the LocustWorld > Mesh Box and Darklite and Netgear Client equipment. > > These have been out in the field for over a year in attics, Barns and > Loose boxes running build 25 dev 88 and now 90