I’m used to a hapAC2, but new to WiFi Wave2 on a hAPax3. I’m experiencing something which makes no sense and feels like a bug, but might just be my unfamiliarity. Both Wifi1 and Wifi2 are bound to the bridge, but the hosts table shows devices on Wifi1 as an unknown port, but Wifi2 is correct!
To eliminate configurations errors, I went back to basics, accepted the default configuration, but changed country to UK and followed the various firewall stages. Everything worked pretty much out the box. Wifi Settings are:
I notice after I’ve run both commands, when I check the configuration, WiFi1 has datapath.bridge=bridge automagically added, but WifI2 does not(!). I don’t know why this is different, but it’s repeatable:
It’s naughty to reply to my post, but it looks like a bridge or Wifiwave2 bug (or perhaps a hardware fault on a batch), rather than something I’m doing wrong, because a refined search shows up other users with this issue all without a resolution.
Thanks holvoetn. I’ve not contacted support yet, because I started with the assumption it was my ignorance causing the issue. The fact you don’t experience this makes me think it is something obscure in my settings, so I’ll go back over them and start from default again. If I reproduce the effect I’ll log a support call. It might be (e.g.) a hardware issue.
What I do find strange is that using identical SET commands (adjusted obviously for the different channels) produces a different outcome - namely the “datapath.bridge=bridge” setting that appears in Wifi1 that’s not there in Wifi2. The GUI confirms there is a different outcome…
Hi ToTheFull - thanks this is helpful. I’d not run the print detail command, so had not seen the *FFFFFFFF identifier before, but now I’ve run it I get the same as you. I’m planning to reinstall via netinstall, build the simplest working config possible and check. If I’ve still the issue I’ll log a call, but even more likely I’ll just return the hAPax3 and live with the hAPac2, since the former has been a lot more bother than benefit.
> interface/bridge/host/print detail
Flags: X - disabled; I - invalid; D - dynamic; L - local; E - external
0 D mac-address=xx:xx:xx:xx:xx:01 interface=ether2 bridge=bridge on-interface=ether2
1 D mac-address=xx:xx:xx:xx:xx:02 interface=ether3 bridge=bridge on-interface=ether3
2 ID mac-address=xx:xx:xx:xx:xx:03 interface=*FFFFFFFF bridge=bridge
3 D mac-address=xx:xx:xx:xx:xx:04 interface=ether5 bridge=bridge on-interface=ether5
4 DL mac-address=xx:xx:xx:xx:xx:05 interface=bridge bridge=bridge on-interface=bridge
5 DL mac-address=xx:xx:xx:xx:xx:06 interface=ether3 bridge=bridge on-interface=ether3
6 IDL mac-address=xx:xx:xx:xx:xx:07 interface=*FFFFFFFF bridge=bridge
7 DL mac-address=xx:xx:xx:xx:xx:08 interface=wifi2 bridge=bridge on-interface=wifi2
8 ID mac-address=xx:xx:xx:xx:xx:09 interface=*FFFFFFFF bridge=bridge
9 D mac-address=xx:xx:xx:xx:xx:10 interface=wifi2 bridge=bridge on-interface=wifi2
10 ID mac-address=xx:xx:xx:xx:xx:11 interface=*FFFFFFFF bridge=bridge
11 ID mac-address=xx:xx:xx:xx:xx:12 interface=*FFFFFFFF bridge=bridge
12 D mac-address=xx:xx:xx:xx:xx:13 interface=ether5 bridge=bridge on-interface=ether5
13 ID mac-address=xx:xx:xx:xx:xx:14 interface=*FFFFFFFF bridge=bridge
I have used Netinstall to re-install the routeros and wifiwave2 packages and now the bridge tables and interfaces are correct. So it’s not a bug or hardware but perhaps something in the initial install or something I mistyped that caused the issue. When I did the first install, I renamed the bridge, but later changed it back. I don’t know if there is something strange in the way wifiwave2 talks to the routeros bridge code and expects the name to never change…
Thanks for letting us know thats very useful, would be nice to know what caused the problem but I’ll take the fix, but I see it more of an irritation so not that worried about it. Did you try an old config or just go straight for a fresh one ?
I accepted the default config and used Quick Set to set it up as a “home dual AP” (out of laziness). I then copy and pasted some useful stuff from the old config (such as DHCP leases). Finally I added a few firewall basics and logs. I was keen not to get too far away from default, since I can’t tell if it’s something I did wrong.
For my first installation (which caused the interface=*FFFFFFFF issue) I naively took a gamble on importing an ac2 export, but it didn’t work for the WiFi stuff because WifiWave2 is a different syntax. This might have set something wrong somewhere, but manually checking through a verbose export (of the ax3) showed nothing suspicious.