What's new

[Beta 382] Asuswrt-Merlin 382.2 Beta is now available

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

Status
Not open for further replies.
That won't be anytime soon, as Asus has yet to release any source code for 384_10007.

The fix Asus is referring to there is for PPPoE.

I got my WAN Connection Type setup as PPPoE, so I guess that's still applicable to me...

Sad to hear not anytime soon...
 
Last edited:
New 382.3 alpha 1 test builds uploaded to the Test Builds folder:

RT-AC3200 (based on GPL 382_19466 code + binary blobs)
RT-AC68U (based on GPL 382_19466 code + 382_19333 binary blobs - hopefully fixes some of the Trend Micro-related issues)
Thank you.

Up and running on my RT-AC68U. Initial impressions are good.
 
Been running 382.2_beta2 for a few days now on my RT-AC86U. It's been working almost perfectly. The only issue is with the web interface and its really minor. I changed the name of all my client devices and added pictures so I could easily find devices in my list. Randomly I've been unable to change the icon or name of clients. I click on the client change the icon and name but when I click apply it goes back to what is was set for before. Sometimes only either the icon or the name changes. I only have a few client devices with this issue. Also sometimes I change the name and the hostname field goes blank and I have to reset it. Again this is a really minor issue.

I had a major problem when I first set up the router on Monday. This issue was total user error and I only put my humiliation here to save anyone else from the same problem. Monday night I was testing different VPN services and connections when all of a sudden I couldn't make any changes to any of the five OpenVPN clients! No matter what I put in or if I clicked default the settings reverted to the last VPN I had successfully working. I tried resetting the router multiple times even went back to 382.1_2. At first after each reset everything seemed fine, but as soon as I started setting up the router the OpenVPN clients would revert back. I finally (after 5 hours!) figured out it happened when I changed the default IP address. I figured out the issue when I connected to the router through Microsoft edge and the OpenVPN clients were fine!

Turned out I had saved the ExpressVPN login info with Lastpass. I didn't realize that it saved almost every field on the page and was auto filling in them every time I went to the page! It only showed up when I changed the IP address because Lastpass matches logins by ip address or domain name. Man I felt stupid when I finally figured it out!

I do have one question. I want to test the unofficial beta3 for AC86U. Should I reset after I upgrade?

Thanks!

ASUS RT-AC86U - Merlin 382.2_beta2
 
I do have one question. I want to test the unofficial beta3 for AC86U. Should I reset after I upgrade?

Thanks!

ASUS RT-AC86U - Merlin 382.2_beta2

Most likely, no reset would be needed. If you see anything weird after the update, you can always factory reset.

If you were moving to the Asus 384 release, then a reset would be needed.
 
Most likely, no reset would be needed. If you see anything weird after the update, you can always factory reset.

If you were moving to the Asus 384 release, then a reset would be needed.

Thanks for the quick response! Gonna give it a go later today.
 
That won't be anytime soon, as Asus has yet to release any source code for 384_10007.

What is the average time Asus normally takes between a firmware release and the source being released? And also, what is the average time it normally takes between a source release and it being integrated into your firmware?

I'm just curious because I just bought a second Asus router to do the mesh thing.

Also I'm not sure which Merlin features I'm currently using. And one last thing. If I do decide to flash the standard AsusWRT over Merlin, do I need to reset the settings, or will it pick up the settings it supports and discard the ones it doesn't?

Thank you.
 
I do have one question. I want to test the unofficial beta3 for AC86U. Should I reset after I upgrade?

No, just flash.

What is the average time Asus normally takes between a firmware release and the source being released? And also, what is the average time it normally takes between a source release and it being integrated into your firmware?

Asus can take anything between 24 hours and a few months to release the GPL (the latter being usually if nobody asks them for it and they forget it).

Once the code is out, it depends on how much change there are from the previous release, whether the GPL release is complete (it often isn't), and so on. So, I usually need a whole evening to analyze the changes, then if the GPL is complete I can take anything between 1 and 5 days to merge (provided I DO have that free time to spend on this). Then you have the debugging/testing period, which can last a couple of weeks.

That's why I'm saying "not anytime soon", as a typical release can take me between a month or two, depending on all those variables, and we haven't even reached the first requisite yet (which is code availability).

If I do decide to flash the standard AsusWRT over Merlin, do I need to reset the settings, or will it pick up the settings it supports and discard the ones it doesn't?

Best you do, as our settings have starting to increasingly divert with the amount of changes in 382. DHCP and various OpenVPN-related settings are no longer compatible for instance.
 
New 382.3 alpha 1 test builds uploaded to the Test Builds folder:

RT-AC3200 (based on GPL 382_19466 code + binary blobs)
RT-AC68U (based on GPL 382_19466 code + 382_19333 binary blobs - hopefully fixes some of the Trend Micro-related issues)

Thank you! 382.3 alpha 1 works fine on RT-AC68U :)
 
