Eap225v3 OC200 mesh with wired backhaul

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Eap225v3 OC200 mesh with wired backhaul

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Eap225v3 OC200 mesh with wired backhaul
Eap225v3 OC200 mesh with wired backhaul
2020-03-07 22:20:47 - last edited 2020-03-09 02:26:39
Model: EAP225  
Hardware Version: V3
Firmware Version: 2.6.1

I have 3x EAP225 v3 with multiple SSIDs on 2 different VLANs, thinking about adding an OC200 to support mesh (objective: fast roaming and band steering) All EAPs are connected to a POE smart switch - which is connected to a VLAN-capable router. 

 

The OC200 manual assumes the EAPs are connected with one "Root" EAP wired, and the others "Meshed" using wireless backhaul. 

 

What is the proper way to set this up with all the EAPs wired? With other hardware I am aware of, the mesh APs would need to be "downstream" of the device running as controller, with spanning tree protocol turned off on that portion of the network, for example.

 

Step-by-step instrunctions -- added to the OC200 manual -- would be real handy.

 

Thanks for your help.

  0      
  0      
#1
Options
1 Accepted Solution
Re:Eap225v3 OC200 mesh with wired backhaul-Solution
2020-03-08 20:14:43 - last edited 2020-03-09 02:26:39

@SpeedyMe, a mesh can have any number of root nodes, but I wonder why you would want to use a mesh nework anyway?

 

Basic roaming, seamless roaming and band steering do not depend on setting up a mesh network.

You can use the former features with any network topology, even with wired-only EAPs.

 

For basic roaming you just need to use the same ESSID and wireless settings (mode, encryption etc.). In addition, for seamless roaming you need a controller.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
Recommended Solution
  1  
  1  
#2
Options
5 Reply
Re:Eap225v3 OC200 mesh with wired backhaul-Solution
2020-03-08 20:14:43 - last edited 2020-03-09 02:26:39

@SpeedyMe, a mesh can have any number of root nodes, but I wonder why you would want to use a mesh nework anyway?

 

Basic roaming, seamless roaming and band steering do not depend on setting up a mesh network.

You can use the former features with any network topology, even with wired-only EAPs.

 

For basic roaming you just need to use the same ESSID and wireless settings (mode, encryption etc.). In addition, for seamless roaming you need a controller.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
Recommended Solution
  1  
  1  
#2
Options
Re:Eap225v3 OC200 mesh with wired backhaul
2020-03-09 02:25:47

@R1D2   Thank you. Sounds like I do not need a mesh for my wired APs. The objective was just to enhance roaming between my APs (not that I have a problem, just a retired guy tinkering at home). 

  0  
  0  
#3
Options
Re:Eap225v3 OC200 mesh with wired backhaul
2020-03-09 13:22:53 - last edited 2020-03-09 13:30:10

Hi SpeedyMe, you're welcome anytime.

 

A mesh network is useful if a cable connection to the EAP isn't possible. The advantage of meshing is to save a cable for easy deployment of an EAP, but the dis-advantage is that a mesh network will be able to serve only the same number of client devices a single EAP of this mesh does. If you ask me, cabling is the preferred method to connect EAPs to an existing network.

 

You even don't need a controller for basic roaming: just set all three EAPs to the same SSID, same WiFi security, same WiFi modes. Only »seamless« (fast) roaming needs a controller. Seamless roaming avoids the scanning for nearby SSIDs on a client when roaming. In seamless roaming mode, the controller will send a list of suitable nearby EAPs to the client which than can connect faster. Note that this particular mode (802.11k/v) for seamless roaming requires the client to support this mode, too.

 

But an OC200 controller can be useful anyway: you define all settings only once and they get applied to all your three EAPs automatically.
The controller offers more functions compared to an EAP in stand-alone mode. You could also install the software controller version on your PC to test it before considering to buy an OC200 or as a permanent replacement for an OC200.

 

Happy tinkering at home! ;-)

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re:Eap225v3 OC200 mesh with wired backhaul
2020-03-22 16:13:04

The OC200 is really nice for management and works well with the Omada Cloud and Omada App (I use iOS) functionality.  I've had TP-LINK EAP's for my home for several years now (before the OC200).

 

Honestly, my experience is that roaming works really well on these AP's (even without the controller) when they are configured using the same SSID and encryption/security/password info (as others have said). 

 

Since acquiring the OC200 about a year ago, I've enable "FAST ROAMING" using the controller but honestlyI don't really notice much (if any) difference.

 

-Jonathan

  0  
  0  
#5
Options
Re:Eap225v3 OC200 mesh with wired backhaul
2020-03-22 16:18:43
I should have added, that I also have MESH enabled. But as others have said this is separate and unrelated to roaming. I have two EAP225 V3's currently in my smaller home. Ideally I would get one more, but I don't have enough free channels due to neighbors, etc. Anyway, my downstairs EAP is hardwired to my FIOS routers. But my upstairs EAP is connected using a MOCA 2.0 Bonded Coax Bridge. A couple times a year when my router reboots, etc. the MOCA will flake out and the upstairs EAP gets disconnected from the internet. This used to be an issue b/c I have like 40 Wifi clients in my house some would stay associated with the upstairs EAP but they would lose internet connectivity. Now with MESH, when the MOCA/Ethernet flakes out, the EAP falls back to wireless MESH and my clients stay connected. Yea! Jonathan
  0  
  0  
#6
Options