On Tuesday, 13 March 2018 01:54:13 PDT Nadavd wrote:
Hi Dev
From what i understand the iotivity doesn't support only IPv4 multi-cast?
It does. You may have found a bug.
But that shouldn't be a showstopper because IPv6 should be working.
* About this thanks i see it works on my server client *
Cause my problem is when i am on a local network (Router IPv4 & IPv6), i
am getting a problem that the server sometimes not getting the IPv6 ,
and because of that i am getting an error on the server that
"error:socket IPv6".
This is the reason why i need to use IPv4.
No, that means you need to fix IPv6. What you're asking for is like going to
your mechanic and saying "raise the volume of the horn, because the brakes
don't work". You need to fix your brakes instead.
About fixing the IPv6 it is a problem because it doesn't work on
different Android box devices (not mine from different company) also the
router.
For the question if the packets go out on IPv4, so in the first 5
minutes i can't see them only after.
How did you test this? Was it with tcpdump on the local machine? Was that
machine just recently booted? Had it already acquired an address via DHCP?
I tested it by using a close network with server client and the
simulator, and checked if i receive messages on the server side and on
the network, and didn't got any message.
About the scenario is: after i start the iotivity for the first time on
the client device (the server was already on with resources), then i try
to discover the devices on the network (multicast message) and not
getting any answer after waiting 5 minutes i try again and it works.
So this is why i can't understand the reason why.
Also when i am using IPv6 the multicast message will work straight after
starting the iotivity.
Thanks
Nadav Dawidowicz
Software Engineer
SURE Universal Ltd.
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
