So I was troubleshooting a client connection problem today and I noticed the Tranzeo CPE device was having problems staying connected. After further investigation I noticed the memory in the Tranzeo unit was decreasing at a somewhat steady pace, after about 30-60 seconds the 32MB of memory was exhausted and the device lost its association with the AP and would not respond to pings or HTTP requests.
I thought it was an issue with the CPE so naturually I checked the firmware, it was up-to-date so I reloaded it just in case, and still same problem occured. I then assumed the unit defective and replaced with another Tranzeo TR-CPQ19 and noticed the exact same “memory leak” problem.
I then decided to try and switch the customer to a different AP in the area, that worked to a certain degree, I didn’t quite have LOS, but I got an acceptable signal to maintain a connection and there was no sign of the memory leak, however, bandwidth suffered.. The only difference between the two AP’s was the RouterOS version, one was running an old ROS v.2.8.22, where the original AP was running 2.9.8.
To further prove my hypothesis I turned the CPE around to another AP which again had poor LOS, but was able to achieve an acceptable signal level to maintain a connection. When associated to that AP the memory leak did not occur. This third AP was also running ROS v.2.9.8, however, the hardware was different. The third AP is an Intel based board w/ P4 1.7Ghz processor.
The following hardware was in the faulty AP:
Routerboard 230
Senao Prism 200mW (nl series)
After upgrading the “faulty ap” to the latest ROS version (2.9.11) it resolved the memory leak problem on the CPE. This is just an FYI for anyone else who may have run into this same problem or uses Tranzeo CPE equipment.
This was the first user on this particular AP with a Tranzeo CPE device. All other devices were ZCOMAX units and didn’t experience this problem.
It appears the problem exsists with 2.9.8 and the Routerboard 230 w/ prism card when using Tranzeo CPE equipment (particularly the TR-CPQ19). Not exactly sure what the root cause of this problem was, but upgrading to the latest OS version seems to resolve it. Hope this helps someone! 