Hi to all
I'm using the firmware 382.2 beta 2 for the rt-ac68U on my DSL-ac68U. I know that I lose the modem part, but the additional features compensate for the loss (thanks RMerlin).
Now two question:
1) Yesterday I tried to insert a USB3 Key (the DSL has only one USB3 port) but the USB LED does not light up and the device is not detected. I tried several keys (USB3 or USB2) without result. I also tried to disable the parameter 'Reducing USB 3.0 Interference' without result.
Does anyone find the same problem? Can It be caused by the firmware ? (I remember that with the last fork of HGG the USB keys worked).
I would like to use the USB3 to put the swap file after installing AB-Solution (I read that they recommend creating the swap file).
Does anyone have any suggestions?

2) Do you recommend installing DNSCrypt and AB-Solution using the amtm tools?​

Thanks
 
@RMerlin - ASUS few days ago released .384 branch for RT-AC68U (most likely others will follow):
...
Does this mean you have to move entire ASUSWRT-Merlin to the new code branch again?
This is puzzling. They just got 382 out.

Already discussed on page 20, and probably after that too (not linking to a particular post, as there are various comments on it there).
 
Sorry, missed that.
 
Ping @RMerlin
I don't know what the implication is, I just want to let you know by changing the "client icon" in the Networkmap/clients triggers QOS to restart. No pressure, I know ASUS is the one to fix but thought it might be quicker for asus to know through you.:)
Code:
Jan 11 12:19:54 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Jan 11 12:19:54 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
Jan 11 12:19:54 kernel: ioctl_iqos_op_config() fail!
Jan 11 12:19:54 kernel: ERR[qos_start:3344] QoS is already started!
Jan 11 12:19:54 kernel: ioctl_iqos_op_switch(1) fail!

RT-AC68P 382.3 Alpha1
 
So I installed 382.2_beta3 (Unofficial) on my AC86U. Still having the minor issue of changing the client names. If I do it in the dhcp reserved list it just goes back to what it was before. Also it sometimes removes the hostname. I reset the hostname which reset the name back to the MAC address (lol). When I try from the Network map page not only does it not change the name but I lose the web interface and my internet access for about 90 seconds. Not sure what's going on. Again not a major issue just a minor annoyance. :)

Note: I tried from another browser on my desktop PC same issue. Also tried on my daughter's Windows Notebook same issue.
 
I installed 382.2_beta2 on my AC 68U. I just started playing with the Network Protection Filters. I have found a problem with DNS based filters. If I turn on DNS based filters (either Norton Connect Safe, Yandex Safe, Comodo Secure DNS, or OpenDNS) then some devices cannot get on my Network anymore. One device is a HP Touchpad with Evervolv 7.1.2 Android installed. It looks like that the router gives an IP address, because I see it in the list of devices on the network on the router, but the device never has a completed connection. There are other devices that don't connect either like my Chromecast devices. Looks like this capability has a big problem.

Dec 31 13:53:01 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx *** Chromecast 1
Dec 31 13:53:01 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.249 xx.xx.xx.xx.xx.xx
Dec 31 13:53:01 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx *** Chromecast 1
Dec 31 13:53:13 crond[492]: time disparity of 1272652 minutes detected
Dec 31 13:54:19 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.101.65 xx.xx.xx.xx.xx.xx *** Android device worked fine
Dec 31 13:54:19 dnsmasq-dhcp[484]: DHCPACK(br0) 192.168.101.65 xx.xx.xx.xx.xx.xx android-31931075130e1e0a
Dec 31 13:55:31 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:55:31 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong network
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.194 xx.xx.xx.xx.xx.xx
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong server-ID
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx ***Chromecast 1
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx wrong network
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx *** Android device
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.228 xx.xx.xx.xx.xx.xx
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.84 xx.xx.xx.xx.xx.xx *** Android device
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.84 xx.xx.xx.xx.xx.xx wrong server-ID
Dec 31 13:55:53 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.101.179 xx.xx.xx.xx.xx.xx
Dec 31 13:55:53 dnsmasq-dhcp[484]: DHCPACK(br0) 192.168.101.179 xx.xx.xx.xx.xx.xx Jack-PC *** HP Laptop worked fine
Dec 31 13:58:08 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:58:08 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong network
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.194 xx.xx.xx.xx.xx.xx
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong server-ID
Dec 31 13:58:17 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx *** Chromecast 1
Dec 31 13:58:17 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx wrong network
Dec 31 14:00:46 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 14:00:46 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong network

Why are the devices requesting 192.168.0.xxx instead of 192.168.101.xxx?
 
Last edited:
No, just flash.



Asus can take anything between 24 hours and a few months to release the GPL (the latter being usually if nobody asks them for it and they forget it).

