MikroTik

Hi all,

I think I'm getting crazy. I got a brand new hAP ax3 C53UiG+5HPaxD2HPaxD device.
I created a new bridge in default configuration and added the wifi2 port to this bridge. Then I created a dhcp-client for this bridge.
After I configured the wifi2 in mode station, the connection goes up and I think all fine.
But I didn't get an IP adresse from the dhcp server.

Things I tried:
Used an other ssid (mikrotik ap with dhcp server) with the same result.
When I removed the wifi2 from the bridge and changed the dhcp-client directly to the interface I got an ipaddress.
I've wondered, when I add the wifi2 back to the bridge - the MTU size of the bridge didn't automaticaly reduced to the MTU size of the wireless connection, but the wireless connection is already up.
Software Version 7.7 and 7.8 tested without change.

Any idea what happened?
Any necessary informationen needed?

Thanks to all answers.

Is normal with current wifiwave2 setup.
https://help.mikrotik.com/docs/display/ROS/WifiWave2

Lost features
The following notable features of the bundled wireless package do not yet have equivalents in the wifiwave2 package

Station-bridging or other 4-address modes
Nstreme and Nv2 wireless protocols

Drop the second bridge, leave wifi2 in station mode.

Thank you for the fast answer and helpful info my friend!

a little question to that: Is it possible to use the new wireless chip with the old wireless package, even I know to lose the AX features?

Nope.
That's impossible.

Okay thanks again.
Topic is solved

I bought a hAP ax3 specifically for this purpose, to use it as a wireless station to share the WiFi through the Ethernet ports with devices without WiFi capabilities and encountered with the same issues "namex" found.

As "namex" said it works if I remove the wifi2 interface from the bridge and use it as a WAN interface but I don't want to double NAT.
Ideally I just want the wifi2 interface in station mode LAN bridged with the Ethernet ports.

Is there any way I can achieve this?

Ax to ax, yes you can.
Ax to legacy, nope. Not possible in an easy way.
It CAN be done if you put something like EOIP over both ax/ legacy endpoints but that's not really standard setup.