Hi
Is there a way to make static bound of certain client to specific AP by it's mac address under CAPsMAN environment?
I have 3 AP in my home network, and I need some static clients like Apple TV box to connect best AP by signal level, but it doesn't work by default. I think that they connect to the first available AP during CAPsMAN start up, so the access list is not a solution, cause the APs appear in the unpredictable order each time
Re: bound client to specific AP by mac adress by CAPsMAN
No, you can't do that.
What you can do is to nake cAP-specific SSID and then configure those clients to connect to appropriate SSID.
What you can do is to nake cAP-specific SSID and then configure those clients to connect to appropriate SSID.
-
-
gotsprings
Forum Guru
- Posts: 2124
- Joined:
Re: bound client to specific AP by mac adress by CAPsMAN
Couldn't you use the ACL in caps-man and allow it on the cap you wanna allow. Then put a rule right after that to deny it from any interface.No, you can't do that.
What you can do is to nake cAP-specific SSID and then configure those clients to connect to appropriate SSID.
Re: bound client to specific AP by mac adress by CAPsMAN
I can't, as I've told before. There is no way to control an order of CAPs registration by CAPsMAN, so what is cap1 and cap2 next router reboot can became cap3 and cap4, so the access list is unusable this way.Couldn't you use the ACL in caps-man and allow it on the cap you wanna allow. Then put a rule right after that to deny it from any interface.
Re: bound client to specific AP by mac adress by CAPsMAN
I can't figure out how to set the wi-fi channel ((What you can do is to nake cAP-specific SSID and then configure those clients to connect to appropriate SSID.
There is no this option at all. Configuration, security, datapath - all is accessible, but there is no "channel".
Re: bound client to specific AP by mac adress by CAPsMAN
The suggestion, as fas as I understand, is to provision a separate slave configuration with a different SSID to the AP you want to use (e.g., SSID: "wifiForAppleTV" for the AP closest to that device) and then configure your AppleTV to connect to that device.
It is, indeed, what I do in my case: I have a common SSID and then also a specific SSID for each AP. If I want to roam, I configure the common SSID on the device, if I want to stick to a particular AP, I configure the specific SSID on the device.
It is, indeed, what I do in my case: I have a common SSID and then also a specific SSID for each AP. If I want to roam, I configure the common SSID on the device, if I want to stick to a particular AP, I configure the specific SSID on the device.
Re: bound client to specific AP by mac adress by CAPsMAN
Yes, that is exactly what I try to do. Could you please direct me to some sort of guide how to set up these specific SSID for each AP? I've stuck with configuration of thisThe suggestion, as fas as I understand, is to provision a separate slave configuration with a different SSID to the AP you want to use (e.g., SSID: "wifiForAppleTV" for the AP closest to that device) and then configure your AppleTV to connect to that device.
It is, indeed, what I do in my case: I have a common SSID and then also a specific SSID for each AP. If I want to roam, I configure the common SSID on the device, if I want to stick to a particular AP, I configure the specific SSID on the device.
Re: bound client to specific AP by mac adress by CAPsMAN
Details depends on device, version, and generation of wifi interface.
Basically, add a provisioning rule specific for each AP with a configuration specific for each AP and restricting the radio-mac.
See, for example, viewtopic.php?t=193963
Basically, add a provisioning rule specific for each AP with a configuration specific for each AP and restricting the radio-mac.
See, for example, viewtopic.php?t=193963
Re: bound client to specific AP by mac adress by CAPsMAN
Thank you. I've changed the "name format" from "cap" to "identity" in provisioning settings and now I can make the access list much more stable.Details depends on device, version, and generation of wifi interface.
Basically, add a provisioning rule specific for each AP with a configuration specific for each AP and restricting the radio-mac.
See, for example, viewtopic.php?t=193963
I think it's more consistent way to maintain all of this than to have specific configs for specific APs.
Thank's a lot one more time!
-
-
gotsprings
Forum Guru
- Posts: 2124
- Joined:
Re: bound client to specific AP by mac adress by CAPsMAN
Create enableI can't, as I've told before. There is no way to control an order of CAPs registration by CAPsMAN, so what is cap1 and cap2 next router reboot can became cap3 and cap4, so the access list is unusable this way.Couldn't you use the ACL in caps-man and allow it on the cap you wanna allow. Then put a rule right after that to deny it from any interface.
With that setting I could name the CAPs.
That would allow the access list to be setup the way I am thinking.