My thoughts.
Sorry for the amount of text.
Assumes a moderately recent router OS. (v6 or v7)
- If what you mostly want is internet. Use a Routed/Natted wireless connection. This is reliable under almost all conditions.
From a default configuration. (Using winbox)
If needed you can (carefully) use quickset to change the IP address range of the hap.
You will likely need to disconnect and reconnect your PC’s network connection
after changing it to get the dhcp client on your Computer to update.
After this
Remove the WLAN from the bridge. (bridge port)
Set the WLAN up to connect to the Access Point, use station mode.
Put an IP DHCP Client on the WLAN interface, perhaps make its default route distance 2.
Add the WLAN to the WAN interface list. (So traffic exiting via the WLAN gets NATTED) Interface / Interface List
You should now have a dual wan configuration on the HAP. (ether1, and the WLAN client)
If required, you can disable the DHCP client on ether1 and then add ether1 to the bridge.
Giving 5 LAN ethernet interfaces.
- A bridged configuration. Your devices behind the hap device are on the same subnet as the devices on the existing wired network.
Configuring this ranges from easy to “It won’t work”.
From a default configuration:
2.1. Common configuration:
2.1.1. Setup so you have somewhat guaranteed access to the device,
(alternatively with winbox you can connect via mac address)
Connect to hap via ether4.
Remove ether5 from the bridge (bridge port)
Add ether5 to the LAN interface list. interface / interface list
Move the ip dhcp server from bridge to ether5
Move the ip address from bridge to ether5
You should now connect to ether5 to manage the hap.
2.1.2. Common configuration continued.
Set the WLAN up to connect to the Access Point, use station mode.
Add an ip dhcp client to the bridge.
Attach the WLAN to the bridge.
You won’t have connectivity via the WLAN at this time.
2.2. Device Specific setups.
2.2.1. Traditional Mikrotik Access Point (easy):
The Access Point you are connecting to is a Mikrotik running the traditional wireless package.
Change the WLAN to station bridge mode.
Check to see the dhcp client on the bridge gets an IP address.
Plug back into any of the WAN ports (likely ether2-ether4)
Should be job done, yay.
2.2.2. Other Access Point (less easy):
2.2.2.1 Station Pseudo Bridge Mode
Change the WLAN to station pseudo bridge mode.
Disable Spanning tree on the bridge (protocol=none)
Check WLAN is connected.
See if the dhcp client on the bridge gets an IP address.
If you plug your computer into ether4, hopefully it will also get an IP address,
and be able to connect to the rest of the network, and internet.
If not work:
Try reboot.
Potentially, turn off spanning tree on the Access Point you are connected too.
If can’t get it to work, you can try Station Pseudo Bridge clone mode.
2.2.2.2 Station Pseudo Bridge Clone Mode
This allows a SINGLE device behind the HAP to connect to the Access Point.
However, the hap itself won’t get an IP address by DHCP.
Though you may be able to connect to it with winbox via mac address, or you can
give the hap a static IP address in the same range provided by the Access Point.
Disable the ip dhcp client on the bridge.
Maybe: give the bridge on the hap a static address (ip address)
(from the Access Point Range)
Change the WLAN mode to station pseudo bridge clone.
Disable Spanning Tree on the bridge (Protocol=none)
Plug your computer into say ether4, and see if it gets an IP address
(In the Access Point Range)
If not work, try reboot.