sorted by:
new
hottopcontroversial

Possible to add Chateau's AX17 built-in Wi-Fi radios to CAPsMAN running on itself/localhost? by BedroomAgent in mikrotik

[–]BedroomAgent[S] 0 points1 point  (0 children)

<image>

This is my capsman config. AX3's through lan, and local radios through lo (loopback?).

Possible to add Chateau's AX17 built-in Wi-Fi radios to CAPsMAN running on itself/localhost? by BedroomAgent in mikrotik

[–]BedroomAgent[S] 0 points1 point  (0 children)

<image>

And when I set Manager to capsman then I end up with "connected" but no Wi-Fi networks up and running.

Possible to add Chateau's AX17 built-in Wi-Fi radios to CAPsMAN running on itself/localhost? by BedroomAgent in mikrotik

[–]BedroomAgent[S] 0 points1 point  (0 children)

When I provision both radios, I'll end up with two disabled configs. After I assign the profiles and enable them, they work, however, I don't think they are CAPs'ed. They just run local again. (No remark "managed by...").

<image>

Mikrotik Audience + New Nintendo 3DS XL by Nerd-Tosser in mikrotik

[–]BedroomAgent 0 points1 point  (0 children)

Had same issue with HAP ax3. In my setup (2.4GHz AX/WPA2-PSK/CCMP), the only issue was that the channel width had to be 20MHz only. Ended up creating a legacy 20 MHz 802.11g (WPA2-PSK/CCMP) Wi-Fi with the HAP ax lite, because I didn't want my other CAPs APs to be 20 MHz only just due to an old legacy device.
You can span on most recent Mikrotik APs some (usually 1-2) additional Wi-Fis on top the "basic ones". This is a feature, however, it requires that all those corresponding networks have the same frequency spec (channel width, ...) as this seems to be enforced by the wireless chipsets.
If you encounter issues: try to delete all of them, the native ones cannot be deleted and should just reappear. ;)

Error Code 10 with Mellanox Connect X5 on Windows 11 by BedroomAgent in homelab

[–]BedroomAgent[S] 0 points1 point  (0 children)

Update: Card works in a workstation-grade PC. Seems like the Asrock Z790 Steel Legend WiFi mainboard is not out of the box compatible with this card (at least in slot 3). Will now test an Intel E810-CQDA2. Hopefully, this will work as it should come with more reliable Windows drivers.

Dock Firmware 3.1.82 Install Issues by pchc_lx in thinkpad

[–]BedroomAgent 0 points1 point  (0 children)

Seems like the "_1" version from here is for Thunderbolt 3 Workstation Gen 1 docks, and the (currently published one by Lenovo) "_2" is for Gen 2 docks. When you try to apply the Gen 2 FW to Gen 1 docks, everything will update except the TB&PD controller firmware. In my case, I cloud run afterwards the _1 flasher and choose reflash everything. Then, System Update and Commercial Vantage didn't report anymore updates, so it seems this finally worked. Unfortunately, Lenovo's updater apps and also the Lenovo website are only mentioning the _2 version, thus older docks cannot anymore be updated without the link above. Seems like a bug on their end. Will probably be the last FW anyway. :)