3 ms·
There is nothing special here about LAN IPs. This same problem impacts anything that sits behind a firewall that the browser might have access to. A browser ha
by kortilla 6y ago
There is nothing special here about LAN IPs. This same problem impacts anything that sits behind a firewall that the browser might have access to.
A browser has no way to know that a particular IP address is supposed to be sacred and unreachable by other websites. I’ve seen several dashboards hosted externally that load things from internal IP addresses and that design is MEH but it works.
- jeremyjh 6y agoThere absolutely is something special about most of these IPs. There are blocks that are reserved only for use in private networks. IETF standards for IPv4 on this topic have been in place for decades: https://en.wikipedia.org/wiki/Reserved_IP_addresses https://en.wikipedia.org/wiki/Reserved_IP_addresses https://tools.ietf.org/html/rfc1918 https://tools.ietf.org/html/rfc1918
- kortilla 6y agoNo, there isn’t anything special about them from a browser’s perspective. They have been reserved so they can be re-used across private networks without conflicting with routes on the Internet. An address in the rfc1918 space isn’t magic and a shitload of corporate/campus/etc networks depend on treating them just like any other IP address when you load stuff up in a browser. If a page loads a resource from a private address, it can easily be a local cache on the network. It can also be a dashboard like the example I gave you. Example: local.dashboard.example.org resolves to 192.168.255.244 dashboard.example.org resolves to some public address and web server that hosts a page that loads resources from local.dashboard.example.org