)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"9c1481d7f5c27b18805a3dd4f1b6af645f58f1e8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ac53643f_e4b42478","updated":"2025-07-18 19:16:48.000000000","message":"works!\n\nDisabled the \"goto done\" part from the \"same peer-id\" check, and played with the LAN cable :-) - resulting in\n\n```\n2025-07-18 21:14:25 us\u003d793140 cron2-freebsd-tc-amd64/udp6:193.149.48.173:49409 peer-id\u003d0 disallowing peer 0 (cron2-freebsd-tc-amd64) from floating to its own address (udp6:193.149.48.173:49409)\n2025-07-18 21:14:25 us\u003d793175 cron2-freebsd-tc-amd64/udp6:193.149.48.173:49409 peer-id\u003d0 closing instance cron2-freebsd-tc-amd64/udp6:193.149.48.173:49409 peer-id\u003d0 due to float collision with cron2-freebsd-tc-amd64/udp6:193.149.48.173:49409 peer-id\u003d0 using the same certificate\n```\n\n(and then, of course, it SIGSEGVs, but that\u0027s expected - so the extra logging makes this a much clearer picture.  Could not reproduce with two different clients, but I don\u0027t think this will add extra testing coverage)","commit_id":"8fba751bf2de0b696cdc3db902876120700c4fbd"}]}