What's new

Asuswrt-Merlin 376.49 is out

  • 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!

Try disabling everything related to AiProtection and AiQoS, as the issue could be related to the TrendMicro DPI engine.

Also try by disabling NAT acceleration.

Both are closed source, and beyond my control.

AiProtection and AiQoS already disabled.
Will try disabling NAT Acceleration even knowing performance will be a problem (1gb WAN) and let you know.

Thanks!
 
The filtering services supported by DNSFilter are YandexDNS, OpenDNS, Norton Connect Safe and Comodo Secure DNS. Of these, Yandex is the only one with IPv6 servers. Google's public DNS are just standard resolvers, with no filtering capability, so they aren't relevant.

Ah, I see what you mean. Thank you - that makes much more sense.
 
Try disabling everything related to AiProtection and AiQoS, as the issue could be related to the TrendMicro DPI engine.

Also try by disabling NAT acceleration.

Both are closed source, and beyond my control.

Hi RMerlin,

I use a AC87 i have disabled NAT Acceleration to test to see if i still get the errors i have been experiencing in my sys log.

I am sure this has been asked before, but does disabling NAT Acceleration have any impact on my network speed? WAN to LAN and vice versa?

Or does it just mean the CPU load is higher?

Thanks in advance,

Regards
 
Will try disabling NAT Acceleration even knowing performance will be a problem (1gb WAN) and let you know.

Thanks!

Just for testing purposes to see if it's related.
 
Disabling NAT Acceleration fixed some of the errors but not the vlan1 error.

Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPDISCOVER(br0) 40:f4:xxxxxx:33
Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPOFFER(br0) 192.168.1.114 40:f4:xxxxxx:33
Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPREQUEST(br0) 192.168.1.114 40:f4:xxxxxx:33
Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPACK(br0) 192.168.1.114 40:f4:xxxxxx:33
Dec 31 19:26:36 kernel: br0: received packet on vlan1 with own address as source address

Regards
 
Hello, everyone. This is my first post but have been lurking for quite a while. I have an Asus RT-AC66U router and yesterday I upgraded the firmware from 49_2 to 49_4, right after doing so, both my and my wife's Samsung Galaxy Note 4s will no longer connect to the WiFi. Our laptops and Amazon Fire TV stick connect wirelessly without issues. I tried to reboot the router and forget the wifi connection profile on the phone and reconnect, no joy. The phones see the router and can authenticate but it stalls on "obtaining IP" and goes no further. The wifi on the router is set up for N only and both the 2.4 Ghz and Ghz radios are enabled, set to the same password, and use WPA2. Something in the latest update borked our ability to connect our phones. any suggestions would be appreciated.

Same issue here but on Asus RT-AC56U.
 
Just tried this build. In 5ghz bridge mode, using the 2.4ghz radio as an access point is broken. Didn't try the other way around. Reverted back to 376.48 update 3. I'm using a RT-AC66.
 
been running 376.49_4 for a couple days now, no issues.

Sam
 
Disabling NAT Acceleration fixed some of the errors but not the vlan1 error.

Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPDISCOVER(br0) 40:f4:xxxxxx:33
Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPOFFER(br0) 192.168.1.114 40:f4:xxxxxx:33
Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPREQUEST(br0) 192.168.1.114 40:f4:xxxxxx:33
Dec 31 19:25:05 dnsmasq-dhcp[681]: DHCPACK(br0) 192.168.1.114 40:f4:xxxxxx:33
Dec 31 19:26:36 kernel: br0: received packet on vlan1 with own address as source address

Regards

Same issue here on my RT-AC87u...
 
Try disabling everything related to AiProtection and AiQoS, as the issue could be related to the TrendMicro DPI engine.

Also try by disabling NAT acceleration.

Both are closed source, and beyond my control.

There's probably an issue with Trend Micro engine.. my router (RT-AC87u) rebooted itself today after sending a dump to the syslog... a very specific part of the log read like this:

---------cut here---------------

Unfortunately I didn't capture the log to be able to post it here.. but I will next time.

A few seconds after that turned up in the log, the router rebooted...


I'll report back as soon as I can provide more details on this.

Cheers,

Dragster
 
For RT-AC87U owners: I did a quick recompile of the firmware with the newest Quantenna SDK taken from the recent Asus release (since updating the SDK was a fairly simple thing to do). Grab it here:

http://www.mediafire.com/download/5z5zlb4z6yz412e/RT-AC87U_3.0.0.4_376.49_5_newqtn.zip

