What's new

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

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Buddy, thank you for the answer! I'm glad you're doing a very useful job. Please tell me, Merlin AC66 build, 380.70 - supports certificates of 4096 characters?
I'm glad you asked the question....made me double check the 380 code branch. Sorry to report that the limit there is still 3499. The increase only made it into 384.

But, I just finished an update to allow 5119 (5K-1) length on my fork. I'll send you a PM with a link to test it.
 
I'm glad you asked the question....made me double check the 380 code branch. Sorry to report that the limit there is still 3499. The increase only made it into 384.

But, I just finished an update to allow 5119 (5K-1) length on my fork. I'll send you a PM with a link to test it.

You know, it's just amazing, and really necessary and useful work that you do, it is necessary for people. It would be very interesting to test your firmware 5119 (5K-1) Thank you!
 
I'm glad you asked the question....made me double check the 380 code branch. Sorry to report that the limit there is still 3499. The increase only made it into 384.

But, I just finished an update to allow 5119 (5K-1) length on my fork. I'll send you a PM with a link to test it.


I noticed the support for TOR you don't? May I ask why? Thank you for your reply, hope For your understanding.
 
I noticed the support for TOR you don't? May I ask why? Thank you for your reply, hope For your understanding.
TOR was an experimental set of code that ASUS wrote and Merlin debugged (as far as I know ASUS never actually activated it). Just a lot of work to try and port it over/maintain it for a limited audience.
 
Router: RT-AC68U
Firmware: 374.43_33E7j9527

I'm having a strange issue that I think might be router-related. I have two PS4 consoles (Yay! Black Friday) that are both connected to the 2.4GHz network. When one person is playing GTA 5 in an online session, if I merely TURN ON the other PS4, they get disconnected from their GTA Online session. It's very similar to when I run the microwave and the connections get lost so I was wondering if it could be router related.

My only thought is that maybe there's some kind of beamforming thing going on with the single PS4 and when I turn on the second PS4 it loses the connection while reconfiguring the antennas. I'm truly at a loss for why this is happening. I didn't want to go randomly changing settings trying to fix it because everything is working pretty well router-wise except for this new issue.

Each PS4 is assigned a fixed IP address in the DHPC Server tab, if it matters.

Also, not sure if it matters but I have a LOT of devices (20-ish) in my house and almost all of them are connected to the 2.4GHz network because the 5GHz network doesn't seem to be as reliable due to distance from the router. I don't know if there's a limitation with the number of 2.4 GHz devices and I need to move more of them to the 5GHz network or something.

Any ideas?
 
@krick Being disconnected from a game session is not the same as being disconnected from the WiFi. The two are not necessarily related.

From your description it sounds like it's fairly easy to recreate the problem on demand. So I'd start by looking at the "Connected" time in System Log > Wireless Log. From that you can tell if you are loosing the WiFi connection when the game disconnects.

My guess is that this is not a WiFi problem as such.
 
@krick Being disconnected from a game session is not the same as being disconnected from the WiFi. The two are not necessarily related.

From your description it sounds like it's fairly easy to recreate the problem on demand. So I'd start by looking at the "Connected" time in System Log > Wireless Log. From that you can tell if you are losing the WiFi connection when the game disconnects.

My guess is that this is not a WiFi problem as such.

Yeah, the symptoms were similar to what I see when I run my microwave so I wasn't sure if it was a WiFi connection issue or a GTA Online bug or not but the "Connected" time is over 1 hour so I think you're right. It's probably not a router issue. Sorry for the false alarm.

GTA Online is massively buggy, so I guess I shouldn't be surprised.

Thanks for the input.
 
Hi,

I got a RT-N66U and I'm getting loads of DNS NXDOMAIN errors with this firmware (Never had them before this router, when I switch routers I don't get them).

My setup is using a Synology to give out pre-assigned DHCP with the DNS set to 1.1.1.1 & 1.0.0.1. this should bypass the router should but it doesn't seem to be?


I've disabled DHCP on the ASUS. And there are no logs about it either.


I would be using the Archer C7 I have but it doesn't support dual wan and I can't understand openWRT :(
 
My setup is using a Synology to give out pre-assigned DHCP with the DNS set to 1.1.1.1 & 1.0.0.1. this should bypass the router should but it doesn't seem to be?
If you are set up as you say, you are correct, the router will be bypassed for DNS....unless you set up something in DNSFilter which will intercept all the DNS requests.
 
If you are set up as you say, you are correct, the router will be bypassed for DNS....unless you set up something in DNSFilter which will intercept all the DNS requests.
I can confirm that it's setup like that with DNS filtering off.

Is this router doomed?
 
Last edited:
What clients are you using that have a problem (Linux, Win, Android, ....)?
Android, Apple TV, iOS, Synology, Windows 8.

It's weird. Things like speed test take about 30-60 seconds to start then give perfect results with 0% packet loss....

External pings to the router (wan) are fine too....
 
@krick Being disconnected from a game session is not the same as being disconnected from the WiFi. The two are not necessarily related.

From your description it sounds like it's fairly easy to recreate the problem on demand. So I'd start by looking at the "Connected" time in System Log > Wireless Log. From that you can tell if you are loosing the WiFi connection when the game disconnects.

My guess is that this is not a WiFi problem as such.

Welp. I spoke to soon earlier. It just happened again and I checked the wireless log and the other two PS4 consoles lost their connection right when I turned mine on.
 
Welp. I spoke to soon earlier. It just happened again and I checked the wireless log and the other two PS4 consoles lost their connection right when I turned mine on.
Was it just the PS4's that lost their connection or was it all your wireless devices?
Anything in the router's System Log > General Log at that time?
 
Was it just the PS4's that lost their connection or was it all your wireless devices?
Anything in the router's System Log > General Log at that time?

It was only the PS4 consoles that lost their connection. All the other wireless devices are still connected.
The only thing in the general log around that time is this sort of thing. Note that 192.168.1.223 is the IP of the PS4 that I turned on. Seems like a lot of noise to connect a single device. Is that related to beamforming?

Code:
Nov 25 15:11:03 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:03 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:09 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:09 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:09 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:09 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:16 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:16 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:16 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:16 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:21 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:21 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:28 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:28 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:28 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:28 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:34 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:34 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:34 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:34 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:40 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:40 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:46 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:46 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:46 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:46 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:53 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:53 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:53 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:53 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:59 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:59 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:59 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:11:59 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:06 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:06 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:06 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:06 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:12 dnsmasq-dhcp[567]: DHCPDISCOVER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:12 dnsmasq-dhcp[567]: DHCPOFFER(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:12 dnsmasq-dhcp[567]: DHCPREQUEST(br0) 192.168.1.223 dc:a2:66:9d:d4:55
Nov 25 15:12:12 dnsmasq-dhcp[567]: DHCPACK(br0) 192.168.1.223 dc:a2:66:9d:d4:55
 
It was only the PS4 consoles that lost their connection. All the other wireless devices are still connected.
You reported a similar problem earlier in the year with PS3's.

The only thing in the general log around that time is this sort of thing. Note that 192.168.1.223 is the IP of the PS4 that I turned on. Seems like a lot of noise to connect a single device. Is that related to beamforming?
If you have Universal Beamforming turned on you should disable it.
 

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