No ... it seems to be the same version related to the bad HNAP implementation which allowed the password to be reset ; in the EU apparently D-Link decided to seed the "beta" to the automatic update servers . It's nice they've added WPA3 option and also option to no longer use WPA as that has been unsecured for a long time ( you couldn't choose only WPA2 before)
Here is the version.txt output:
Firmware External Version V1.30
Firmware Internal Version: V1.30B06
Date: 2020-04-21 09:55:49
Checksum 23568AA5
Kernel linux 3.10.14 2020-04-21 09:55:49
HNAP Version 0202
WAN MAC: 28:3B:82:xx:xx:xx
LAN MAC 28:3B:82:xx:xx:xx
2.4GHZ WLAN MAC 28:3B:82:xx:xx:xx
5GHZ WLAN MAC 28:3B:82:xx:xx:xx
2.4GHz country code EU 1,2,3,4,5,6,7,8,9,10,11,12,13
5GHz country code EU 36,40,44,48,52,56,60,64,100,104,108,112,116,132,136,140,149,153,157,161
Firmware variant Default
2.4GHZ SSID
5GHZ SSID
There are still some issues with it however :
1. After a few min of inactivity the VPN connection stops any packets transmission even though the VPN link is stil up
2. Even though the 5 GHz channels 52,56,60,64 are listed as available in the version.txt summary in the actual Wifi Settings configuration page the available options to choose from manually skip from 48 straight to 149 ( 52,56,60,64,100,104,108,112,116,132,136,140 are missing ) even though DFS is enabled and I'm nowhere near an active radar ( https://imgur.com/ikNDRQI ) . Might be normal for DFS/TPcchanels to only be available via Auto and not manually but it never chooses these channels
3.The router still checks @ UTC 00:47 every night for updates even though it's configured not to do it.
Syslog of nightly check:
2020-06-03 03:47:25 FOTA_CONFIG[28805]: mtk/fota_generate_config.c, main, 1064:
2020-06-03 03:47:25 FOTA_CONFIG[28805]: Execute config ACTION: config.
2020-06-03 03:47:25 FOTA_CONFIG[28805]: mtk/fota_generate_config.c, action_config, 779:
2020-06-03 03:47:25 FOTA_CONFIG[28805]: Now start generating the configuration file.
2020-06-03 03:47:25 FOTA_CONFIG[28805]: mtk/fota_generate_config.c, main, 1072:
2020-06-03 03:47:25 FOTA_CONFIG[28805]: Done.
2020-06-03 03:47:26 FOTA[28804]: fota_api_curl.c, get_http_response_code, 167:
2020-06-03 03:47:26 FOTA[28804]: iHttp_code=401.
2020-06-03 03:47:26 FOTA[28804]: fota_api.c, refresh_access_token, 214:
2020-06-03 03:47:26 FOTA[28804]: Now REFRESH the access token.
2020-06-03 03:47:27 FOTA[28804]: fota_api_curl.c, get_http_response_code, 167:
2020-06-03 03:47:27 FOTA[28804]: iHttp_code=200.
2020-06-03 03:47:27 FOTA[28804]: fota_api.c, refresh_access_token, 248:
2020-06-03 03:47:27 FOTA[28804]: REFRESH the access token success.
2020-06-03 03:47:28 FOTA[28804]: fota_api_curl.c, get_http_response_code, 167:
2020-06-03 03:47:28 FOTA[28804]: iHttp_code=200.
2020-06-03 03:47:28 FOTA_OUTPUT[28825]: mtk/fota_output.c, main, 339:
2020-06-03 03:47:28 FOTA_OUTPUT[28825]: Now processing the result of ACTION: auto.
2020-06-03 03:47:29 FOTA_OUTPUT[28825]: mtk/fota_output.c, handle_action_auto, 85:
2020-06-03 03:47:29 FOTA_OUTPUT[28825]: 'pUpdate_done_notify' is null pointer.
2020-06-03 03:47:29 FOTA_OUTPUT[28825]: mtk/fota_output.c, main, 344:
2020-06-03 03:47:29 FOTA_OUTPUT[28825]: The value of 'iRet' is not OK.
4 . still can't use 443 for Port Forwarding to a personal Web Server even though the router's remote management port has been changed to some other port or has been disabled entirely .
5. Scaling in the statistics tab still way off