On Fri, 2024-10-18 at 17:18 +1100, Karl Auer via Public wrote:
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).
Well, ahem, cough, it was a printer misconfiguration. I dropped a little router with wifi beside the printer, associated the printer and a laptop to it, still couldn't see the printer. Checked the printer IP address to ping it and realised it was not in the network that the router was configured to provide. The printer was configured with a static IP address, one not in any network available in the building. The solution was to let the printer obtain its address via DHCP. I am puzzled as to how it ever worked at all, to be honest, but it demonstrably did work a few times and had in fact been working well for months up until a week or so ago. This is a mystery I don't intend to try to solve, though entertaining theories are welcome. On the up-side I learned heaps about client isolation, default forwarding and so on... Many thanks to all who contributed thoughts. Regards, 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.