New firmware version 4.7 being released for beta testing

Technical Support for Routers
92

Oh Yeah !! I want it too :wink:

3 Likes
93

Looks like corn job🤔
Good idea but iot need to be WiFi on for cctv, doorbell, rule with wifi smart things.. (wifi plugs if motion detected)

1 Like
95

Thank you for your feedback, we have taken note of your request and will consider it carefully.

4 Likes
96

I upgraded from 4.6.4, keeping settings. I am in AP mode. I found luci is no longer accessible. I saw this in the log:

Mon Oct 7 22:04:04 2024 daemon.err uhttpd[28689]: getaddrinfo(): Name does not resolve
Mon Oct 7 22:04:04 2024 daemon.err uhttpd[28689]: getaddrinfo(): Name does not resolve
Mon Oct 7 22:04:04 2024 daemon.err uhttpd[28689]: Error: No sockets bound, unable to continue
Mon Oct 7 22:04:04 2024 daemon.info procd: Instance uhttpd::instance1 s in a crash loop 6 crashes, 0 seconds since last crash

If I restart uhttpd I get the same thing.

100

Hi
May I know what screenshot of the error message?
Please try to unbind it, reset to factory settings and re-bind it.

101

After upgrading from 4.6.4 to 4.7 the new cloud icon on first page says all is connected.
But after a firmware reset (on 4.7) entering my Goodcloud credentials on new icon fw responds connected but dialog box remain unchanged with credentials. If i exit cloud icon remain with a dot (=unconnected).
Entering Goodcloud router is bound properly and i can see it.

1 Like
102

Hi,

The firmware version is 4.7.0 2024-09-30, have not reproduced this issue.
Please check if the 'Settings Page' URL in the GL GUI is [GatewayIP]:3000?

image
image1872×928 67.4 KB

image
image1403×520 34.1 KB

103

Please PM me the router syslog when it connects (even failed) to the GoodCloud, and the Device ID/Device MAC/Device S/N.

104

There were no changes in the adguardhome port. Could you test using the Mulvad browser browser?

105

image
image1400×1006 74.5 KB

with the default settings of the Mullvad Browser... Maybe check what security settings you have set

106

Thanks for the suggestion but unfortunately not working still. Here is the screenshot:

Bind Failure
Bind Failure1629×715 124 KB

107

So...I just upgraded from Beta2 to Beta3 on my MT6000. Performance was sluggish, including the local LAN and the internet connection. It disconnected randomly. When I tried to run a speed test, my normal 25ms ping was more than 2700ms. I am using Adguard home and have a Wireguard client running (Windscribe). I had to reboot a couple of times to get it to accept the Beta2 file and commit it. Once it did, I had to manually reboot and it came up with Beta2. It's working normally again. There's something in the new Beta that my setup doesn't like.

108

Please PM me your router device ID, MAC, SN, and your syslog when it is connecting to the GoodCloud.

109

When will ipv6 features be finished?

1 Like
110

IPv6 for what features?

Now Supported IPv6 for LAN and WAN.

111

Router states:

The current version of the firewall, VPN, terminal list, cloud service, etc., may not support IPv6 for the time being. Therefore, the IPv6 function can only be used for configuration within this interface.

1 Like
112

Can the 4.7.0 be implemented in openwrt 24 version to?

4 Likes
113

Package system is broken in beta 4, or your back end is down. Unable to update package list in beta 4 worked in 2 and 3. Unable to get SQM and netdata re-installed after upgrade keep settings

114

I just migrated from beta 3 to 4 and I am seeing the package list. I kept the settings as well.

115

Packages update fine for me as well