Beta Bluecave beta firmware released Version 9.0.0.4.386.41994 Beta Version 2021/02/02

[Northguy]

Please note that Asus released a new beta firmware Version 9.0.0.4.386.41994 Beta Version 2021/02/02

Just installed the fw and I can report that the reboot issue seems resolved in this fw version

 

[Smedley]

As reported by chongaik3 in asuswrt-386-rc2-public-beta-with-full-functions-aimesh-2-0-continued

Version 9.0.0.4.386.41994 Beta Version 2021/02/02 33.05 MBytes
ASUS Blue Cave Firmware version 9.0.0.4.386.41994 (Beta Version)
Security Fixed:
Fixed CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685, CVE-2020-25686

However, when we download and unzip the file. We get BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx.

Besides Northguy above, have any other brave Blue Cave users installed this version? If so, does it resolve some of the reported stability issues of the prior few releases?

 

[NSNE]

I also got BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx after unzipping. Was really hoping it would bring the Blue Cave onto the 386 line, but it looks like that was a hasty typo on ASUS’ part.

Installed it a few days ago and have seen nothing but stability with an AX88U and AC68U mesh network. Then again, I hadn’t seen many issues with the Blue Cave as an occasional node prior to this.

 

[chongaik3]

Hi, i have problem setup my VoIP on 9.0.0.4.386.41994". I reported here - http://www.snbforums.com/threads/as...ctions-aimesh-2-0-continued.69274/post-660102

In fact, i'm facing this problem since Version 3.0.0.4.384.46468. Reported to Asus Support but they insist no bug/problem. Asus even told me they do not have the equipment to simulate my problem.

 

[mtdoit]

As reported by chongaik3 in asuswrt-386-rc2-public-beta-with-full-functions-aimesh-2-0-continued

Version 9.0.0.4.386.41994 Beta Version 2021/02/02 33.05 MBytes
ASUS Blue Cave Firmware version 9.0.0.4.386.41994 (Beta Version)
Security Fixed:
Fixed CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685, CVE-2020-25686

However, when we download and unzip the file. We get BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx.

Besides Northguy above, have any other brave Blue Cave users installed this version? If so, does it resolve some of the reported stability issues of the prior few releases?

I'd be curious to know if your are seeing the new AIMESH Tab in the ASUSWRT menu with this version installed on your Blue Cave as seen on my RT-AC88U (attached).

 

[chongaik3]

I'd be curious to know if your are seeing the new AIMESH Tab in the ASUSWRT menu with this version installed on your Blue Cave as seen on my RT-AC88U (attached).


View attachment 30622

Nope, if i remember correctly because i have revert to older version as i have problem with VoIP service using the latest version.

 

[litapajar]

I also got BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx after unzipping. Was really hoping it would bring the Blue Cave onto the 386 line, but it looks like that was a hasty typo on ASUS’ part.

Installed it a few days ago and have seen nothing but stability with an AX88U and AC68U mesh network. Then again, I hadn’t seen many issues with the Blue Cave as an occasional node prior to this.

I also got BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx after unzipping. It was so disappointing.

BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx firmware seems to the same one Lyra. I am not sure what's going on there? I wonder if we can use 386 version from another router e.g. RT-AC68U?

 

[Northguy]

I also got BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx after unzipping. It was so disappointing.

BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx firmware seems to the same one Lyra. I am not sure what's going on there? I wonder if we can use 386 version from another router e.g. RT-AC68U?

Do try and let us know the outcome

 

[Smedley]

As reported by chongaik3 in asuswrt-386-rc2-public-beta-with-full-functions-aimesh-2-0-continued

Version 9.0.0.4.386.41994 Beta Version 2021/02/02 33.05 MBytes
ASUS Blue Cave Firmware version 9.0.0.4.386.41994 (Beta Version)
Security Fixed:
Fixed CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685, CVE-2020-25686

However, when we download and unzip the file. We get BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx.

Besides Northguy above, have any other brave Blue Cave users installed this version? If so, does it resolve some of the reported stability issues of the prior few releases?

I'll answer my own question first, then ask another... Yesterday, I upgraded an associate's Blue Cave to 384_46629 and it has been stable thus far. I performed a full reset and reconfigured from scratch. I also upgraded the modem to a Arris DOCSIS 3.1 at the same time.

All works fine, but I cannot access the modem's UI through the router, however I can connect when directly hardwired to the modem (setting my IP to the same subnet).

I checked the Blue Cave's LAN subnet, but it appears fine at 255.255.255.0. Is there some setting I might have borked, or is this possibly a glitch in this firmware?

Thanks!

 

[OzarkEdge]

I'll answer my own question first, then ask another... Yesterday, I upgraded an associate's Blue Cave to 384_46629 and it has been stable thus far. I performed a full reset and reconfigured from scratch. I also upgraded the modem to a Arris DOCSIS 3.1 at the same time.

All works fine, but I cannot access the modem's UI through the router, however I can connect when directly hardwired to the modem (setting my IP to the same subnet).

I checked the Blue Cave's LAN subnet, but it appears fine at 255.255.255.0. Is there some setting I might have borked, or is this possibly a glitch in this firmware?

Thanks!

Wired to my RT-AC86U (192.168.1.1 and 255.255.255.0), I can browse my Arris SB6141 cable modem at 192.168.100.1.

