Yeah, tricky one for a Friday arvo, but now that I have a beer in hand I feel better inclined to think about it :- D The only client isolation sort of behaviouri I can tbink of,, assuming all your bridges are set up ok (and if they weren't you'd likely be seeing more trouble than that ;) is 'default forwarding' behaviour on the wireless interfaces. Forwarding enabled means that a client connected to an ap can pass l2 frames to other clents connected to the same ap - forwarding disabled means tgey can't - eitger way, clients can still reach peers connected to any bridges attached to the ap interface. So pretty much opposite to what you're describing... Could it be the other way around? Cheers! -----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Karl Auer via Public Sent: Friday, 18 October 2024 5:19 PM To: MikroTik Public <public@talk.mikrotik.com.au> Cc: Karl Auer <kauer@nullarbor.com.au> Subject: [MT-AU Public] client separation? We're seeing something that looks a bit like client separation - a PC can't talk to a printer on the same network (both on wifi, both using the same SSID, both on the same VLAN and same IP network, not necessarily both on the same AP though). How can I check for this on 17.15.1? I'm not really convinced it is this, because *sometimes* we can print. But maybe it's because they are on sometimes on different APs? Any other suggestions about how the network could be the problem would be welcome. Thanks, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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. _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au