4 ms·
1. It would be the norm with an IPv6 gateway. It's not like it takes anything special to replace NAT with a firewall: allow outbound, allow established/related
by Spivak 8y ago
1. It would be the norm with an IPv6 gateway. It's not like it takes anything special to replace NAT with a firewall: allow outbound, allow established/related inbound, and replace port forwarding in the UX with allow rules for (host, port).
2. No argument, does seem odd that it wouldn't be the app though. Figure a door bell wouldn't be all that intensive.
3. Yeah, recurring revenue is pretty much the gold standard.
A device that stands between your device and the public internet, provides security and access control, and is standards based... so a perimeter firewall? But with an API to allow internal devices to punch their own holes. Ehh don't get me wrong I like the spirit, but that would immediately get used by malware.