This uses the new Quantenna v36.7.0.31 driver which should resolve compatibility issues with Apple devices. Asus recommends doing a factory default reset when updating to this new driver - I suggest people first test it without doing so. If you still have connectivity issues with your Apple devices, then go ahead and do the recommended factory default reset + manual reconfiguration.

Been running it on my own router for the past few hours now while using the laptop connected over 5 GHz wifi without any problem.
 
wow you just beat the New Year...thanks Merlin I will try it out in the morning...
 
@merlin i have installed this test build and since then I have sometimes connection but no internet. Disabling wifi on the iPhone en enable again fixes that. Normal _4 build does not have that issue. So the new driver is something off I guess.
I have ac87u and iPhone 6 connected in ac mode.
 
For RT-AC87U owners: I did a quick recompile of the firmware with the newest Quantenna SDK taken from the recent Asus release (since updating the SDK was a fairly simple thing to do). Grab it here:

http://www.mediafire.com/download/5z5zlb4z6yz412e/RT-AC87U_3.0.0.4_376.49_5_newqtn.zip

This uses the new Quantenna v36.7.0.31 driver which should resolve compatibility issues with Apple devices. Asus recommends doing a factory default reset when updating to this new driver - I suggest people first test it without doing so. If you still have connectivity issues with your Apple devices, then go ahead and do the recommended factory default reset + manual reconfiguration.

Been running it on my own router for the past few hours now while using the laptop connected over 5 GHz wifi without any problem.

So what are these compatibility issues?
I have both a Macbook Pro and several iPhones (and an iPad) and do not see any issues (as far as I know at least).
 
So what are these compatibility issues?
I have both a Macbook Pro and several iPhones (and an iPad) and do not see any issues (as far as I know at least).

I suffered with disconnect issues, this was fixed with an earlier RMerlin release, however the new .4 driver has accelerated my throughput to 150 meg/sec which is the limit of my broadband connection, so i am very happy with the new .4 release. :)
 
Ok, thank's for the information, I'm running .4 release too.
 
Perhaps I spoke too soon, is this a sign of the compatibility issue (wrong address on an iPhone 5S)?

Jan 1 13:21:35 dnsmasq-dhcp[2365]: DHCPREQUEST(br0) 192.168.161.25 dc:9b:9c:xx:xx:xx
Jan 1 13:21:35 dnsmasq-dhcp[2365]: DHCPNAK(br0) 192.168.161.25 dc:9b:9c:xx:xx:xx wrong address
Jan 1 13:21:36 dnsmasq-dhcp[2365]: DHCPREQUEST(br0) 192.168.1.213 dc:9b:9c:xx:xx:xx
Jan 1 13:21:36 dnsmasq-dhcp[2365]: DHCPACK(br0) 192.168.1.213 dc:9b:9c:xx:xx:xx iPhone5S
 
Perhaps I spoke too soon, is this a sign of the compatibility issue (wrong address on an iPhone 5S)?

Jan 1 13:21:35 dnsmasq-dhcp[2365]: DHCPREQUEST(br0) 192.168.161.25 dc:9b:9c:xx:xx:xx
Jan 1 13:21:35 dnsmasq-dhcp[2365]: DHCPNAK(br0) 192.168.161.25 dc:9b:9c:xx:xx:xx wrong address
Jan 1 13:21:36 dnsmasq-dhcp[2365]: DHCPREQUEST(br0) 192.168.1.213 dc:9b:9c:xx:xx:xx
Jan 1 13:21:36 dnsmasq-dhcp[2365]: DHCPACK(br0) 192.168.1.213 dc:9b:9c:xx:xx:xx iPhone5S


Do you have a mixture of static ip address's on your network? For example if you have a static ip of 192.168.1.5 for your main computer but your DHCP address range is 192.168.1.2 to 192.168.1.255 then you need to modify the range to NOT include any static ip's

My DHCP range starts at 192.168.1.10 as any below that are static ip's

Does that make sense?

Regards
 
I have exactly what you describe, a 'Static Range' from 2-19 and the rest (20-254) on DHCP, but this goes against RMerlin's recommendations..

Address 192.168.161.25 in the log I showed in a previous post is definitely not in my Static Range, not even in my network (192.168.1.x) at all!

It was my wife's iPhone that had that strange address, I wonder if it is some address she picked up in a shop before coming home.
 
Last edited:

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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