Mode station
This is standard mode that does not support L2 bridging on station - attempts to put wireless interface in bridge will not produce expected results.
If the other device was a Mikrotik, you could use station-bridge, but since it is a dlink, you can only use station-pseudobridge.
It will pseudo-work, obviously, from the same page linked above:
Mode station-pseudobridge
From the wireless connection point of view, this mode is the same as standard station mode. It has limited support for L2 bridging by means of some services implemented in station:
MAC address translation for IPv4 packets - station maintains IPv4-to-MAC mapping table and replaces source MAC address with its own address when sending frame to AP (in order to be able to use 3 address frame format), and replaces destination MAC address with address from mapping table for frames received from AP. IPv4-to-MAC mappings are built also for VLAN encapsulated frames.
single MAC address translation for the rest of protocols - station learns source MAC address from first forwarded non-IPv4 frame and uses it as default for reverse translation - this MAC address is used to replace destination MAC address for frames received from AP if IPv4-to-MAC mapping can not be performed (e.g. - non-IPv4 frame or missing mapping).
This mode is limited to complete L2 bridging of data to single device connected to station (by means of single MAC address translation) and some support for IPv4 frame bridging - bridging of non-IP protocols to more than one device will not work. Also MAC address translation limits access to station device from AP side to IPv4 based access - the rest of protocols will be translated by single MAC address translation and will not be received by station itself.
This mode is available for all protocols except nv2 and should be avoided when possible. The usage of this mode can only be justified if AP does not support better mode for L2 bridging (e.g. when non-RouterOS AP is used) or if only one end-user device must be connected to network by means of station device.
It is not "true" L2 bridging, but it should work fine for IPv4 based protocols bridging.
Just changed the router configuration to Pseudobridge, still i am not able to ping dlink router from the PC connected to Mikrotik router. Any other configuration to be done other than below configuration while using Psuedobridge?
below is the configuration,
# 2025-10-09 11:04:11 by RouterOS 7.20.1
# software id = FK6D-W2ZG
#
# model = C53UiG+5HPaxD2HPaxD
# serial number = <mod edit>
/interface bridge
add name=my_bridge
/interface wifi
# SSID not set
set [ find default-name=wifi1 ] configuration.mode=ap disabled=no
set [ find default-name=wifi2 ] channel.band=2ghz-n .skip-dfs-channels=disabled \
configuration.country=India .mode=station-pseudobridge .ssid=D-Link_123 \
disabled=no security.authentication-types=wpa2-psk
/interface bridge port
add bridge=my_bridge interface=wifi2
add bridge=my_bridge interface=ether1
/ip dhcp-client
add interface=my_bridge
/ip dns
set allow-remote-requests=yes
Hi,
You usually need to disable rstp on the Mikrotik bridge when using pseudo mode (strictly only on the wifi interface) I got told why once but couldn't really understand the explanation but I have found it doesn't work if you don't disable it (RSTP).
The config looks fine to me.
The DHCP client receives address 192.168.1.33/24 and the route 0.0.0.0/0 with gateway 192.168.1.1.
The routes are fine, the DAd one comes from the DHCP and the DAc from the address assigned to the bridge.
The 192.168.1.1 is the d-link that is both AP and gateway?
Can you ping (on the Mikrotik) an internet address?
What is the error when you ping to 192.168.1.1 on the PC?
What happens if you run on the PC a traceroute to the gateway (i..e. tracert 192.168.1.1) or to an internet address?
Could it be some setting (multiple interfaces/firewall/whatever) setting on the PC or on the d-link?
You can also try with mode station-pseudobridge-clone, but I don't think it will change the situation, the Mikrotik settings seem correct to me.
@rplant
Is this a v7.x thing?
I have a very similar setup on a hap lite used as station towards a tp-link AP, but it is running v 6- wireless, not wifi.
Anyway, it costs nothing to try disabling it.
Should be:
/interface bridge set [find name=my_bridge] protocol-mode=none
to disable it on the whole bridge while to disable a single interface one neds to set the specific port as "edge", right?
So that should be:
/interface bridge port set [find bridge=my_bridge interface=wifi2 ] edge=yes
?
but I have found it doesn't work if you don't disable it (RSTP).