-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gurkan,
On Thursday, May 30th, 2019, Gurkan Erdogdu
wrote:
>
> In macOS test server, when configuring the mcastBindAddress as
> 192.168.1.139 and address as 228.0.0.4 , the code does not use
> mcastBindAddress , instead it uses multicast
Hi ChrisIn macOS test server, when configuring the mcastBindAddress as
192.168.1.139 and address as 228.0.0.4 , the code does not use mcastBindAddress
, instead it uses multicast address for socket binding and throws exception
when sending the datagram packet. Here is the exception:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gurkan,
On 5/29/19 02:28, Gurkan Erdogdu wrote:
> Hi In an McastServiceImpl#setupSocket method, if the user
> configures the mcastBindAddress, it will use the socket to bind to
> this address. But, in the code below, it uses the "address" field
>
HiIn an McastServiceImpl#setupSocket method, if the user configures the
mcastBindAddress, it will use the socket to bind to this address. But, in the
code below, it uses the "address" field while creating the socket. Is this
correct ?
if (mcastBindAddress != null) {
try {