Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

When exposing services to the internet it's even more PITA since each device needs a DynDNS client configured, whereas with IPv4 just the router needs one for my single public IP.

Presumably because you configured the forwarding on the router? I mean, that should still be possible, right? Set up a name for the routers IP, and have it forward the connections statically.

IPv6 on the LAN is quite a pita due to the massive "random" prefix, gone are the days of easy addresses like 10.0.0.12.

Or just use the hostname? Sometime a couple of years ago, local names just started working, sort of on their own. My Synology is nas.local, Linux boxes are reachable using their configured hostname, even my elderly printer shows up as vigor2.local.



> Set up a name for the routers IP, and have it forward the connections statically.

If you mean NAT, then what does that buy me over what I got? If you don't mean NAT then how would that work?

> Or just use the hostname?

Right, but that requires the DNS to register the host names, and for it to respond. Or since you mention .local I guess you mean mDNS, which requires a service to run on each device and seems to be hit and miss at least for me (I just tried, several of my devices do not respond).


If you mean NAT, then what does that buy me over what I got? If you don't mean NAT then how would that work?

Nothing. But you can just keep doing what you are doing now, even with IPv6. That's what I meant.

I just tried, several of my devices do not respond

Ok. Like I said, it Just Works for me.


> But you can just keep doing what you are doing now, even with IPv6.

Do you mean keep using IPv4 or use NAT with IPv6? If the former then well, so much for that IPv6 future. If you mean the latter, the whole point of IPv6 was death to NAT no?


The whole point of IPv6 was we ran out of IPv4. NAT was a kludge necessary because "we" didn't act fast enough on that fact.


> Or just use the hostname? Sometime a couple of years ago, local names just started working, sort of on their own.

That highly depends on what router you have. For mine, the actual suffix is Speedport_W_123V_2_34_000, which is complex and/or invalid enough that a lot of software refuses to resolve it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: