Remote ConsolePI is not recognized with mDNS about consolepi HOT 2 CLOSED

If they are both on the same L2 subnet (sounds like that's the case via the LAN side connection), then yes they should see each other.

Verify with consolepi-status that nothing has happened to the mdns daemons. They should be active/running and double check the status output to ensure there are not exceptions. Same for consolepi-api as it's required to get full details from a discovered remote.

On one of the systems use consolepi-browse which will shut down the consolepi-mdnsbrowse daemon and start the browser script in shell with output. If it discovers a remote it will display if it has an asterisk next to the hostname in the list that means that indicates new or updated data for that remote which results in an update to the local cache (which is cloud.json)

beyond that you can try capturing the logs after restarting the services (restarting the services just so we get any startup logs). Here is a kinda secret convenience command I use for that
consolepi-sync -nopull -reload
Then to tail the logs consolepi-logs -f

The issue may be with the Tagged interface. There is a limit to how much you can put into an mdns payload. If the payload is too big (it's essentially the output of consolepi-details local then it will strip the adapters from the payload, if it's still too big with the adapters removed the only option left is the interfaces so it will actually strip any interfaces with a '.' in them (so it will remove all the tagged interfaces).

I'll re-work it if that ends up being the issue. As long as the receiving side has the IPs to try it can query the full details via the API. So I could just strip the mdns payload down to hostname, cpuserial, and list of IPs. The receiving side would query for full details via the API.

If that's what's causing the issue

from consolepi.

Hi
After a consolepi-sync -nopull -reload the discovery on both ConsolePIs worked well. now i can see all Serial adapters on both ends.
Thank you for the hint with the reload command!

to shorten the mDNS message would be good in any case. I assume a ConsolePI with 12 Serial adapters is too big for a mDNS payload?!
And the strategy to send only the host and IP and cpuserial would be nice, as long you have a API to call!

Thank you very much! We can close the issue now.

from consolepi.