On Dec 5, 2017 4:38 PM, "Thiago Macieira" <[email protected]> wrote:
On Tuesday, 5 December 2017 14:29:43 PST Gregg Reynolds wrote: > Three years ago, this was a design goal. If IoTivity is running on your > router, > > > How would that happen? Some kind of bridge? It could be anything. The router could be connected to some device by other means. > you DO NOT want to accept OCF packets > > > What would be the point of running iotivity if you don't accept OCF > packets? I must be missing something here. You accept packets on the LAN interface. Just not from the Internet. And you don't send queries to the Internet. Don't mean to try your patience, but I still don't follow. It sounds like you're describing an ocf service that just happens to run on a router. In that case there's no question of not accepting ocf local packets nor of talking to the cloud. No? There would only be an issue if the OCF service was indeed a router/bridge which could send and receive stuff on the cloud. Then you might want to white/black list cloud (tcp/http) addresses. But that's not an ocf issue, is it? g
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
