Hi!
I have not investigated if a similar problem exists with IPv6 addresses.
If you have time, please go ahead and try it!
thanks,
Anders Widell
On 08/05/2016 06:38 AM, A V Mahesh wrote:
> Hi Anders Widell,
>
> Did you verified IP6 or you want me to test ?
>
> -AVM
>
>
> On 8/4/2016 2:22 PM,
Hi Anders Widell,
ACK with assumption, that In Container environments IV6 not being
used/issue doesn't observed.
-AVM
On 8/4/2016 2:22 PM, Anders Widell wrote:
> osaf/services/infrastructure/dtms/dtm/dtm_read_config.c | 36
> +++-
> 1 files changed, 32 insertions(+), 4
Hi Anders Widell,
Did you verified IP6 or you want me to test ?
-AVM
On 8/4/2016 2:22 PM, Anders Widell wrote:
> osaf/services/infrastructure/dtms/dtm/dtm_read_config.c | 36
> +++-
> 1 files changed, 32 insertions(+), 4 deletions(-)
>
>
> The IPv4 broadcast address is
osaf/services/infrastructure/dtms/dtm/dtm_read_config.c | 36 +++-
1 files changed, 32 insertions(+), 4 deletions(-)
The IPv4 broadcast address is sometimes not configured when running in some
container environments (e.g. docker). In these cases, derive the broadcast
address from
