Simple task: 3 wired IP devices needed to be connected to a client (non Mikrotik) WLAN. I use CAP Lite (v6.48.7) and a non managed simple switch connected too ETH1. Client network is 192.168.1.1/24. Important, I need to access my 3 devices from the WLAN. Each has a fixed IP address, so DHCP is not necessary to work over the wireless link.
What works:
CAP Lite connects to WLAN (SSID, passowrd) correctly.
The IP address of the bridge is 192.168.1.200
Behind my switch, everything works. So my PC connected to a simple (non-managed) switch, it is connected to CAP lite ETH1. My PC has 192.168.1.60. From the PC, I can bowse the internet, ping everything (google, etc.). However from the WLAN I cannot see neither my PC IP address (192.168.1.60) nor the IP address of the bridge (192.168.1.200)
How is it possible?
And because of this, from the WLAN I cannot connect to the 3 devices behind the CAPS lite and its ETH1 port. I wanted to set this up with NAT. But for that, I need to be able to see at least the IP address of the CAP lite.

This is my config:

# jan/04/1970 04:45:55 by RouterOS 6.48.7
# software id = Z9WL-KD9D
#
# model = RBcAPL-2nD
# serial number = HER094JDC5W
/interface bridge
add name=bridge
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n country=hungary disabled=no \
mode=station-pseudobridge ssid=_____
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk,wpa2-eap mode=\
dynamic-keys supplicant-identity=MikroTik wpa2-pre-shared-key=______
/interface bridge port
add bridge=bridge interface=all
/ip address
add address=192.168.1.200/24 interface=bridge network=192.168.1.0
/ip route
add distance=1 gateway=192.168.1.1
/system identity
set name="RouterOS CAP Lite"

However from the WLAN I cannot see neither my PC IP address (192.168.1.60) nor the IP address of the bridge (192.168.1.200)

I understand the non-MT wifi is the AP. The CAP Lite is a station, connected via wifi to the AP

1. It looks like your non-MT WLAN is not allowing inter-client communication (like MT does with wifi forward disabled). So one WLAN client cannot see the other WLAN client.
2. Next problem will be the pseudo-bridge MAC translation table, that will need the client device behind the pseudo-bridge to communicate first (to add the corresponding MAC-translation entry in the pseudo bridge table)


As a test, connect the CAP Lite as a regular station (not station-pseudobridge) and see if you can reach the CAP Lite from your test-point (PC on wifi WLAN?)