My take on this is that both processes, Netinstall and "Reset to Default after Upgrade", use exactly the same *.npk files in order to write new system and default configuration files to the HDD. [...] It's up to you, you can go with "reset to config" any time you want. But I'll ...

During an initial migration of RB4011 from Ros6 to Ros7 (years ago), there was some issue even though everything was apparently still working. From time to time during one v7 update, RB4011 failed to reboot properly, but I simply initiated a reboot on my own. Did you, following an upgrade, reset th...

@mkx @infabo With respect, both of you appear to agree that confidence in the effectiveness of Netinstall is based upon empirical reports, and that nobody outside Mikrotik knows definitively the details of how it works. My take on this is that both processes, Netinstall and "Reset to Default af...

I've now started using the following process whenever I upgrade the software on my AX3 and AX2:- 1) Export the script file of the current configuration 2) Download and install the upgraded software, reboot 3) Upgrade Routerboard (not reboot) 4) Reset to default configuration, keeping users, and run ...

*) ipv6 - fixed IPv6 RA delay time from 5s to 500ms according to RFC;

Upgraded hAP AX^3 from ROS 7.11.2 to 7.12, and upgraded the firmware, but IPv6 RA Delay Time still shows as 3 seconds and cannot be changed to 500ms. The parameter in ND only accepts seconds. Have I missed something?

Confusion resolved and now looking straightforward.

Thank you very much.

Sorry, I should have stated the connection between AX2 and AX3 will be by ethernet.

It appears that, under WifiWave2, multiple clients of the AX2 WAP will all pick up IP addresses, routing information, etc. Hence there is now no need for ap-bridge mode?

Thank you.

Given there is no ap-bridge mode in WifiWave2, is that now irrelevant for this use case?

I'm currently running an AX3 as a straightforward domestic router/ap, with a DHCP client on Eth1 and all other interfaces bridged. I now want to configure an AX2 device to operate as a switch/WAP on the AX3 LAN subnet. Having read available articles I have become confused because they all assume the...

But then you need to be careful that Windows Update does not replace it with the dumbed-down driver lateron. A small point but I recently came across this programme that solves the issue of windows update overwriting newer/better drivers, Windows Update Mini Tool (WUMT). It was written by "stu...

You are correct. My default was "LAN" and I can only offer memory lapse as an excuse.

It doesn't affect the solution, however.

Thanks
--
Renfrew

I recently received an hAP ax^3, and immediately updated the software to v7.8 as recommended in the documentation. I cannot therefore say whether the problem I found is specific to ROS 7.8. Problem I've a Gigaset N300IP attached to an ethernet port on the router which worked as expected when first c...

On version 6.48.6, under firewall/connections/tracking, the udp stream timeout was 3 minutes. The default udp stream timeout is still the same on upgrading my rb951g to version 7.5. Perhaps you could double-check that the udp stream timeout has not changed.

viewtopic.php?t=165563

Thank you.Fairly obvious when you know it!

Stupidly, when I installed v3.30 I forgot to keep a copy of v3.29. I reported the issues with columns to support on Thursday but their software archive doesn't have copies of previous version of winbox, that I can find. Could someboy kindly point me to a trustworthy site for downloading v3.29 ? Many...

I have reverted to Winbox v3.21 and everything now OK for Malwarebytes. Besides, the interface is more stable (zoom issues on laptop screen) than v3.24

Today, Malwarebytes (v4.1.0) running on Windows 10 Pro (v1909) has flagged Winbox (v3.24) as being malware, and quarantined the winbox64.exe file. I suspect that this is a false positive because I have been using that version of Winbox for a few days but only today has it been flagged. For informati...

I have been plagued for a long time with an issue whereby Win10 WiFi clients cannot renew their IPv6 connection, after having first been assigned an address via SLAAC. This problem only affected Win10 laptops connecting via WiFi to a RB951G-2HnD. IPv6 connections via ethernet work as expected, as do...

There is one further issue. The DHCPv6 client needs to be able to receive UDP packets on Port 546 through the relevant interface, and your firewall configured as necessary.