Merlin 384.19 for AC66U_B1 webex issue?

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

btrieve

New Around Here
Hi,

About a week ago, I recently installed the latest Merlin firmware (384.19 for AC68U) on my Asus router which was previously running stock Asus firmware.
Was running fine until my kid tried to login to his webex classroom (stuck at "connecting"). Tried to troubleshoot further and the problem seems to happen on all machines in my network (wired or wireless).

We also discovered the webex connection (google webex test) works immediately when we connect using a VPN. If I disconnect the VPN, webex connections stop working again.

Since I suspected the new firmware, I reverted back to the Asus firmware (3.0.0.4.386.40558) and it also fixes the problem as does (3.0.0.4.386.41634).

I couldn't figure out the cause, but I figured I would post in case others experience similar issues.
 

L&LD

Part of the Furniture
After flashing the older base firmware from RMerlin, did you do a full reset to factory defaults on the router?

Going from 384.19_0 to 386.xx firmwares without a reset and those issues are to be expected.
 

btrieve

New Around Here
After flashing the older base firmware from RMerlin, did you do a full reset to factory defaults on the router?

Going from 384.19_0 to 386.xx firmwares without a reset and those issues are to be expected.

Good point - When I installed Merlin for the first time I didnt reset defaults since my previous config was left intact. Perhaps this was the cause?

To clarify: I went from Asus stock 386.x to Merlin 384.19_0 (which I believe is the most current stable for AC66U_B1... I didnt yet try Merlin 386.x beta)
 

btrieve

New Around Here
Also, just found this post which reports the same symptoms i had as well:


Sounds like reseting the factory defaults is the fix..
Thanks for your help
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top