On Fri, 2024-10-18 at 19:45 +1100, Patrick Sayer via Public wrote:
If you are using CAPsMAN tunnels and have configured your Bridge Horizon to be identical on them all (ie some value set) then it will cause the opposite effect to Client Isolation on the AP in that it will block communication between devices on different APs.
It is identical on all of them, but only in that none of them have a BridgeHorizon value set. In winbox: WiFi -> Datapath -> (select datapath) -> Bridge Horizon field is blank, with a down-arrow beside it. If, for example, the printer or the laptop were changing from AP to AP, and comms between clients on different APs were blocked, that would explain why it sometimes works. Not why the devices would waft from one AP to another, but still, plausible. I'm not sure if I am using CAPSMAN tunnels. I did find the "Client Isolation" checkbox though. It is set on one network, our guest wifi network, but not on any of the others, and not on the network with the printer and laptop in it. Regards, K. PS: This is not urgent. Sorry I didn't make that clear. Also, I will see what happens if I connect to the printer on an independent different router using actual wires. Just to make sure this is not, you know (waves hands) printer things. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@nullarbor.com.au, he/him) work +61 2 64957435 http://www.nullarbor.com.au mobile +61 428 957160 Please feel free to deal with this email during your own working hours.