I connected with WINBOX and opened a terminal followed by:
/system reset-configuration
Waited some time and closed and reconnected with WINBOX.
[admin@RouterSwitchAP] > /interface wireless security-profiles set [ find default=yes ] authentication-types=wpa2-psk mode=dynamic-keys wpa2-pre-shared-key="TestWifi123"
expected end of command (line 1 column 57)
So the first command already fails. Should this work with “RouterOS 7.7” ? What did I do wrong that the first command already fails?
This makes me wonder if the rest of the commands will work? Or is this mentioned guide not for my device/routeros version?
Use the GUI, learn CLI on the side, otherwise you will take 5 years to config your router from what is NOT a purpose built guide to install a complete config on a router but a concept for how to use VLANS. No one here is going to answer your every question as every input line you attempt may or may not work as desired…
A full export (minus serial, WANIP, yada yada ...) might be needed here to see what has been done.
OP is using a stable version but there are stable/beta/rc versions where some settings are only available via CLI.
Just saying.
While that guide from pcunite is still GOLDEN as base material, it might be useful to make a ROS7/Wifiwave2 version of it.
Especially since more and more AX devices are going to come out moving forward.
Not everyone is going to be able to translate easily from legacy wifi to wifiwave2.
This is a “quick and dirty” way of doing it. A more proper way of doing it would be using the various profiles (e.g. create a profile under /interface/wifiwave2/security) and then use those profiles where ever they apply. This makes possible to use exactly the same settings (e.g. same set of SSID,PSK,authentication types,…) on multiple wireless radios, be it local radios on different band (2.4GHz, 5GHz) or on CAPsMAN managed radios or a mix of the two.
The above examaple translated to a more proper config example:
Question to not using the mentioned “profiles”. If I understand it right, they help with quickly reusing the settings as you explained.
But it is not a security risk or wrong config if someone is not using them, right?
No, not a problem per se.
But it will make your life a bit easier when being used consistently and when using something like capsman (it uses more or less the same settings).
It’s more “clean” if you want.
The thing to really avoid is to mix both styles. Then you can be chasing your own tail when looking why a certain setting does not work as you intended (since direct config has preference over profiles).
So yes, you can config everything directly on the interface if you want.
Disgree with MKX,
WiFIWAVE2 has nothing to do with setting up vlans.
That is the beauty of NOT corrupting wifi profiles with vlans and handling it all cleanly through /interface bridge port and /interface bridge setting.
In otherwords article does not need an update…
Suggesting, Holvoe help MKX with a Wifi Wave 2 Setup User Article…
I suspect only the best quality too!!
I beg to differ …
I never said that a guide to wifiwave2 configuration should be part of excelent tutorial on VLANs by @pcunite … I only agreed that a guide to wifiwave2 is needed.
It seems you have difficulties with understanding the world around you. Like: the white stuff falling off the skies during the winter … that’s not ice cream.
I never said I would write the guide to wifiwave2 configuration … I only agreed that a guide to wifiwave2 is needed.