Beta Asuswrt-Merlin 3006.102.4 Beta is now available

[Dedel66]

HUH WHAT???? where you getting 3096 bro, I went from ASUS RT-BE92U Firmware version 3.0.0.6.102_37526 to Merlin RT-BE92U_3006_102.4_beta1 Firmware

You could be a little more polite... 3096 is obviously a typo...

 

[GWTechTalk]

HUH WHAT???? where you getting 3096 bro, I went from ASUS RT-BE92U Firmware version 3.0.0.6.102_37526 to Merlin RT-BE92U_3006_102.4_beta1 Firmware

So you went from factory firmware to a FORK of similar firmware. Meaning code has been changed, features added, and GUI possibly updated. You need to factory reset the device so that the Merlin defaults are loaded and any incompatible settings are cleared. Then set up the device again manually in the Merlin fork. Stock and Merlin are NOT the same and should be treated like a brand new firmware. Sounds like you flashed to Merlin but chose to retain stock settings and now you are having an issue. Factory reset and manual setup need to be completed before this can be determined as a bug or not. What you did is called a dirty flash. You can’t do that when changing to a new firmware fork. However, that tends to work fine if you are loading a new version on the same fork. Still not recommended as Merlin is in active development.

 

[JoGi]

Did you remove and re-add the AiMesh nodes as recommended?

i have always in the past learned and i think that is also the advice of merlin. that if your main router runs on merlin, the aimesh routers just keep running on latest stockfirm?
or did i miss something and is it also advised to run merlin firmware on aimesh routers?

Pls correct me if i’m wrong

 

[GWTechTalk]

i have always in the past learned and i think that is also the advice of merlin. that if your main router runs on merlin, the aimesh routers just keep running on latest stockfirm?
or did i miss something and is it also advised to run merlin firmware on aimesh routers?

Pls correct me if i’m wrong

Normally that’s how I leave my mesh. With past models there have been issues where Merlin’s fork just could not add new mesh nodes so you had to setup the mesh nodes first then upgrade the main router to Merlin. I don’t use a mesh anymore. So I can’t say for sure.

 

[alan6854321]

So, I've been running this FW for over four days now and I think it's probably the most stable release I've ever run.

I have a fair number of IoT devices - Smart plugs, lights and IP cams, and they usually have a habit of disconnecting/reconnecting on a regular basis. But, on this release, everything is quiet and they all just seem to sit there and work. Like they should.

Aimesh with a 3004 node works fine as well and our phones switch to the best source as we move around the house/garden.

I haven't crossed-swords with guest networks yet, they look a lot more complicated than the previous incarnation. Maybe I don't need to as I've managed fine without them up to now.

 

[freddyjuarez]

So you went from factory firmware to a FORK of similar firmware. Meaning code has been changed, features added, and GUI possibly updated. You need to factory reset the device so that the Merlin defaults are loaded and any incompatible settings are cleared. Then set up the device again manually in the Merlin fork. Stock and Merlin are NOT the same and should be treated like a brand new firmware. Sounds like you flashed to Merlin but chose to retain stock settings and now you are having an issue. Factory reset and manual setup need to be completed before this can be determined as a bug or not. What you did is called a dirty flash. You can’t do that when changing to a new firmware fork. However, that tends to work fine if you are loading a new version on the same fork. Still not recommended as Merlin is in active development.

Thank you for this answer I'm going to hard reset router later today...

 

[jarip]

The Asus router is trying to use 192.168.52.1 for itself, so your Netgate device will need to use a different address.

Changed it in pfSense to 192.168.52.2 and rebooted 88U Pro. Dnsmasq error message is gone, but VLAN still not working.
Looking at system log in pfSense, I see

Apr 16 19:53:41    dhcpd    63542    DHCPDISCOVER from xx:xx:xx:xx:xx:xx via igc3: network 192.168.4.0/24: no free leases

So it looks like 88U Pro is not adding VLAN tag????

 

[CaptainSTX]

Changed it in pfSense to 192.168.52.2 and rebooted 88U Pro. Dnsmasq error message is gone, but VLAN still not working.
Looking at system log in pfSense, I see

Apr 16 19:53:41    dhcpd    63542    DHCPDISCOVER from xx:xx:xx:xx:xx:xx via igc3: network 192.168.4.0/24: no free leases

So it looks like 88U Pro is not adding VLAN tag????

If I look in my log the VLAN numbers are there. See attached file. VLAN = 0 or 52 or 53. Running an AX88 Pro on Beta 1.

 

[visortgw]

Changed it in pfSense to 192.168.52.2 and rebooted 88U Pro. Dnsmasq error message is gone, but VLAN still not working.
Looking at system log in pfSense, I see

Apr 16 19:53:41    dhcpd    63542    DHCPDISCOVER from xx:xx:xx:xx:xx:xx via igc3: network 192.168.4.0/24: no free leases

So it looks like 88U Pro is not adding VLAN tag????

Is that possibly because it is set up as an AP (as opposed to as a router)?

 

[RMerlin]

Changed it in pfSense to 192.168.52.2 and rebooted 88U Pro. Dnsmasq error message is gone, but VLAN still not working.
Looking at system log in pfSense, I see

