Closed CowSmiles closed 2 years ago
Yes, multiple edges are supported. You just should assign its own port such as -p 1234
and its own management port, e.g. -t 6543
.
The message you see is related to a multicast port (1968) which is used to detect local network area edges more easily. It is same for all edges. I have never seen it conflicting when starting several edges but might have escaped my attention. Has anyone else experienced this?
@Logan007 Thank you very much. I have tried the parameter again and with no luck.
Thank you for your feedback, I will check multicast socket again then. What system do you have it running on?
Meanwhile, there are several ways to disable the seemingly issue-triggering multicast detection:
-e auto
or -e <your_local_physical_ip_address>
which should disable multicast peer detection.-DSKIP_MULTICAST_PEERS_DISCOVERY
to completely disable that feature in your build.Thank for you kind help. My system is MacOS Monterey 12.4 x86.
I tried your suggestions. The second one worked. Thank you very much.
./configure CFLAGS="-DSKIP_MULTICAST_PEERS_DISCOVERY"
The parameter in the first one gives the same error message.
When I tried to start two edge instance to connect different supernodes. I got the following error:
does n2n support multiple edges? Or if there are some options to support this?
My environments:
Thanks.