On two of my Nano Loco M2's I'm running V3.15.1 software. One of the NLM2's is used for tunneling. The other to connect from another room to the tunnel node by RF. The tunnelnode runs for day's without problems. It has 5 client and one server connection going.
When connected, through the other node, the tunnel node starts rebooting spontaneously over and over. If I take the second node up and connect it to the switch, tunnel in to it through a external server it keeps running without a problem.
Took a old 54GL with BBHN v3.1 and connected with the same result.
Reloaded the software several times but it keeps rebooting when connected over RF.
Replaced the node by another NLM2 and.... again the same, reboots when connected by RF, not by tunneling in to it..
Can anyone tell if or what I'm doing wrong..
Ruud
Hi Darryl.
Only the tunnel software is loaded on the node.
Ruud
If anyone else reading this is using a NSM2 loco for tunneling, please confirm A) usage; and B) can reproduce or not. Can't think of why this would be unique to a NLM2, but sometimes things aren't always intuitive.
Triple check basics: swap cat 5 cables, proper power is sustained between 24 and 12v, different RF channel changes anything.
Joe AE6XE
if you tell me how to do that i'm more then willing to do so.
The problem is the timing. I'll try several times as close before the reset as possible.
Ruud
I have tryed to get a few files as close as I could get them before a spontanious reboot. I have sevearal files.
Aached is one of them. If you want more just mail me and I'll snd them to you. There are "a few" ,hi..
Before a reboot the load avarage go's up to way above normal. Seen 7.02-3.2-0.68. Also the memory go's down from aroun 2900Kb to less the 2100Kb. Wait for 10 seconds and you can see the node reboot.
Ruud
Joe, Conrad, Darryl.
I have changed the config over here.
First I switched of the server tunnels. Average load went down to under 0.50. No reboots and memory stayed near 4000Kb.
Added 4 extra tunnels to see what would happen. The load went op marginal, no reboots.
Added just 1 server tunnel and removed the 4 extra client's and the rebooting sequence started again.
Removed al but one client and one server tunnel but the rebooting continued.
To make sure the node itself was not the problem I swaped the NLM2's but without succes.
Put the clients and server on different NLM2's. Linked the client and server. They talk ot each other and no reboots ever since. The load averages stay down, under 0.75 on the server and 0,25 on the client node.
The memory stays near 3800Kb on both nodes..
For now the problem is solved by using two NLM2's but it looks if something is wrong with the tunneling software?.
I know, we want radio links but the tunneling is the only way of getting of my island over here. For that reason I (have to) use the tunnels, hi..
Ruud
did you ever find anything in the file I attached. The problem is far from over and is abt 75-25% to server-client node.
It's not every 2 - 3 hours but once a day to once every 3 days before reboot.
I sill have some more files if want or need them.
73, Ruud
Hi Joe.
t seems I'm not the only one having this problem. Eddie, ZL2AQY seems to have the same problem.
I'm getting more and more convinced it is a memory problem like you suggested before.
This morning I send him a e-mail and put you in the CC (at.arrl.org)
Over here the only thing for both nodes to do is to tunnel and connect the localy used nodes on wifi. There are NO services other the the tunneling software running on the nodes. On one node the client connections and the other the server connections. connected to eachother by wifi and not DtD.The client node is the one rebooting most.
73, Ruud
Hi Joe,
I have been doing some testing today with only Meshchat as a Service and 2 tunnel clients.
All was ok until I tried to use the tunnel server.
As soon as I entered my DNS name the node started to play up locking up and finally rebooting.
This behavior continued until I removed my DNS name and left nothing entered in the tunnel server.
I am running firmware version 3.16.1.0b02
It looks like maybe it doesn't like both the server and the client being used at the same time.
.
73 Eddie
Note that a rocket has 64Mb of RAM and 2x the maneuvering room of the other UBNT devices which have only 32Mb. A typical linux operating system has disk drives and ability to shuttle data between memory and a disk drive (just gets a bit slower), to continue operating and have more space. Embedded devices that don't have disks, do not have this luxury.
Joe AE6XE
Ruud WE1BTV
Thanks for working out that problem Joe.
For now I am running MeshChat on my Raspberry pi (which also runs FreePbx) and I have had no more crashes.
73
Eddie ZL2AQY
Joe AE6XE