Apr 16 19:53:41    dhcpd    63542    DHCPDISCOVER from xx:xx:xx:xx:xx:xx via igc3: network 192.168.4.0/24: no free leases

So it looks like 88U Pro is not adding VLAN tag????

Your router is trying to obtain a lease from the 192.168.4.0/24 subnet, which is not handled by the Asus router.

This is really a pfsense configuration issue, and should be discussed in a separate thread.

 

[jarip]

Your router is trying to obtain a lease from the 192.168.4.0/24 subnet, which is not handled by the Asus router.

Actually it wasn't, turned out that the culprit was Suricata running on 192.168.4.1 interface. When turned off, client connected immediately with correct IP.

This is really a pfsense configuration issue, and should be discussed in a separate thread.

Sorry about that, obviously I wasn't sure where the problem is. All good with 3006.102.4_beta at the moment, thank you.

 

[bbunge]

i have always in the past learned and i think that is also the advice of merlin. that if your main router runs on merlin, the aimesh routers just keep running on latest stockfirm?
or did i miss something and is it also advised to run merlin firmware on aimesh routers?

Pls correct me if i’m wrong

That is not what I mean. After upgrade to the 3006 firmware, if you are having problems with the AiMesh nodes, remove them as nodes which will reset them then add them back into the AiMesh system.
As for the firmware on the nodes, there is plenty of debate: use Merlin or use Asus. I've done both with good results. There are reasons to use Merlin such as the ability to just use Samba with SMB2. With merlin one can run scripts, add swap and several other useful features. At this moment I am running Merlin on my AX86U AiMesh node.

 

[dsring]

So, I've been running this FW for over four days now and I think it's probably the most stable release I've ever run.

I have a fair number of IoT devices - Smart plugs, lights and IP cams, and they usually have a habit of disconnecting/reconnecting on a regular basis. But, on this release, everything is quiet and they all just seem to sit there and work. Like they should.

Aimesh with a 3004 node works fine as well and our phones switch to the best source as we move around the house/garden.

I haven't crossed-swords with guest networks yet, they look a lot more complicated than the previous incarnation. Maybe I don't need to as I've managed fine without them up to now.

Just curious if you factory reset after updating to this version. I am thinking about flashing this version, but I don't want to go through the process of setting everything up after a factory reset. I will be updating from Asuswrt-Merlin 3004.388.8_4.

 

[RMerlin]

I just finished merging GPL 102_37526 for the RT-BE92U, which Asus uploaded to my server tonight. I expect to have beta 2 available probably by the end of the week.

 

[RMerlin]

It’s used for NTP intercepting already, so it can’t be too flaky. But then the whole “Access Intranet” setting comes into play. Complicated.

One little nuance about "Router" mode that I had forgotten: by default, "Router" will try to redirect to the DNS servers configured on the DHCP page. If there is no server configured there, only then the router's own IP is used. That might be why I ended up using a DNAT target back then, as it would work regardless of the destination (DHCP DNS or router itself).

I am tempted to change the behaviour so "Router" would always only redirect to the router itself, and people wanting to redirect to a custom server configured on the DHCP page would then need to configure them as a Custom DNS Director target. Doing so would make the global behaviour more consistant, since right now, for a Guest Network, that Router mode only uses the router's IP (on that subnet) rather than any DNS server configured within the Guest Network itself. It would probably be more intuitive as well, since "Router" would truly mean "the router itself" rather than "Whatever is configured on the DHCP server, with the fallback being the router itself".

 

[Ripshod]

Well, instead of posting just after installing I've waited a sensible length of time to allow bugs to show. I must say this firmware is good to go for my needs.

 

[dwadj]

I also update my GT-AX110000 pro (main + node in AIMesh wifi 5G2 as backbone) from official Asus 3.0.0.6.102_34750 to this beta....
At first it looked ok, however in AiMesh this beta is not working...
Some clients would not connect and others are constantly connecting/disconnecting.
Checked all settings but could not resolve it.
So went back to official 3.0.0.6.102_34750 firmware and all works fine again, so @RMerlin think still some work in progress?

 

[MDM]

I also update my GT-AX110000 pro (main + node in AIMesh wifi 5G2 as backbone) from official Asus 3.0.0.6.102_34750 to this beta....
At first it looked ok, however in AiMesh this beta is not working...
Some clients would not connect and others are constantly connecting/disconnecting.
Checked all settings but could not resolve it.
So went back to official 3.0.0.6.102_34750 firmware and all works fine again, so @RMerlin think still some work in progress?

You did Factory reset after going from official to RMerlin as indicated several times in this thread...?
Otherwise report does not count.

 

[dwadj]

You did Factory reset after going from official to RMerlin as indicated several times in this thread...?
Otherwise report does not count.

Yes of course, but it should not matter, because i was already on the 3006 from Asus.

 

[Ripshod]

Yes of course, but it should not matter, because i was already on the 3006 from Asus.

I refer you back to post #262

Beta - Asuswrt-Merlin 3006.102.4 Beta is now available

HUH WHAT???? where you getting 3096 bro, I went from ASUS RT-BE92U Firmware version 3.0.0.6.102_37526 to Merlin RT-BE92U_3006_102.4_beta1 Firmware You could be a little more polite... 3096 is obviously a typo...

www.snbforums.com

But it doesn't matter since you reset after flashing Merlin