![]() ![]() Set supplicant-identity=MikroTikĪdd authentication-types=wpa2-psk eap-methods="" management-protection=\Īllowed mode=dynamic-keys name=profile1 supplicant-identity="" \ Now wired clients can pull DHCP from the ServerAP. ![]() The ClientAPs then run in station bridge to allow them to connect wirelessly and bridge their ether interfaces over. So by breaking the subnet up we can run multiple servers.Įther2 is configured for 192.168.88.19/24 with a DHCP handing out 192.168.88.100-254. ![]() I first thought about bridging Ether2 and WLAN1, but if you do this, you can only run a single DHCP server…which means we can’t set aside a special IP for the server. If you don’t add an interface with an IP, the DHCP won’t enable. I then set Ether2 to IP 192.168.88.1/28 and configured a DHCP server on it to only hand out 192.168.88.10. The ServerAP has proxy-arp enabled for both Ether2 and WLAN1. Oh yeah…and they all have to be in the same “subnet” and accessible to each other. They also want the ClientAP to just bridge everything together so the remote special devices will pull DHCP from the server AP. The routers need to be a generic config so they can use them no matter what MAC address the server has. Off of the ServerAP, Ether 2 must always hand out 192.168.88.10. I had a customer ask for a very odd configuration. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |