sirwifi
Regular Contributor
Background
For the past couple of Merlin releases I noticed that I had problems with my phones making VOIP calls over WiFi, 2.4Ghz band. Very poor call quality, hard to understand the other party, etc. It prompted me to look at the WiFi connection. Didn't notice anything unusual, the signal was strong, the connection itself was stable, the clients were not being disconnected. I suspected channel interference, so I tried other channels (but mainly tried to stay with 1, 6, 11). Nothing helped. I thought it was just my phone. But it did it on other phones too.
Troubleshooting
I decided to connect my Macbook Pro (late 2013 model) to the same 2.4Ghz SSID (the Mac normally is on 5Ghz) and ran some iperf tests against a wired Linux server.
What I noticed was jitter all over the place and packet loss around 5%, sometimes lower, sometimes higher. That explained the crappy VOIP calls right away.
Fix
First attempt: I had read about the LTS fork before so I decided to use the latest one V27E5 (which was somewhat tricky to downgrade to from 380.68) because I had no problems in the past with older versions of Merlin. To my surprise, it didn't make a difference, same problems. Then someone mentioned in the forums that even LTS uses the latest drivers for RT-AC68U, so I posted the question which LTS version had the old wireless drivers. Answer: v26E4.
Working fix: I switched to LTS v26E4 which uses wireless driver "Apr 25 2014 11:16:33 version 6.37.14.86 (r456083)" and BINGO! back to a working WiFi. Very low jitter, no more packet loss, a few test calls sound good. Now, it's a bit early to declare total victory but it looks promising.
Just for kicks, I put once again 380.68 back on the router, reset NVRAM, clean configuration by hand. Same problems returned. Now back to LTS v26E4 (the painful way) and it's all fine again.
So there is something going on here, something about the new driver "Jun 1 2017 17:28:05 version 6.37.14.126 (r561982)" and my hardware. I think it's the driver, not sure what else to blame it on. Once again, with the "bad" driver the connection is stable, signal is strong, nothing unusual, except Tx/Rx results in high packet loss and jitter.
For completeness here are my hardware details:
I'm not sure whether the CFE can have an impact in any of the above. Mine is a custom made one based on a guide from 3+ yrs ago.
Now this is one data point, it may be just me, but I'd be curious to hear from others who have genuine RT-AC68U and also modified TM-AC1900.
But if you run into any WiFi problems, you may want to try a firmware version before the driver change.
For the past couple of Merlin releases I noticed that I had problems with my phones making VOIP calls over WiFi, 2.4Ghz band. Very poor call quality, hard to understand the other party, etc. It prompted me to look at the WiFi connection. Didn't notice anything unusual, the signal was strong, the connection itself was stable, the clients were not being disconnected. I suspected channel interference, so I tried other channels (but mainly tried to stay with 1, 6, 11). Nothing helped. I thought it was just my phone. But it did it on other phones too.
Troubleshooting
I decided to connect my Macbook Pro (late 2013 model) to the same 2.4Ghz SSID (the Mac normally is on 5Ghz) and ran some iperf tests against a wired Linux server.
What I noticed was jitter all over the place and packet loss around 5%, sometimes lower, sometimes higher. That explained the crappy VOIP calls right away.
Fix
First attempt: I had read about the LTS fork before so I decided to use the latest one V27E5 (which was somewhat tricky to downgrade to from 380.68) because I had no problems in the past with older versions of Merlin. To my surprise, it didn't make a difference, same problems. Then someone mentioned in the forums that even LTS uses the latest drivers for RT-AC68U, so I posted the question which LTS version had the old wireless drivers. Answer: v26E4.
Working fix: I switched to LTS v26E4 which uses wireless driver "Apr 25 2014 11:16:33 version 6.37.14.86 (r456083)" and BINGO! back to a working WiFi. Very low jitter, no more packet loss, a few test calls sound good. Now, it's a bit early to declare total victory but it looks promising.
Just for kicks, I put once again 380.68 back on the router, reset NVRAM, clean configuration by hand. Same problems returned. Now back to LTS v26E4 (the painful way) and it's all fine again.
So there is something going on here, something about the new driver "Jun 1 2017 17:28:05 version 6.37.14.126 (r561982)" and my hardware. I think it's the driver, not sure what else to blame it on. Once again, with the "bad" driver the connection is stable, signal is strong, nothing unusual, except Tx/Rx results in high packet loss and jitter.
For completeness here are my hardware details:
Code:
TM-AC1900 (2014) flashed as RT-AC68U
Bootloader (CFE): 1.0.2.0
nvram get boardrev
0x1100
nvram get HW_ver
170
nvram get bl_version
1.0.2.0
nvram get wl_corerev
42
I'm not sure whether the CFE can have an impact in any of the above. Mine is a custom made one based on a guide from 3+ yrs ago.
Now this is one data point, it may be just me, but I'd be curious to hear from others who have genuine RT-AC68U and also modified TM-AC1900.
But if you run into any WiFi problems, you may want to try a firmware version before the driver change.
Last edited: