Режимы работы и виды топологий маршрутизатора Cudy C200P со встроенным контроллером

Режим работы 1. Маршрутизатор + Контроллер (режим по умолчанию)

В этом режиме C200P выступает как в роли маршрутизатора, так и в роли контроллера.

В этом режиме рекомендуется подключать не более 10 точек доступа и не более 100 клиентских устройств.

Топология 1: Интернет 🡢 C200P 🡢 Коммутатор 🡢 Точки доступа

  • Сценарий использования: управление множеством точек доступа.
  • Требования
    • Подключите один конец кабеля Ethernet к интернет-розетке или модему, а другой — к порту WAN C200P; подключите один конец кабеля Ethernet к порту LAN C200P, а другой — к коммутатору; затем подключите к коммутатору точки доступа.
    • Убедитесь, что C200P и точки доступа находятся в одной сети VLAN (трафик управления точками доступа не имеет тегов VLAN).
  • Поддержка SSID VLAN
    • При включении функции SSID VLAN клиентский трафик будет тегироваться при передаче от точки доступа.
    • C200P не поддерживает сети и интерфейсы VLAN.
    • Перед включением функции SSID VLAN убедитесь, что коммутатор поддерживает сети и интерфейсы VLAN, а также DHCP-серверы, иначе он не сможет присваивать IP-адреса клиентским устройствам Wi-Fi в сети VLAN.

Топология 2: Интернет 🡢 C200P 🡢 Точки доступа

  • Сценарий использования: управление небольшим количеством точек доступа (не более 4 шт., поскольку у C200P четыре порта LAN).
  • Требования
    • Подключите один конец кабеля Ethernet к интернет-розетке или модему, а другой — к порту WAN C200P; затем подключите точки доступа к портам LAN C200P.
    • C200P, точки доступа и клиенты Wi-Fi должны быть в одной сети.
  • Поддержка SSID VLAN
    • При такой топологии SSID VLAN не поддерживается, поскольку C200P не поддерживает сети и интерфейсы VLAN.

Режим работы 2. Контроллер

В этом режиме C200P выступает исключительно в роли контроллера.

В этом режиме рекомендуется подключать не более 200 точек доступа, максимальное поддерживаемое количество клиентских устройств зависит от возможностей шлюза (коммутатора).

Топология: Интернет 🡢 Маршрутизатор 🡢 Коммутатор 🡢 Точки доступа и C200P

  • Требования
    • Подключите один конец кабеля Ethernet к интернет-розетке или модему, а другой — к маршрутизатору; подключите маршрутизатор к коммутатору; затем подключите к коммутатору C200P и точки доступа.
    • Переведите C200P в режим Контроллер:
      • Выполните вход в веб-интерфейс C200P.
      • Перейдите в раздел Быстрая настройка и выберите режим Контроллер.
    • Убедитесь, что C200P и точки доступа находятся в одной сети VLAN (трафик управления точками доступа не имеет тегов VLAN).
  • Поддержка SSID VLAN
    • Перед включением функции SSID VLAN убедитесь, что шлюз (коммутатор) поддерживает сети и интерфейсы VLAN, а также DHCP-серверы, иначе он не сможет присваивать IP-адреса клиентским устройствам Wi-Fi в сети VLAN.

Если у вас остались вопросы, обратитесь в нашу службу техподдержки по адресу support.ru@cudy.com

Вернуться к блогу

Комментариев: 53

@Dear Kacper Rucinski,
Thank you for your kindly advice! We will provide your feedback to the product department for evaluation.

“Hello,

I just bought C200P today, swayed by its ability to bind clients to individual APs. However, I’m quite disappointed.

1) C200P doesn’t allow managing APs with a wireless backhaul. Do you have any plans to introduce this to the software? Currently, if a cable connection to an AP is interrupted, the AP fails – whereas it should continue working via wireless backhaul.

2) Adopting certain routers in AP mode fails. It fails to adopt the M3000 – factory reset and connected via cable. It similarly fails to adopt WR3000H. Both these devices could easily join mesh if a different device (e.g., AP3000) served as controller. So, while there’s no such mention on its web page, C200P seems to be much more limited with regard to supported access points. Any plans to allow other devices?

