Omada EAP650 Trunk Not Working with Mikrotik Router
Hello, I have a TP-Link EAP650 access point that I would like to connect to my MikroTik router (RB5009UPr+S+IN) on port ether2. I bought the access point knowing that I can set up VLAN's on it and set up network segmentation trunked from the router to multiple WLAN's on the AP. This is my setup:
- On my router, ether1 is a WAN port. A bridge network exists (192.168.1.0/24).
- ether2 is connected to the EAP650.
- Three VLAN's have been created on the router, vlan-id 10, 15, 20. Subsequently, IP address networks created for each:
- Gateways 10.1, 15.1, 20.1.
- DNS server 1.1 (matching the bridge network).
- Each VLAN (10, 15, 20) acts as an interface, and is tagged to bridge and ether2. Ether2 acts as a trunk port.
I have set up other ports (access not trunk) on the router that are on VLAN30, and VLAN30 is only tagged to the bridge with these ports untagged (for instance, ether3).
Whenever I connect the access point to ether3, the AP gets an IP address. But on ether2, it disconnects.
Anyone who may help to fix the trunking issue? Much appreciated.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @memekritis
Thanks for posting here.
Did you configure the management VLAN on the Mikrotik Router? What's the default LAN of the Mikrotik Router?
Please also add that VLAN to the ETH2 port.
In addition, you need to create the corresponding VLANs on the EAP as well.
If the situation is still the same, you may contact the support team, and provide screenshots of the VLAN configuration page on the Mikrotik Router and the EAP. They will help you to check the config.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@lukepo Thanks for your response. I do not have an Omada switch. My AP is connected directly to the Mikrotik. My assumption is that the router can perform some switching via the bridge (layer 2 connectivity). In your opinion, will such a connection work? (Mikrotik <> EAP650)
- Copy Link
- Report Inappropriate Content
I had eap connected to rb5009 directly before so yes it should work. I had no issue using it in trunk or access port. Also with eap in standalone mode and now with controller
- Copy Link
- Report Inappropriate Content
Hi @memekritis
Thanks for posting here.
Did you configure the management VLAN on the Mikrotik Router? What's the default LAN of the Mikrotik Router?
Please also add that VLAN to the ETH2 port.
In addition, you need to create the corresponding VLANs on the EAP as well.
If the situation is still the same, you may contact the support team, and provide screenshots of the VLAN configuration page on the Mikrotik Router and the EAP. They will help you to check the config.
- Copy Link
- Report Inappropriate Content
@Vincent-TP Thanks, I was able to fix the issue.
- Copy Link
- Report Inappropriate Content
Hi @memekritis
Glad to hear that.
May I ask how you fix it? This might help other users who are facing similar issues.
memekritis wrote
@Vincent-TP Thanks, I was able to fix the issue.
- Copy Link
- Report Inappropriate Content
@Vincent-TP Indeed. The issue is that the AP itself was not getting an IP address. I changed my eth2 configuration to admit all frame types (untagged for the sake of the AP getting its own IP address, and tagged for VLAN trunking). I also set the PVID value for eth2 to the management VLAN value. On the management VLAN interface, eth2 was untagged. On the VLAN interfaces corresponding to the WLANs set up on Omada AP for segmentation, eth2 was tagged.
* For context, eth2 (on the MikroTik device) is connected physically to the Omada AP.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 409
Replies: 8
Voters 0
No one has voted for it yet.
