Closed Ataraxiall closed 1 year ago
Comitup, for the most part, ignores the ethernet port. When using the Comitup image, that port is handled by a pair of NetworkManager connections. If you are not using the image, Comitup is uninvolved.
I just tried this on a Pi 4. Nothing bad happened. Comitup didn't log the event at all, and continued working.
What do you mean by "break/stops"? It looks like Avahi stops the registered service on the port, so the host entry on "Avahi Discover" is gone until a restart/reboot (that's inconvenient, but not a significant problem). mdns still works, so "ping comitup-<nnn>.local" gives what you expect.
Good morning,
I have noticed a bug that happens to me after reinstalling and trying different versions. If I have a cable connected to the ethernet port and comitup running, if I remove the ethernet cable, and put it back, comitup breaks/stops. any ideas? I don't know what log they could help you. Thanks!