3) App management. While web management has its advantages, these days many network admins work on the go. Do you have plans to allow these devices to be managed from an app?

4) Suggestion: ethernet port location. With the exception of rack-mounted devices (which C200P is not), it’s usually more convenient and neat to have ethernet cables connected on the back of a device. For your next product, I suggest to consider placing ethernet ports on the back."

support

Hello,

I just bought C200P today, swayed by its ability to bind clients to individual APs. However, I’m quite disappointed.

1) C200P doesn’t allow managing APs with a wireless backhaul. Do you have any plans to introduce this to the software? Currently, if a cable connection to an AP is interrupted, the AP fails – whereas it should continue working via wireless backhaul.

2) Adopting certain routers in AP mode fails. It fails to adopt the M3000 – factory reset and connected via cable. It similarly fails to adopt WR3000H. Both these devices could easily join mesh if a different device (e.g., AP3000) served as controller. So, while there’s no such mention on its web page, C200P seems to be much more limited with regard to supported access points. Any plans to allow other devices?

3) App management. While web management has its advantages, these days many network admins work on the go. Do you have plans to allow these devices to be managed from an app?

4) Suggestion: ethernet port location. With the exception of rack-mounted devices (which C200P is not), it’s usually more convenient and neat to have ethernet cables connected on the back of a device. For your next product, I suggest to consider placing ethernet ports on the back.

Kacper Rucinski

@Dear Rafal,
No, doesn’t support to use AP3600 with C200P via Wireless. If you want to use the C200P to manange the AP. You must connect them via cable. If you can’t, you have another choice. Do not use the C200P. You can choose one of the AP3600 to be the main mesh AP. And install Mesh system with them.

“Hi Cudy Support,

I’m trying to configure a third Cudy AP3600 without an Ethernet connection and I’m not sure if this is supported.

My setup is:

C200P AP Controller (Firmware: 2.5.15)
3 × AP3600 (Firmware: 2.5.11)
Two AP3600 are connected via Ethernet to the network and have been successfully adopted by the C200P.
The third AP3600 was also connected via Ethernet, upgraded to the latest firmware, adopted by the controller, and configured successfully.

After that I disconnected the Ethernet cable and moved the third AP to its final location, where it has only power (no Ethernet)."

support

Hi Cudy Support,

I’m trying to configure a third Cudy AP3600 without an Ethernet connection and I’m not sure if this is supported.

My setup is:

C200P AP Controller (Firmware: 2.5.15)
3 × AP3600 (Firmware: 2.5.11)
Two AP3600 are connected via Ethernet to the network and have been successfully adopted by the C200P.
The third AP3600 was also connected via Ethernet, upgraded to the latest firmware, adopted by the controller, and configured successfully.

After that I disconnected the Ethernet cable and moved the third AP to its final location, where it has only power (no Ethernet).

The result is:

The AP becomes Offline in the C200P controller.
Its LED continuously cycles between orange → purple → blue.
It never reconnects via Wi-Fi.

According to the AP3600 release notes, firmware 2.5.11 includes features such as:

Wireless Backhaul
Mesh Topology View
Uplink Node Selection

However, I cannot find any settings related to Wireless Backhaul, Mesh, or Uplink Node in the C200P web interface or in Cudy Cloud.

My questions are:

Is it possible to use an AP3600 managed by a C200P as a wireless mesh node (wireless backhaul, no Ethernet)?
If yes, what is the correct configuration procedure?
Is there any additional setting that must be enabled on the controller or on the AP?
Where can I find the Mesh Topology View and Uplink Node Selection mentioned in the firmware release notes?

Thank you!

Rafal

@Dear Sk SINHA,
Our technical support has sent you the solutions via email. Please check.

“Hello Cudy Support,

I am using a Cudy AX1500 router. I am experiencing two problems:

1. The internet speed (Mbps) is lower than expected.
2. The Wi-Fi coverage/range is also quite low.

Could you please tell me why this is happening and what settings I should use to get better speed and wider Wi-Fi coverage?

Please help me troubleshoot this issue.

Thank you."

support

Комментировать