@duxgavin, Wi-Fi 7, and thank you for the device output
That /interface wifi print was exactly what was needed, and it corrected us on something we had wrong.
Our catalogue had the hAP be³ Media as wifi1=5GHz, wifi2=2.4GHz. Your device says otherwise:
1 wifi1 .band=2ghz-n
2 wifi2 .band=5ghz-be mld-interface=mld1
3 wifi3 .band=6ghz-be mld-interface=mld1
So wifi1 is 2.4, not 5. Fixed, and that model is now marked verified rather than derived from a spec sheet. The 6 GHz radio had also been missing entirely from our data, and the be lite had the wrong port count (it is one 2.5G plus three 1G).
MLO is in, built from your configuration rather than from my reading of the manual:
/interface wifi security
add authentication-types=wpa3-psk name=sec-mlo passphrase=... wps=disable
/interface wifi datapath
add bridge=bridge name=dp-mlo
/interface wifi configuration
add country=... datapath=dp-mlo mode=ap name=cfg-mlo ssid=MT-Home security=sec-mlo
/interface wifi
add comment="genconf: MLO group" configuration=cfg-mlo disabled=no mld-name=mld1 name=mld1
set wifi2 mld-interface=mld1
set wifi3 mld-interface=mld1
It only appears on 802.11be hardware with more than one radio, forces WPA3, puts the datapath on the MLD interface since that is the forwarding point, and defaults to leaving 2.4 GHz out of the group for exactly the reason you gave: that band is there for older and IoT clients, which gain nothing from MLO.
@rextended, three of yours
The MikroTik default firewall is now an option. Firewall section, first choice. Picking it emits 43 rules taken verbatim from MikroTik's published router-mode default configuration, defconf: comments and all, with none of ours mixed in. That took two attempts: the first still leaked our RAW bogon rules and the IPv6 section added a second copy of the IPv6 filter on top. A "stock" firewall quietly containing half our opinions would defeat the entire point.
This also settles the defconf naming argument. Those rules genuinely are the defaults, so defconf: is the honest label there, which is what jaclaz wanted, without breaking your rule that defconf must mean the real thing. Anything the tool writes itself stays genconf. The two positions turn out to be compatible once there are two rule sets.
The IPv6 firewall is now always generated. You were right and this was the worst thing in the thread. Our IPv6 section defaulted to off, and the entire module was gated behind it, so anyone who simply never opened that section got a device with an empty IPv6 filter table. Safe until something brings the stack up, and then wide open.
It is now emitted unconditionally, verified across every case that previously produced nothing: IPv6 section off, IPv6 on with its firewall off, the stock firewall with no IPv6, and roles that never mention IPv6 at all. Exactly one block in each, never two. There is no opt-out toggle, because a switch labelled "remove IPv6 protection" is an invitation. It is not silent either: a configuration that does not use IPv6 is told why the rules are there, since unexplained rules get deleted by whoever reads them next.
On band=, I have not touched it and I would rather ask than guess. You raised that specifying a band may restrict the radio to that standard rather than merely setting the operating mode. The wifi package manual says band "defaults to newest supported standard", which supports your point that specifying it may be unnecessary. duxgavin's device does show band=5ghz-be in use, so it is not fatal. But if selecting 5ghz-be excludes older clients, then our long standing 5ghz-ax has been excluding a/n/ac clients on every AP we have ever generated, which would be a significant bug. Do you know whether that restriction applies to the wifi package as it does to the legacy driver?
Your bridge MAC one-liner is elegant, and the loop over every bridge is better than our per-device approach. Noted for when we support multiple bridges properly.
@jaclaz, three of yours
Token order is now alphabetical everywhere. You were right that it was inconsistent, and rextended was right that alphabetical is the order. Output is now:
add action=accept chain=input comment="genconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="genconf: drop invalid" connection-state=invalid
which matches an export line for line. That change touched every generated line and broke 21 test assertions, all of which were expectations about ordering rather than behaviour. Several were brittle in a second way, assuming adjacency, since comment= now sorts between things. Worth it for the reason you gave: a reordered line reads as a changed line in any diff.
The spaces around = in the preview: mitigated, but I could not reproduce it. Both previews here copy as name=bridge via the normal path, and the Copy button was never affected since it copies the script text rather than the rendering. But your output, add name = bridge protocol-mode = none with doubled spaces and spaced equals, is precisely the signature of a copy inserting whitespace at every inline element boundary, which some browsers do. The = is now inside the key's span instead of sitting between two spans, which halves those boundaries, so the worst case becomes extra spaces between tokens rather than a broken =. That is a mitigation for an inferred cause, not a confirmed fix. If you still see it, tell me which browser.
The MikroTik default firewall option is in, as above. And thank you for updating Compare_config to treat genconf as equal to defconf, and for linking the tool from it. To confirm publicly: genconf is a stable label. It will not be renamed. If we ever need another tag it will be an addition, not a rename of this one.
@luxyves, thank you, glad it is useful.
Test suites after all of the above: 1172 generate, 84 multi-device, 132 import. Every item has a regression test, including the ones that were only findable because someone here tried the thing on real hardware.