Did you cycle power on both boxes?

OE

 

[Smedley]

Wired to my RT-AC86U (192.168.1.1 and 255.255.255.0), I can browse my Arris SB6141 cable modem at 192.168.100.1.

Did you cycle power on both boxes?

OE

Yes, after I factory reset the router, I power cycled both the router and modem.

I've never had a prior issue accessing a modem at 192.168.100.1 through the wireless connection. I know the modem UI is functional, as I can connect with a cable from my laptop directly to the modem. I've read dozens of google search results where people have had similar issues, but other than a bad subnet, the solutions seem random.

 

[Smedley]

OK, I'm baffled! Following a random post from a Google search, I changed the IP address of the Blue Cave from 192.168.0.1 to 192.168.1.1 and the modem's UI was immediately accessible via wireless. Why would the router at 192.168.1.1 provide access to the modem at 192.168.100.1, whereas 192.168.0.1 would not? The subnet remained at 255.255.255.0.

 

[Mcdull]

I also got BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx after unzipping. It was so disappointing.

BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx firmware seems to the same one Lyra. I am not sure what's going on there? I wonder if we can use 386 version from another router e.g. RT-AC68U?

No. Blue Cave uses Intel chips, while most Asus routers including AC68U use Broadcom chips.
I believe the new update, as said in the description, is just a quick patch for DNSmasq vulnerabilities.

 

[Mcdull]

I also got BLUECAVE_9.0.0.4_384_46629-g481b3fb.trx after unzipping. Was really hoping it would bring the Blue Cave onto the 386 line, but it looks like that was a hasty typo on ASUS’ part.

Installed it a few days ago and have seen nothing but stability with an AX88U and AC68U mesh network. Then again, I hadn’t seen many issues with the Blue Cave as an occasional node prior to this.

Saw you're using Blue Cave as AiMesh, have you noticed that Blue Cave altered the MAC address of devices connected wired or wirelessly to it?
(My setup was wireless AiMesh, not sure if it's the same with ethernet backahul)
e.g. MAC address shown up in main router is different if connected through Blue Cave than the device's real MAC address
Trying to confirm the issue I had here. I still wish one day Asus will fix that so I can use it in Living Room rather than other ugly Asus routers.

DHCP assigned IP issue with Blue Cave as AiMesh router

I just got a Blue Cave to replace an RT-AC68U as main router in a 3x RT-AC68U AiMesh. Then I'm seeing issue in getting manually assigned IP from DHCP: 1. if the devices are connected to the Blue Cave (main), they get the assigned IP 2. if the devices are connected to the other nodes, they get...

www.snbforums.com

 

[NSNE]

Saw you're using Blue Cave as AiMesh, have you noticed that Blue Cave altered the MAC address of devices connected wired or wirelessly to it?

I haven't experienced this issue myself. I just took a few minutes to cross-reference a couple random devices (e.g., Logitech Harmony Hub, iPhone 12 Pro) that were connected via Wi-Fi to the Blue Cave node, and their MAC addresses checked out. I used the Asus iOS app as well the router GUI to view the devices that were connected to the node. Are you seeing the incorrect MAC reported for all devices or just select ones?

Granted, as you mentioned, my Blue Cave is connected via Ethernet to my AX88U. That might have an effect. But I had my BC connected wirelessly for a time, too, and didn't observe the odd MAC behavior then.

 

[Mcdull]

I haven't experienced this issue myself. I just took a few minutes to cross-reference a couple random devices (e.g., Logitech Harmony Hub, iPhone 12 Pro) that were connected via Wi-Fi to the Blue Cave node, and their MAC addresses checked out. I used the Asus iOS app as well the router GUI to view the devices that were connected to the node. Are you seeing the incorrect MAC reported for all devices or just select ones?

Granted, as you mentioned, my Blue Cave is connected via Ethernet to my AX88U. That might have an effect. But I had my BC connected wirelessly for a time, too, and didn't observe the odd MAC behavior then.

In my case, all wireless or wired devices connected to Blue Cave will get the same first 3 Hex values (which will also change after restarting) in the MAC Address. So, basically using DHCP assigned IP is impossible.
It's pretty obvious in the table when a few devices having the same prefix in MAC addresses.
(and in this thread DHCP assigned IP issue with Blue Cave as AiMesh router | SmallNetBuilder Forums (snbforums.com)
I had 2 screen caps showing my Door Bell got DA:50:E6:25B:83 and canon printer got DA:50:E6:D8:31:36

Might be it happens only when Blue Cave is using wifi in AiMesh. I've noticed Netgear extenders did this when using with AC-68U, might be the implementation of AiMesh in Blue Cave has some wifi extender thing in it.

 

[sleepy]

Besides Northguy above, have any other brave Blue Cave users installed this version? If so, does it resolve some of the reported stability issues of the prior few releases?

I've had it installed since april 24th rebooting every 48 hrs. i have no issues to report with the wifi not restarting on boot. and both of the previous firmwares did have that problem for me.

 

[chongaik3]

Hi all, FYI. 384 version out. Only fix iOS login issue

 

[L&LD]

What is 'officially' stated is never the 'only fix'.

 

[chongaik3]

Because previously is Beta version. So i called it official