CAPsMan commutation problem

No man, if you set “create dynamic enable” in your provisioning you don’t have to click anywhere.

I had discussion with Uldis from Mikrotik support, he said that it is not recommended to use CAP from the same machine where’s capsman working, cause you can’t properly use MAC connection there, and IP connection is corrupted with the firewall, either you use your local ip like my 192.168.5.1/24 or you simply use 127.0.0.1 My “local” caps connection, both networks are working, but clients that connecting without hotspot directly to my bridge can’t interact with wired clients while on “local cap”. If I move to another side of apartment. client changes CAP and then its all ok, he’s totaly visible and available. It’s the capsman problem, when his local CAP connected to it from it’s own bridge through MAC or IP, nevermind, and even if you disable the last drop rule in your firewall, wireless client on this “local cap” cant reach wired clients, and vise versa. I presume this is some kind of bug and you should not use local wlan interface on the machine where’s capsman running. I have 750UP as capsman in my ffice and four 951-s running as CAPs and this scheme works perfectly. I hope mikrotik will improve capsman functionality. Also I hope they will introduce a new home router with PPC processor and 10+ gigabit ethernet ports, cause 2011 is good, but nowadays you need gigabit everywhere and you need much more poerful processor than MIPSBE for encrypted vpn and torrent in the same time. And also you need 5 GHz at home already, I hope someone in mikrotik reading this posts from time to time :slight_smile: