Skip to main content

in reply to Dan Hon

Just some of the shitty things this could be:

* macOS Ventura, which was recently updated
* the Caldigit TS4 hub, which I also had to mess with because "depending on the order in which I plug things in to the back and front ports, a front port may or may not be a USB 10GBPs port"
* the switch under my table
* one or both of two ethernet cables
* one or both of two MOCA adapters between this and the telco router
* the telco router

#wenevershouldhavetaughtthesandtocount
in reply to Dan Hon

At least we’re not still using token ring.

🤔
in reply to Dan Hon

despite all of my hobbies and most of my interest being #fouragesofsand adjacent … today is a day when I think you’re right #wenevershouldhavetaughtthesandtocount . I wish Douglas Adams were here to offer his wit.
in reply to Dan Hon

if the device is on both WiFi and Ethernet (which after actually the same network) it could be discovering is self, I've had Linux do that with mDNS
in reply to Ben Hardill

@ben yeah, that's probably the answer. It's on Wi-Fi so I can still do eg AirDrop and unlock with my watch :(
in reply to Dan Hon

as pointed out by ben this is probably an mdns multiple network interface on same network fuckup, so it's likely a ventura bug

https://elk.zone/bluetoot.hardill.me.uk/@ben/109785232147325172
in reply to Dan Hon

curious why you’re not entertaining “an intruder is on my network and their device is by chance using the same Bonjour name broadcast” as a possible root cause. Stay vigilant 🙃
in reply to Dan Hon

I had this error a lot when my internet connection was via DSL.
in reply to Dan Hon

you have WiFi and Ethernet connections to the same network and the Bonjour name is conflicting with itself and causing a race condition.