3 ms·
Even with normal NAT, you have to set up the port-forwarding, and you have to know how to do that. Also, some routers have a bug¹ whereby even a properly port-
by deathanatos 5y ago
Even with normal NAT, you have to set up the port-forwarding, and you have to know how to do that.
Also, some routers have a bug¹ whereby even a properly port-forwarded service won't be accessible from within the network. E.g., the port-forwarded service "works", except for you, on your own network. Really frustrating since it means how you connect depends on where you are, and it's a lot of special crap needed to determine "oh, okay, I'm on the home network so use the internal IP"; almost ended up setting up a split-horizon DNS to deal with it².
¹ISPs will tell you that they "lack a feature". Yeah, okay.
²but then we moved and now we have a different monopoly for an ISP.
- AdamJacobMuller 5y ago1) isn't a bug, it is a lack of a feature. In order to accomplish that you need to double-NAT things because otherwise the internal service will send the reply directly to your computer instead of sending it back to the NAT gateway to reverse the NAT. The router needs to NAT the destination IP for the client and NAT the source IP for the server. The thing is, 99.9999% of these devices never even have the port forwarding feature touched and an even smaller % of the devices where people enable port forwarding care about this.
- mercora 5y ago> Also, some routers have a bug¹ whereby even a properly port-forwarded service won't be accessible from within the network. i think the missing feature is called hairpinning[0] [0] https://en.wikipedia.org/wiki/Hairpinning https://en.wikipedia.org/wiki/Hairpinning