Creating a network with wireless router and 3 WAPs

[joswittevrongel]

Hi

I have the following configuration:

- RV110W wireless router, central on ground floor, channel 1

- WAP150 (1) wireless access point, one side of ground floor, channel 9

- WAP150 (2) wireless access point, other side of ground floor, channel 12

- WAP150 (3) wireless access point, central on first floor, channel 6

with multiple SSIDs (internal, external, infrastructure).

The WAP150 devices are in a cluster, the router does not have cluster functionality. All are wired and it works fine most of the time.

When I am in the focal point (all 3 same strength) between the router, WAP 1 and WAP 2, I can connect but it keeps switching.

- Is there a way to keep the client connected to one instead of switching? Can one AP hand over the client to another AP?

- I do not like to use WDS but is there similar functionality with all 4 devices using the wired backbone?

Thank you.

Jos

[Sujoy Paria]

Hi,

You may try one thing…

When you are at the focal point of the RV110W router, WAP 1 and WAP 2, that time try the ‘MAC Filtering’ option available under the Wireless menu in WAP150 device to block the Wireless LAN card MAC of the system connecting to those devices. In that case you need to select the check box ‘Block all stations in list’.

As per the admin guide of the WAP150 device, Client Filter configuration parameter supposed to propagate among all the clustered WAP devices. So, in your case at that point your system is supposed to connect with only RV110W Router.

As of now there is no automated mechanism implemented in WAP150 device to hand over the wireless client to another AP. So, we need to check for the manual configuration options available.

Also, ‘Wireless MAC Filter’ option is available in RV110W to prevent the systems from accessing the Wireless Network. If you try that then your system supposed to be associated with the WAP150 APs when you are at the mentioned focal point between those devices. Only difference will be, now your system may get associated with both the available WAP150s (one at a time) in case client filter is not configured in WAP150.

[joswittevrongel]

Thank you for the hint. I saw another problem in that they connect to the RV110W on VLAN3 whereas they connect to the WAP150s on VLAN1 (even though the WAP150 is configured to connect them on VLAN3). Possibly this is why the switch takes so long, as the DHCP IP address received is in a different range. I'm a bit in a muddle with the VLAN tagging/untagged/excluded. Is there a clear explanation somewhere?