In message <[email protected]> Michael Richardson writes: > > >>>>> "Curtis" == Curtis Villamizar <[email protected]> writes: > Curtis> A WiFi AP will not connect to another AP and wireless > Curtis> routers are typically AP by default. So if two wireless > Curtis> routers autoconfig to being AP and using open routing, then > > OUT OF THE BOX: not every device plugged into a home network have > no prior configuration. For instance, someone bringing a newsed > device to grandma's house.
He who configures it needs to fix it. Or press the factory default button (if there is one). The example is two AP. Most AP can be restored to factory default with a button press. Grandma may toss it or call in a geek before figuring out some of the hidden "restore to factory default" procedures like the unmarked "press, hold, and power cylce while holding" trick. This is sort of like the old BIOS that had "secret" ways to get in, different across vendors. They now have a very clear "to enter BIOS do this" to avoid those support calls. > Curtis> there is only a risk if something that is an WiFi client is > Curtis> also a configured to be a router. > > laptop, smartphone, wii, stereo mp3 player, ... I don't have any windows systems or wii on hand (what's the plural of wii, wiii?). And my portable mp3 is (*really old* and only used occasionally on an airplane and ..) USB only. But ... On BSD and I suspect Linux as well, the default for: net.inet.ip.forwarding net.inet6.ip6.forwarding are both zero. A router forwards IP traffic. By default no routing protocols are enabled on a host such as a BSD or Linux system. Even if enabled, a host may run a routing protocol but not forward packets not destined to itself from one interface to another. I would be surprised if any of the devices you have listed above have forwarding enabled by default today, except a smartphone which has been configured to act as a WiFi hub (which itself is not a default). If we define the zeroconf defaults well, then it would be OK if they all forward. As I pointed out in a prior email, the best routing protocol for wired and the best for wireless may not be the same. There will be legacy stuff and we can be compatible with it. We can't work in any arbitrarily misconfigured legacy environment, because you can already make that not work without adding anything. Even with zeroconfig support, we can't work in any arbitrarily misconfigured environment, and maybe the best we can do is provide better hints on what is wrong. [example: a graphical dump of addressing/routing.] Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
