Hey guys and gals

I wasn't sure how to word the title for this question. Essentially what I want to do is plug an mAP lite into a network and receive dhcp from the main network, not the mAP.

I was about to type out some initial thoughts on how to do it but my mind was just coming up with potential problems one after the other at gigabit speed (need to upgrade my mind to SFP+ soon).

How would you guys go about it?

For anyone that's​ interested I'd use this in server rooms without WiFi (which plenty of my clients have) to give my phone VoIP capability and to connect my yoga S1 if I leave my USB Ethernet connector somewhere, which happens often.

Thanks in advance Mtikkers.

Sent from my SM-G920F using Tapatalk

The quick way would be to disable the DHCP service on the Mikrotik and plug the lan into ether2, not ether1. That would be enough to do what you want.

Or you can go the extra mile and turn the Mikrotik into a switch with an IP.
IP > Interface, go through ether2 - ether5, set master port to ether1.
IP > Bridge > Ports. Remove ether2 and add ether1 to bridge-local
IP > DHCP Server, delete the entry
IP > Address, delete the default 192.168.88.0 entry
IP > DHCP Client, edit entry. Set interface to bridge-local

Now you can use any ether port to connect to Lan, and the remaining ports can be for users who wish to use a wired connection in the boardroom.

Good direction, but you might have too many ethernets there for mAP lite.

Just start from blank config, set up wireless interface how you want it, bridge it together with ethernet and that's it, everything else (including IP address on mAP lite) is optional.

Thanks guys.

You were right. I just removed all dhcp servers and addresses, bridged the two interfaces and reassigned the client to the bridge. Problem solved

I guess this will work if I set the wifi to connect to another ssid then feed ethernet to my laptop? (like if i set the mAP up miles away to get a signal and ran a long cable to wherever i was?)

Miles long ethernet cable won't work, but if you keep it shorter, then yes. You'll also want to read about wireless station modes, as there are some limitations.

We do this using two different Vlans. one for management, one for the bridged AP data vlan.

A. Logged into it wireless the first time.
B. Deleted the DHCP client on the ethernet
C. Created two Vlans on the ethernet ( 20, and 222 for our needs)
D. Created IP address on Vlan 20 (for management)
E. Set the Default route to match Vlan 20 needs
F. Connected the mAp to a swicth port with both 20 & 222 on it , tagged
G. Connected to the mAp via the ethernet. (using the new IP address, on Vlan 20)
H. Deleted all other configs in the mAp. DHCP server, firewall settings, etc.
I. Created bridge between Vlan 222 and the Wlan
J. Configured Wlan for our needs
K. Set up the security, passwords, IP services, etc.

It manages on Vlan 20, and the AP bridges on Vlan 222 and gets DHCP from Vlan 222, Works great.

Dean