Hi, I have a RB5009 and a hAPac2. I’ve configured some VLANs and while it works as far as I understand for the wired ports (trunk/access), I have some issues with capsman.
I have provisioned the two radios of the hAPac2 and can configure them in Capsman on the RB5009.
I’ve setup two configurations and two datapaths. The datapaths use mode “use tag” with an appropriate VLAN ID.
I configure the radio master interface with SSID AAA and datapath for VLAN A. Then I configure a slave interface with SSID BBB and datapath for VLAN B.
I see boths WLANs AAA and BBB, and can connect to both. But I only get an IP address on the slave interface from the DHCP in VLAN B. If I change the config to BBB on the master and AAA on the slave, I get an IP in VLAN A but not in B. Whatever WLAN on the master interface, it only connects with a link-local address.
If I put both WLANs on slave interfaces and leave the master interface with an empty configuration I get an IP address on both. (And a WLAN with an empty SSID, which is not what I want)
What am I missing here?
PS: The RB5009 is already on ROS 7.1 while the hAP is still on 6.x - if this might be an issue?!
That's @anav, he gets passionate about things, in both positive and negative way. If he likes something (usually some cloud service), he recommends it everywhere. If he doesn't like something, he discourages everyone from using it. After his last quest against addresses sort of succeeded (don't worry, we're still allowed to use addresses), the new one seems to be quest against CAPsMAN. I'm sure it will pass too.
My point being is I am trying to help you not WASTE your money.
Yes you will have mastered capsman after much head banging, do you want a cookie ??
However the people using your wifi will be pissed at you be it family/friends or customers for the crappy wifi.
SO yes its a great functionality if paired with a decent wifi experience otherwise its a waste of time.
I am practically minded, many others here are IT nerds that do not have to live with the consequences of their advice. ;-PPP
Use the time I am freeing up from Capsman servitude to research an actually useful wifi device for your needs…
No charge advice, you can heed or put it in the circular phone, just sayin…
Caps-man... Absolutely awesome in concept. In form and moving how express and admirable! In action how like an angel, in apprehension how like a god!
Got carried away there.
But ANAV is right about the complaints. Until Mikrotik can get wifi down... An incredibly powerful and elegant control system... Doesn't really matter.
Or as my cohorts say when they watch me grind my teeth over Mikrotik wireless problems on our jobs...
(Looking at caps-man over my shoulder)
"Holy S--t. Can that control a good radio?"
Sadly the wifi wave 2 drivers I used on the Audience that made it work so much better... Are not compatible with this.
"Well what about our other WAPs?"
Nope it's Mikrotik access point control only.
(It wasn't a completely unreasonable question. We do have things that bring together control or configurations of multiple manufactures.)
We moved back to using Ruckus for our wireless exclusively. And the bleeding stopped.
We keep bringing in other manufactures to make sure we are staying on top of things... But I stare over at my stack of cap ACs... It's they have been reduced to "this is why you have to Test devices that only have 2.4 radios in busy environments."
But back to how too.
Put the IPs and DHCP severs on VLANs on the bridge. Use the tag on the SSID.
That's usually all you need to connect those things.
Well using local-forwarding and client to client forwarding.
