01-17-2019 02:53 PM
I'm connecting to the internet using an NSM2 with a static IP. Seems that everyday the connection gets progressively worse until I finally reboot the NMS2 and it returns to "normal", as seen by these screen shots of Pingview. I'm pinging the first hop after the router but it does the same thing if I ping the Google IP. I'm running the latest firmware. Any ideas as to why this does this?
01-19-2019 06:23 AM - edited 01-19-2019 06:24 AM
This morning the RX number was bouncing around from 52 to 78 to 104 but never hits 130. TX is at 130 steady.
Rebooted the station and now a ping timeout here and there but not mulptiple fails in a row. RX numbers still bouncing around. All other numbers same as yesterday. Pingview before reboot:
01-19-2019 07:05 AM - edited 01-19-2019 07:07 AM
The link being in the 2.4ghz band, I assume that the band will be congested.
Do a site survey and select a least used channel.
Lower the power so your signal lies in the -45~50 dbm region.
You may also try the "Alternative" mode in the "Data Rate Module" option (Wireless tab)
I forgot to mention, turn "Airmax" on the AP side.
01-19-2019 07:46 AM
The AP is a friend's ISP provided router. We've tried different settings on the signal strength and it didn't make any difference. Don't see why rebooting would "fix" it. I'll change the Data Rate Module and see if that makes a difference.
01-19-2019 08:21 AM
Rebooting the NS doesn't necessarily mean that the problem is on the station side.
I was under the impression that your link consisted on a pair of nanostations, and so the advice.
The AP being an indoor wireless router, perhaps the problem is related to its sensitivity or the low gain of the antennas used.
In other words, your NS can "see" the wireless router, but the router not too well.
01-21-2019 06:53 AM
If that were the case wouldn't adjusting the power level of the NS correct that? The NS is maybe 20 ft away from the router. I have the TX power at 12 now but can go up to 28. Is it possible the power level is actually too high? I don't think I can tell what the signal strength of the NS is on the router side. Oh, and changing to to Alternative on the Data Rate doesn't seem to make a difference.
01-22-2019 03:45 AM
Doesn't seem to have made any difference. Fail rate around 50%. This time I made an insignifigant change to one of the values and saved it and the fail rate dropped back to "normal", about 3%. Does changing a value and saving it force the radio through the same process as rebooting?
01-23-2019 02:55 AM
Get a second Nanostation and create a proper point-to-point link between them in bridge mode with WDS on.
01-23-2019 01:28 PM - edited 01-23-2019 01:35 PM
Not sure what you mean by making the router "stronger". The signal strength from the router is very good, about -30dBm. I can ping the router all day and get a failure rate of about 0.3%. I did see a period of 1 minute today with a continuous string of request timeouts but other than that only one here and there.
01-23-2019 06:20 PM
This should tell you where and why the pings are dropped, I believe, and lead to better debugging results.
01-28-2019 06:24 AM - edited 01-30-2019 06:32 AM
Thanks,@UBNT-JoshMcGee. I was getting about a 25% fail rate on the pings this morning. Did a capture with wireshark and saved two files. I rebooted the NSM2 station and now the fail rate is about 4%. I have no idea what all this shark data means so I've attached the two files. Can you see where the problem is?