4 ms·
> That would be ideal. But you could also have a GUI program that manages mapping tunnels to ports for apps that don't have built-in support. Right, this sound
by stavros 5y ago
> That would be ideal. But you could also have a GUI program that manages mapping tunnels to ports for apps that don't have built-in support.
Right, this sounds basically like what the firewall does in the p2p case.
> which is much easier than buying a new router, switching to an ISP that supports IPv6, etc.
Yes, if you can't just open a port, a tunnel is easier, true.
> If you're routing through a 3rd-party anyway, why not tunnel and gain all the additional benefits?
Well, you wouldn't be routing through a third party. DDoSes are costly and you usually don't need to protect against them if you're a home user.
> I do wish DNS had a way to specify ports in records.
That's what SRV records are for, no?
> but I don't see it happening for many years to come
Hmm, I don't think we need it everywhere, just where people care to use it, but maybe. I'm not as pessimistic, as my home ISP gives me a (fairly static? I've never actually checked) IPv4 where I opened a bunch of ports, but it would certainly be better if each of my home devices could be addressable from the internet.
TakingNames is an interesting idea, though I'd have to think a bit more about it to tell if I'd find it useful :P The current method of just opening a port on my router has worked extremely well for me so far!