Given the mention of IoT, I imagine the idea is targeted at home users who aren't IT professionals, and the aim would then be to provide "IT infrastructure in a box" for the home user who doesn't want to run separate servers for their IoT devices; for these people, it's probably conceptually easier just to load everything into the one wireless access point they're already used to.
On Sun, Feb 2, 2014 at 5:48 PM, Edward Ned Harvey (blu) <[email protected]>wrote: > > From: [email protected] [mailto:discuss- > > [email protected]] On Behalf Of Tom Metro > > > > Is running applications on your router really such a good idea? > > Define "router," and define what distinguishes it from "firewall." > Define "applications." > > It has been long standing, common practice, by necessity, that the > firewall is the VPN server. Also by necessity, the VPN is provided over > https. And the VPN installer is downloaded by browsing to > https://therouter ... In many ways, this fits the defintion, the > router is in fact serving an application, and rightly so. > > Likewise, the firewall is often the provider of DNS cache, and DHCP > services. I usually prefer to migrate these services elsewhere within the > LAN, but in many situations, it is rightly put on the firewall. > > So in the above https situation ... It's just providing a convenient > mechanism to download vpn client, and relay traffic... But depending on > the model of firewall, often the administration interface is served up via > https as well. > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau / Executive Director, Boston Linux & Unix Email: [email protected] / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
