public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
* MCD with nncp-caller and nncp-daemon
@ 2021-07-19 15:11 Shawn K. Quinn
2021-07-19 17:00 ` Sergey Matveev
0 siblings, 1 reply; 2+ messages in thread
From: Shawn K. Quinn @ 2021-07-19 15:11 UTC (permalink / raw)
To: nncp-devel
So apparently the use of MCD prohibits the simultaneous use of both
nncp-caller and nncp-daemon. Is this intentional?
skquinn@moonpatrol:~$ nncp-caller -autotoss
main.go:127: Can not run MCD reception: listen udp [address]:5400: bind:
address already in use
--
Shawn K. Quinn <skquinn@rushpost•com>
http://www.rantroulette.com
http://www.skqrecordquest.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MCD with nncp-caller and nncp-daemon
2021-07-19 15:11 MCD with nncp-caller and nncp-daemon Shawn K. Quinn
@ 2021-07-19 17:00 ` Sergey Matveev
0 siblings, 0 replies; 2+ messages in thread
From: Sergey Matveev @ 2021-07-19 17:00 UTC (permalink / raw)
To: nncp-devel
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
Greetings!
*** Shawn K. Quinn [2021-07-19 10:11]:
>So apparently the use of MCD prohibits the simultaneous use of both
>nncp-caller and nncp-daemon. Is this intentional?
Not intentional. SO_REUSEPORT is set only to explicitly multicasted UDP
port, that was not created in MCD transmitting function. Fixed in 7.4.0
release. Thanks for finding that out! I just have not run -caller and
-daemon simultaneously on the same machine.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-07-19 17:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-19 15:11 MCD with nncp-caller and nncp-daemon Shawn K. Quinn
2021-07-19 17:00 ` Sergey Matveev