On Thursday 26 February 2015 10:03:21 Dieter, William R wrote: > For example, if IoTivity were integrated into a NAT firewall with one > Ethernet interface going to the outside world and one (or more) interfaces > on the inside network, the firewall would probably only want to find > devices by multicast on the inside network, or at least have a different > level of trust depending on whether a device is inside or outside the > firewall.
What you're saying is true, but the way I see it, it supports my argument: I should be able to select which ones to send on, regardless of the transmission method. You gave the example of a router. On most home routers, there are three or more interfaces available: * a wired one connected to the WAN * a wired one connected to the switch that provides access to the LAN * a wireless one for the WLAN radio (often one for 2.4 GHz and one for 5 GHz) In this case, I want to de-select the first one. A very common scenario for routers is actually that all the LAN interfaces are connected together in a bridge interface. That is neither wireless nor wired -- it's a bridge. That is yet another argument against the distinction between WiFi and Ethernet. But now think of a router for a wireless Internet connection (4G router or WiMax or whatever). Now, instead of having a wired WAN connection, I have a wireless one. So now I want to de-select a wireless interface and keep all wired ones.. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
