News for hackers. Stuff that matters.
Re:The world in which IPv6 was a good design (2017) by stingraycharles on Thursday June 13, 2019 @03:24AM (#20172502)
Ok so here's a question for the HN community: I have IPv6 from my ISP, and as an experiment, I want to primarily use IPv6 to connect to my different home servers.

I use automatic address selection, so no DHCP. So this means that when a server reboots, chances are their address changes.

Other than setting up a custom DNS server and $somehow ensuring that each server registers itself at this DNS server at boot, are there any elegant solutions to this?

Re:The world in which IPv6 was a good design (2017) by cesarb on Thursday June 13, 2019 @06:39AM (#20173422)
> I use automatic address selection, so no DHCP.

This means you're using SLAAC instead of DHCPv6, right? In that case, your servers should have a fixed IPv6 address derived from their MAC address. Even if they also have privacy addresses (and prefer to use them for outbound connections), they should still have the non-privacy address which you could use for inbound connections.

Or is it the problem that, when your router reboots, the IPv6 prefix changes? That is a harder problem (and would be the same in IPv4).

Re:The world in which IPv6 was a good design (2017) by starfox64_ on Thursday June 13, 2019 @03:44AM (#20172579)
Is there anything preventing you from assigning static IPv6 addresses on your machines?
Re:The world in which IPv6 was a good design (2017) by magicalhippo on Thursday June 13, 2019 @09:11AM (#20174454)
In my case, I get a new prefix every time my router reboots or otherwise loses connection.

Then there's the case of firewall rules. My router gets a new prefix which causes my server to get a new IP, how do I get my firewall (pfSense) to update my firewall pass rules to point to the new IP?

I must admit I haven't tried really hard, so there might be some obvious ways I'm missing.

Re:The world in which IPv6 was a good design (2017) by fulafel on Friday June 14, 2019 @03:11AM (#20181067)
If your prefix is always skipping, you have to complain to your ISP and meanwhile automate your network renumbering. Is there a reason you are not using the pfsense device to do routing and (put the cpe device to bridge mode)? Then you don't need to worry about your firewall not knowing about reboots, and the firewall rules will just work (assuming pfsense supports using prefix relative rules, vs hardcoding the prefix to all firewall rules...)
Re:The world in which IPv6 was a good design (2017) by magicalhippo on Friday June 14, 2019 @06:33AM (#20181863)
The cable modem is a dumb bridge, and the pfSense is doing the routing (AFAIK). I can't see any way to do relative rules though, which is what makes it difficult. Maybe I'm missing something though.
Re:The world in which IPv6 was a good design (2017) by fulafel on Friday June 14, 2019 @08:46AM (#20182511)
The manual seems to talk about host and network aliases, which might be what you want. Hopefully there are magic aliases for the interface networkts.

edit: https://docs.netgate.com/pfsense/en/latest/firewall/firewall... also talks about "LAN net" and "WAN net" aliases.

Re:The world in which IPv6 was a good design (2017) by stingraycharles on Thursday June 13, 2019 @03:51AM (#20172609)
Not necessarily. How would I go about making these IPs easily discoverable by other hosts? DNS again?
Re:The world in which IPv6 was a good design (2017) by teddyh on Thursday June 13, 2019 @05:01AM (#20172917)
Or mDNS: http://www.multicastdns.org/

As used by Apple’s Bonjour implementation of the Zeroconf networking stack.

If using Debian or the like, just apt install avahi-daemon and libnss-mdns, and access your hosts on the local network as servername.local.

Re:The world in which IPv6 was a good design (2017) by starfox64_ on Thursday June 13, 2019 @05:02AM (#20172922)
Yes, you would probably then have to allow inbound traffic to these addresses in your ISP router's firewall or whatever you have.

If your router's default configuration is sane it should (by default) only allow returning connections and drop any other.

Re:The world in which IPv6 was a good design (2017) by zamadatix on Thursday June 13, 2019 @09:46AM (#20174770)
If you want outside-of-your-home things to reach dynamically assigned public IP space then DDNS is your only option (there are public servers you can use if you're willing to make that trade as well).

If you just want your local stuff to have public IPv6 outbound and static IPv6 inside your home then you can just multinet. That is add a static private IPv6 to the same interface you get your public IPv6 via SLAAC.