Pseudobridge or Pseudobridge clone not work -> dhcp client in searching

It’s a problem that happens to me at least once a week

I have this setup:
1 Wi-Fi Access Point standard 802.11 Wi-Fi (NOT MT)
1 MikroTik like mAP in “station pseudobridge” mode or “station pseudobridge clone”, with Wi-Fi and Ethernet bridged
1 or more device/s with only ethernet port (not wifi)

With some APs this setup works very well, in some cases the MT device connects but the DHCP is waiting for IP addresses.

I tried to disable RSTP on bridge as suggested here: http://forum.mikrotik.com/t/station-pseudobridge-not-working-with-hap-ax2-and-hap-ax3/169646/1

I tried to apply also this change:

 /interface bridge nat add chain=dstnat mac-protocol=ip ip-protocol=udp src-port=67 dst-port=68 action=dst-nat to-dst-mac-address=FF:FF:FF:FF:FF:FF

As suggested here: http://forum.mikrotik.com/t/dhcp-lease-over-wireless-bridge-does-not-work-for-ethernet-clients/138721/1

In some cases it works, in others it doesn’t.

Since I only want to use Mikrotik devices, I wonder, but is it possible that a solution has not been found for years and that I have to buy bad repeaters/ extenders like tplink dlink ect?
Economical devices that always work with any AP and brand…
Can’t Mikrotik fix such a trivial function?

Does it really need to be bridged?

Putting the wired client(s) behind a Nat would be good.

but I need the devices to be in the same LAN and to be able to access.
Am I forced to use tplink or similar?

You could also try turning off bridge fastpath in bridge setting
That caused me some issues a long time ago.

Thanks for the replies. simply the “station pseudobridge” mode" and “station pseudobridge clone” features are buggy and don’t work.
I had been warned, but I didn’t want to believe that such a trivial feature MK wouldn’t be able to fix it

Since this is only a user forum, please help others by reporting bugs directly to MikroTik by emailing support@mikrotik.com or opening a ticket at their service desk: https://help.mikrotik.com/servicedesk/servicedesk.

Station pseudobridge is a setup, whereas multiple clients at the “station pseudobridge” device side need to reach the other end of the network. Since a “station pseudobridge” wireless device will share its mac address with those devices behind it by using a kind of MAC NAT service, DHCP will have it’s troubles! Behawer that station pseudobridge will deliver you with layer 2 and layer 3 support but no DHCP, and that is fairly simple to understand since for the access point, the client interface has only one mac address and thus one IP delivered by the DHCP server at the access point side of the network lease (mac address to IP bind). Remember that station pseudobridge is only used for setups where the access point is not a mikrotik and you need to extend your network to more than one device at the other end. I really don’t think there is any kind of bug here. This is how it works!

Just use static IP’s for those devices behind the station pseudobridge; don’t forget to exclude them from the DHCP pool.
You can also make use of DHCP server at station pseudobridge-side device with ip pool different from access point dhcp server side.
Ex:

Access Point dhcp server side: pool 192.168.1.100-150
Station Pseudobridge dhcp server side: pool 192.168.200-250