Fixed issue that Cyclone does not receive multicast data on Windows when

the destination cache of the network stack is in a certain state. The issue
is resolved by binding unicast sockets (incoming unicast and all outgoing
traffic) to the address of the interface instead of inaddr_any (0.0.0.0).
Set the new configuration option internal/BindUnicastToInterfaceAddr to
false to get the old behavior.

Co-authored-by: Erik Boasson <eb@ilities.com>

Signed-off-by: Dennis Potman <dennis.potman@adlinktech.com>
This commit is contained in:
Dennis Potman 2020-02-20 14:53:54 +01:00 committed by eboasson
parent af3604dea7
commit 754eb4090e
7 changed files with 54 additions and 19 deletions

View file

@ -491,6 +491,13 @@ day.</p><p>The default value is: &quot;1 s&quot;.</p>""" ] ]
duration_inf
}?
& [ a:documentation [ xml:lang="en" """
<p>Bind unicast sockets to the address of the preferred interface; if
false, bind to 0.0.0.0 (IPv4) or its equivalent</p><p>The default value
is: &quot;true&quot;.</p>""" ] ]
element BindUnicastToInterfaceAddr {
xsd:boolean
}?
& [ a:documentation [ xml:lang="en" """
<p>This element controls which participants will have which built-in
endpoints for the discovery and liveliness protocols. Valid values
are:</p>