Once the code is out, it depends on how much change there are from the previous release, whether the GPL release is complete (it often isn't), and so on. So, I usually need a whole evening to analyze the changes, then if the GPL is complete I can take anything between 1 and 5 days to merge (provided I DO have that free time to spend on this). Then you have the debugging/testing period, which can last a couple of weeks.

That's why I'm saying "not anytime soon", as a typical release can take me between a month or two, depending on all those variables, and we haven't even reached the first requisite yet (which is code availability).



Best you do, as our settings have starting to increasingly divert with the amount of changes in 382. DHCP and various OpenVPN-related settings are no longer compatible for instance.
I assume you've been asking for the GPL?
 
I don't know what the implication is, I just want to let you know by changing the "client icon" in the Networkmap/clients triggers QOS to restart. No pressure, I know ASUS is the one to fix but thought it might be quicker for asus to know through you.:)

It's how Asus has designed the networkmap - any change will restart the entire networking subsystem.

I assume you've been asking for the GPL?

Yes, asked them earlier this week. They sent them last night, however I'm currently swamped with work and won't have the time to look at it for a couple of days.
 
I installed 382.2_beta2 on my AC 68U. I just started playing with the Network Protection Filters. I have found a problem with DNS based filters. If I turn on DNS based filters (either Norton Connect Safe, Yandex Safe, Comodo Secure DNS, or OpenDNS) then some devices cannot get on my Network anymore. One device is a HP Touchpad with Evervolv 7.1.2 Android installed. It looks like that the router gives an IP address, because I see it in the list of devices on the network on the router, but the device never has a completed connection. There are other devices that don't connect either like my Chromecast devices. Looks like this capability has a big problem.

What did you configure on the Network Services Filter page?
 
What did you configure on the Network Services Filter page?
2018-01-11 20_29_36-ASUS Wireless Router RT-AC68U - Network Services Filter.jpg


I think I added these White List values a few months ago because some SSL traffic on 443 was not getting through. I might not need them now, but I have had no additional problems until I tried to add DNS based filtering. But, Network Services Filter is not enabled, so this setup should do nothing.
 
Last edited:
I installed 382.2_beta2 on my AC 68U. I just started playing with the Network Protection Filters. I have found a problem with DNS based filters. If I turn on DNS based filters (either Norton Connect Safe, Yandex Safe, Comodo Secure DNS, or OpenDNS) then some devices cannot get on my Network anymore. One device is a HP Touchpad with Evervolv 7.1.2 Android installed. It looks like that the router gives an IP address, because I see it in the list of devices on the network on the router, but the device never has a completed connection. There are other devices that don't connect either like my Chromecast devices. Looks like this capability has a big problem.

Dec 31 13:53:01 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx *** Chromecast 1
Dec 31 13:53:01 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.249 xx.xx.xx.xx.xx.xx
Dec 31 13:53:01 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx *** Chromecast 1
Dec 31 13:53:13 crond[492]: time disparity of 1272652 minutes detected
Dec 31 13:54:19 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.101.65 xx.xx.xx.xx.xx.xx *** Android device worked fine
Dec 31 13:54:19 dnsmasq-dhcp[484]: DHCPACK(br0) 192.168.101.65 xx.xx.xx.xx.xx.xx android-31931075130e1e0a
Dec 31 13:55:31 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:55:31 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong network
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.194 xx.xx.xx.xx.xx.xx
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong server-ID
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx ***Chromecast 1
Dec 31 13:55:36 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx wrong network
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx *** Android device
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.228 xx.xx.xx.xx.xx.xx
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.84 xx.xx.xx.xx.xx.xx *** Android device
Dec 31 13:55:40 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.84 xx.xx.xx.xx.xx.xx wrong server-ID
Dec 31 13:55:53 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.101.179 xx.xx.xx.xx.xx.xx
Dec 31 13:55:53 dnsmasq-dhcp[484]: DHCPACK(br0) 192.168.101.179 xx.xx.xx.xx.xx.xx Jack-PC *** HP Laptop worked fine
Dec 31 13:58:08 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:58:08 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong network
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPDISCOVER(br0) xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPOFFER(br0) 192.168.101.194 xx.xx.xx.xx.xx.xx
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 13:58:12 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong server-ID
Dec 31 13:58:17 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx *** Chromecast 1
Dec 31 13:58:17 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.82 xx.xx.xx.xx.xx.xx wrong network
Dec 31 14:00:46 dnsmasq-dhcp[484]: DHCPREQUEST(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx ***Chromecast 2
Dec 31 14:00:46 dnsmasq-dhcp[484]: DHCPNAK(br0) 192.168.0.81 xx.xx.xx.xx.xx.xx wrong network

Why are the devices requesting 192.168.0.xxx instead of 192.168.101.xxx?

I had the same problem here, I set a global dns filter ( norton ) and saved my cellphone and laptop as non filter dns ( google ) dns
some devices on my network stopped to work properly
I reported it here but after a few days trying I finshed just using no global filter and just dns filter for some devices at network
 
Status
Not open for further replies.

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