[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[terribell]

Hi

Not suggesting this firmware has anything to do with my problem but it started happening since 16E1 and still on 17E5.

Basically very randomly my 2.4ghz wifi will just drop, I only have a few devices on this band now due to this. I was playing my PS4 and noticed I lost my internet.
Went into GUI and I hid the 2.4ghz SSID and my 2.4ghz wifi internet was back, I then changed it back to normal. So changing this brings it back and I guess a reboot would as well.

But Im not sure why its doing this, Im on channel 6 which according to inssider app is the least used channel in my area with channel 1 and 11 being the most used.

Is there anything else i could try in the settings to fix this?

Thanks

I have exactly the same problem on my RT-N66U and it has been like this for a long time, not just from fork version 16E1.
The hiding and unhiding of the SSID resolve the issue until a reboot occurs, after the reboot it will be okay for a time until the 2.4Ghz will be impossible to connect.
I've tried checking syslog but I don't find anything there, even the connection attempts do not appear.

I'm using channel 1 at the moment but this happened on all the channels that I've tried, when the problem occurs no device can connect on that band.

 

[john9527]

I have exactly the same problem on my RT-N66U and it has been like this for a long time, not just from fork version 16E1.
The hiding and unhiding of the SSID resolve the issue until a reboot occurs, after the reboot it will be okay for a time until the 2.4Ghz will be impossible to connect.
I've tried checking syslog but I don't find anything there, even the connection attempts do not appear.

I'm using channel 1 at the moment but this happened on all the channels that I've tried, when the problem occurs no device can connect on that band.

Toggling the SSID broadcast will cause the wireless radios to restart (twice).

First thing that comes to mind, it to check the value of WMM APSD on the Professional page, and set it to Disabled if it's Enabled. This is a power save feature, and from my understanding, there can be some differences in various vendors implementations (clients and the router must talk the same language so to speak).

Also, when this happens, do the clients show on the Wireless Log page?

 

[terribell]

Thanks for the help John.

Yes, wmm apsd was enabled and I've disabled it now.
Regarding the wireless log I have to wait for a new occurrence but from what I remember the clients did not appear.

 

[Wisiwyg]

17E5 Running Nicely!

Thank you John!

 

[ThD]

Upgraded from 17BA to latest, all good so far RT-N66U

 

[aspen63]

There is one other thing to check if your are using a DDNS service. After the boot, double check that the DDNS update has occurred correctly (no exclamation mark on the DDNS data at the top of the main page).

DDNS works fine. I cannot enter the NAS even if I type ip address.

 

[john9527]

DDNS works fine. I cannot enter the NAS even if I type ip address.

I'm at a loss......are you using any custom scripts to set iptables rules?

Other than that....can you follow the steps I provided in this post to zin105...
http://www.snbforums.com/threads/fork-update-for-374-43-available-v17e5.18914/page-172#post-246109

I'll send you a PM with my email to send the data.

 

[telUK]

I have exactly the same problem on my RT-N66U and it has been like this for a long time, not just from fork version 16E1.
The hiding and unhiding of the SSID resolve the issue until a reboot occurs, after the reboot it will be okay for a time until the 2.4Ghz will be impossible to connect.
I've tried checking syslog but I don't find anything there, even the connection attempts do not appear.

I'm using channel 1 at the moment but this happened on all the channels that I've tried, when the problem occurs no device can connect on that band.

Toggling the SSID broadcast will cause the wireless radios to restart (twice).

First thing that comes to mind, it to check the value of WMM APSD on the Professional page, and set it to Disabled if it's Enabled. This is a power save feature, and from my understanding, there can be some differences in various vendors implementations (clients and the router must talk the same language so to speak).

Also, when this happens, do the clients show on the Wireless Log page?

hi

thanks I will check mine then is there any performance effects for disabling WMM APSD?

As for wireless log, like terribell I will have to wait for it to happen again if it does and check that.

Cheers

 

[mobileman88]

Hi @john9527 ,
I am not sure if your latest changes did something very different. But when I tried to use one of my machines to VPN to an external OpenVPN server. My SCP file transfers went up 1000%. This is great. Kudos

 

[Nullity]

Hi @john9527 ,
I am not sure if your latest changes did something very different. But when I tried to use one of my machines to VPN to an external OpenVPN server. My SCP file transfers went up 1000%. This is great. Kudos

11x, really?

What versions?

 

[terribell]

Thanks for the help John.

Yes, wmm apsd was enabled and I've disabled it now.
Regarding the wireless log I have to wait for a new occurrence but from what I remember the clients did not appear.

@john9527 It just happened again, even after disabling WMM APSD.
I can confirm that no device appears connected on the 2.4 Ghz band.

Anything else I can collect to help troubleshoot?

 

[john9527]

@john9527 It just happened again, even after disabling WMM APSD.
I can confirm that no device appears connected on the 2.4 Ghz band.

Anything else I can collect to help troubleshoot?

Well, of course it couldn't be something easy...

When you checked te Wireless Log, were there no entries at all or were there entries that weren't authenticated (the flags at the end of the line)?

Also, when this happens, do the clients still see the SSID broadcast from the router or is it gone?

Both the above will help determine if the radio is really dying or if it's a negotiation issue.

 

[terribell]

Well, of course it couldn't be something easy...

When you checked te Wireless Log, were there no entries at all or were there entries that weren't authenticated (the flags at the end of the line)?

Also, when this happens, do the clients still see the SSID broadcast from the router or is it gone?

Both the above will help determine if the radio is really dying or if it's a negotiation issue.

Answers to both questions:
There are no entries on the wireless log at all and the clients still see the SSID but cannot connect to it.

 

[john9527]

Answers to both questions:
There are no entries on the wireless log at all and the clients still see the SSID but cannot connect to it.

Although I'm not sure why it would change over time, but please check that both your SSID and passphrase don't contain special characters, only alphanumerics ,(and maybe dash and underscore).

 

[terribell]

Although I'm not sure why it would change over time, but please check that both your SSID and passphrase don't contain special characters, only alphanumerics ,(and maybe dash and underscore).

I've had that problem before with some clients, so both the SSID and password only have alphanumeric characters.

 

[john9527]

I've had that problem before with some clients, so both the SSID and password only have alphanumeric characters.

Just to get any potential problem off the table, can your forget/delete the connection profile on the client and recreate it.

We now know the wireless is still alive (since the client can still see the SSID)....it appears to be in the realm of a connection negotiation problem.

 

[terribell]

Just to get any potential problem off the table, can your forget/delete the connection profile on the client and recreate it.

We now know the wireless is still alive (since the client can still see the SSID)....it appears to be in the realm of a connection negotiation problem.

I have already tried that when the clients couldn't connect and it did not allow them to connect anyway.
Are there some logs I can take when this occurs again?

Sent from my TF700T using Tapatalk

 

[Wisiwyg]

Posting here in the event this is unique to the firmware... Otherwise, there are a couple of posts about LTE modems that I could put this http://www.snbforums.com/threads/how-to-use-3g-4g-usb-modem-on-asus-router.30833/#post-242658. Mods please feel free to move this post.

We're having a winter snow storm in Denver today. Comcast Internet is out due to snow and ice. I'm trying to use my Android phone with USB tethering as a USB modem for Dual-WAN failover. When setting the USB modem options, I can select 'Manual' for provider, but then have only CDMA related connection options. When I select 'AT&T', my provider, I get an Auto option, then 4G/3G, 4G only, 3G only, etc. When I hit Apply, the router reboots with the USB modem option selected, but now the provider is Italia Telecom and there are other options filled in. I cannot input AT&T and have it stick or have the other options remain blank.

There seems to be a couple of things that I'm not expecting:
1) In Manual, I would expect to select between CDMA and GSM options to pick what I need...not just CDMA
2) When selecting a provider like AT&T, I would expect it to stay selected after hitting Apply. Further, I would expect that the dial number and other inputs for the provider would remain blank if I had blanked them before hitting Apply.

Firstly, are my expectations off? What is typical behavoir for this?This is the first time I've tried to do this and don't know what to expect.

Second, @john9527 , is it possible (or worth your time) to create an 'Android' or 'iOS' phone tether provider option in the drop down menu?

edit: looking at the linked post above closer... the images show another screen (3rd image) that gives an option to select an android phone. Is that code in this fork? Am I missing how to get to it? Unfortunately the poster doesn't indicate the fw version.

TIA (Using my Android phone tethered directly to my laptop atm.)

 

[RogerSC]

This has got to be something simple, but I just flashed 17E, and the clients window on the Network Map page is showing 0 clients and the "refresh" circle-y thing just spins. I can see that my clients are all connected, have dhcp addresses and internet access. I reset to factory defaults and rebooted, manually entered settings, and turned on IPv6. Then I rebooted again. And the clients widget is still showing 0 clients.

Does this resolve itself over time, or is there some recommended therapy for this one?

Otherwise, by the way, the firmware is working well. Thanks for that!

 

[Wisiwyg]

Yes, will resolve itself in a few minutes... happens to me too.