DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
Mesh with VigorAP bundle (1 x 903 + 3 x 802) issues
- bennyhest
- Topic Author
- Offline
- New Member
-
- hornbyp
- Offline
- Big Contributor
-
- bennyhest
- Topic Author
- Offline
- New Member
-
- hornbyp
- Offline
- Big Contributor
-
23 Aug 2020 01:44 #96912
by hornbyp
Yes - in a nutshell, when a client reaches the signal strength limits, the AP's start asking around to see if another node would manage something better. If the answer is "yes", the client is booted off and added to a block list for "a while", to stop them just reconnecting.
See that other thread I linked to, for the settings I ended up with. Also, details of Android Developer option for checking from the client end, that it's working.
In that case, remove them from the Mesh, RESET them, then re-add them. When they sync, logon to the GUI and change the password to something you can remember:wink:
(While you're logged on, double-check that all the settings from the 903 that you expect to have propogated, have
If you make any subsequent changes to the Mesh Root, I'm pretty certain you have to manually push them to the Mesh nodes (using "Mesh >> Basic Configuration Sync" and/or "Mesh >> Advanced Configuration Sync")
AFAIK, there's no detailed view of the clients on the Mesh nodes.(I just logged onto mine to double-check and found out that the 2.4GHz band had disabled itself
You know the saying about "taking a horse to water, but not being able to force it to drink"? ... I think it applies to Wifi clients as well
Replied by hornbyp on topic Re: Mesh with VigorAP bundle (1 x 903 + 3 x 802) issues
BennyHest wrote:
Ok, so clients are sticky in regards to mesh node roaming, but this can also be controlled by the mesh nodes with AP-assisted client roaming.
Yes - in a nutshell, when a client reaches the signal strength limits, the AP's start asking around to see if another node would manage something better. If the answer is "yes", the client is booted off and added to a block list for "a while", to stop them just reconnecting.
What are the recommended settings under Wifi roaming section of the main root mesh? This was default turned off.
See that other thread I linked to, for the settings I ended up with. Also, details of Android Developer option for checking from the client end, that it's working.
I have tried the default user/pwd on my VigorAP 802, and the new credentials for my main VigorAP 903, but neither works. Any ideas?
In that case, remove them from the Mesh, RESET them, then re-add them. When they sync, logon to the GUI and change the password to something you can remember
(While you're logged on, double-check that all the settings from the 903 that you expect to have propogated, have
If you make any subsequent changes to the Mesh Root, I'm pretty certain you have to manually push them to the Mesh nodes (using "Mesh >> Basic Configuration Sync" and/or "Mesh >> Advanced Configuration Sync")
Will I be able to see all wireless stations from my central 903 mesh root?
AFAIK, there's no detailed view of the clients on the Mesh nodes.(I just logged onto mine to double-check and found out that the 2.4GHz band had disabled itself
I really hope for at smooth and out-of-the-box easy setup of my fairly simple demands - to have my house covered with no blind wifi spots, without having to tweak all sorts of stuff to accomplish this?
You know the saying about "taking a horse to water, but not being able to force it to drink"? ... I think it applies to Wifi clients as well
Please Log in or Create an account to join the conversation.
- piste basher
- Offline
- Big Contributor
-
- hornbyp
- Offline
- Big Contributor
-
28 Aug 2020 02:17 #96969
by hornbyp
I hadn't noticed that. It is all very peculiar!
As I noted in't other
thread
, it doesn't appear to work unless the AP's are in Mesh-mode
:?:
To confuse further, I was messing with my 2860n's Wifi (which doesn't support any form of Meshing). It does
But despite commonality of SSID/VLAN & subnet, I could not make it inter-operate with my AP903/AP802 combo. (It hung on way past my selected RSSI parameter and did not disconnect the client - which finally gave up itself). From Syslog, I could see the 2860n was getting concerned at the low signal, but it received no offers from either AP903 or AP802. Their Syslogs contained nothing pertaining to this event at all.
I wonder how "Dog's Dinner" translates in Mandarin?
Replied by hornbyp on topic Re: Mesh with VigorAP bundle (1 x 903 + 3 x 802) issues
Piste Basher wrote:
Bear in mind that, according to Draytek,https://www.draytek.co.uk/support/guides/kb-ap-mobility , AP assisted roaming only works if the APs are connected to the wirednetwork.
I hadn't noticed that. It is all very peculiar!
As I noted in't other
To confuse further, I was messing with my 2860n's Wifi (which doesn't support any form of Meshing). It does
Code:
Minimum RSSI with Adjacent AP RSSI over X
* Disconnect clients with bad signal to encourage roaming only when they can have better signal through another DrayTek AP.
* All APs must be DrayTek APs which support this feature. The LANs assigned by the SSID of all APs must be connected by Ethernet
and under the same subnet.
But despite commonality of SSID/VLAN & subnet, I could not make it inter-operate with my AP903/AP802 combo. (It hung on way past my selected RSSI parameter and did not disconnect the client - which finally gave up itself). From Syslog, I could see the 2860n was getting concerned at the low signal, but it received no offers from either AP903 or AP802. Their Syslogs contained nothing pertaining to this event at all.
I wonder how "Dog's Dinner" translates in Mandarin?
Please Log in or Create an account to join the conversation.
Moderators: Chris, Sami