2 ms·

> Do you know enough to assign addresses in a way that you, not your router, wants? If I want to manually assign addresses it's still pretty simple, but in the

> Do you know enough to assign addresses in a way that you, not your router, wants? If I want to manually assign addresses it's still pretty simple, but in the end I normally just don't care. I don't want to know what IP my printer is, I just want to reach it. Which isn't a challenge at all. Even for things at my home that are IPv4 only they're practically all DHCP. Because there's little reason to ever really care about something's address. > Can you ssh/other forms of remote into any machine that accepts ssh on your local network using only ipv6? I have no problems reaching any host on any of my networks even if they're running only IPv6. It's nice too because I can trivially reach any port I want globally as well with a basic firewall change. Even better I can have one host have many IP addresses with different services bound to each address if I want. > Can you redirect ports to specific local machines using only ipv6 (that implies they keep constant addresses)? Why do any port redirection at all? Just set the firewall rule and things can hit it. And yeah, they can keep constant addresses. They can have dozens, hundreds of static host addresses if I want. > Can you easily switch between two internet connections going through different routers that are plugged into the same switch for any machine on your local network using only ipv6? If that's something you're really wanting, Network Prefix Translation can be done pretty easily. But the vast majority of home users aren't using dual WAN anyways. > This is all easily doable with ipv4 in like two afternoons Sounds like your setup with IPv4 took more work than mine with IPv6, as mine only took me an hour or so while yours took multiple days.

nottorp 2y ago
> as mine only took me an hour or so while yours took multiple days. Yeah, because the first time I had no idea what I was doing, except vague feelings about ipv4 works. Did you factor in your pre existing ipv6 knowledge when you counted just an hour? > Network Prefix Translation can be done pretty easily. What's "easily"? How many services do I need to setup? Some other helpful HNer tried to explain to me once and the list was like 2 or 3 daemons in addition to dhcp, firewall etc. Do you set up complex ipv6 networks at work?
- vel0city 2y ago
  > Do you set up complex ipv6 networks at work? Your standard was "It's unusable on your fucking home network." I've set up and managed IPv6 at work before, yes. I don't know if I'd call them "complex" networks though. Either way I set it up at home several years before. And I had been running IPv6 at home before I even bothered setting it up in a way I wanted, as my ISP's box previously had a decently competent SLAAC and IPv6 firewall setup in their CPE router. So that took me 0 minutes of time past plugging it in. As for this disdain of running such complicated systems like "DNS", so many things support mDNS these days and plenty of home routers will automatically update their local DNS with DHCP entries. I didn't have to manually configure a DNS entry for my printer, I just gave it the hostname "brother" when I first set it up and now when I need to add it, I just do "brother" on a new computer and boom it finds it wherever it is. If I want to check the toner level, I open a browser and go to http://brother http://brother and its there. And even though I've radically changed my networking setups over the years, all my configurations pointing to "brother" still just work. > What's "easily"? https://docs.netgate.com/pfsense/en/latest/nat/npt.html https://docs.netgate.com/pfsense/en/latest/nat/npt.html There's seven configuration options here including the Disable/Enable checkbox and a description field. If you're using ip6tables on your router, it is just two commands for a POSTROUTING and PREROUTING nat rules. ip6tables -t nat -A POSTROUTING -o eth0.99 -j NETMAP --to 2607:xxx::/64 -s fd12:3456::/64 ip6tables -t nat -A PREROUTING -i eth0.99 -j NETMAP -d 2607:xxx::/64 --to fd12:3456::/64 But hey just complain about how it's just impossible and takes so much work instead of actually learning new things. From the sibling comment: > No, with ipv4 i can just change the default route :) Are you suggesting you're running around and changing the default route on all the devices on your network when a gateway goes down? What a nightmare. Just have your router have multiple WAN connections and have it do the failover for you. > I have absolutely no problem remembering the last byte of any machine on my network If you want, you can do the same with IPv6. You could set your stuff to have your IP addresses be fd12:3456::1, then fd12:3456::2, then fd12:3456::3, then fd12:3456::4, then fd12:3456::5, etc. Remembering 123456 as your home ULA prefix isn't too challenging, is it? You can then set up an NPT rule like the one above on your router to translate this prefix fd12:3456::/64 with whatever your public prefix is from your ISP. Most wouldn't do this though, as its essentially the Fisher Price of networking designs.

nottorp 2y ago

> as mine only took me an hour or so while yours took multiple days. Yeah, because the first time I had no idea what I was doing, except vague feelings about ipv4 works. Did you factor in your pre existing ipv6 knowledge when you counted just an hour? > Network Prefix Translation can be done pretty easily. What's "easily"? How many services do I need to setup? Some other helpful HNer tried to explain to me once and the list was like 2 or 3 daemons in addition to dhcp, firewall etc. Do you set up complex ipv6 networks at work?

vel0city 2y ago
> Do you set up complex ipv6 networks at work? Your standard was "It's unusable on your fucking home network." I've set up and managed IPv6 at work before, yes. I don't know if I'd call them "complex" networks though. Either way I set it up at home several years before. And I had been running IPv6 at home before I even bothered setting it up in a way I wanted, as my ISP's box previously had a decently competent SLAAC and IPv6 firewall setup in their CPE router. So that took me 0 minutes of time past plugging it in. As for this disdain of running such complicated systems like "DNS", so many things support mDNS these days and plenty of home routers will automatically update their local DNS with DHCP entries. I didn't have to manually configure a DNS entry for my printer, I just gave it the hostname "brother" when I first set it up and now when I need to add it, I just do "brother" on a new computer and boom it finds it wherever it is. If I want to check the toner level, I open a browser and go to http://brother http://brother and its there. And even though I've radically changed my networking setups over the years, all my configurations pointing to "brother" still just work. > What's "easily"? https://docs.netgate.com/pfsense/en/latest/nat/npt.html https://docs.netgate.com/pfsense/en/latest/nat/npt.html There's seven configuration options here including the Disable/Enable checkbox and a description field. If you're using ip6tables on your router, it is just two commands for a POSTROUTING and PREROUTING nat rules. ip6tables -t nat -A POSTROUTING -o eth0.99 -j NETMAP --to 2607:xxx::/64 -s fd12:3456::/64 ip6tables -t nat -A PREROUTING -i eth0.99 -j NETMAP -d 2607:xxx::/64 --to fd12:3456::/64 But hey just complain about how it's just impossible and takes so much work instead of actually learning new things. From the sibling comment: > No, with ipv4 i can just change the default route :) Are you suggesting you're running around and changing the default route on all the devices on your network when a gateway goes down? What a nightmare. Just have your router have multiple WAN connections and have it do the failover for you. > I have absolutely no problem remembering the last byte of any machine on my network If you want, you can do the same with IPv6. You could set your stuff to have your IP addresses be fd12:3456::1, then fd12:3456::2, then fd12:3456::3, then fd12:3456::4, then fd12:3456::5, etc. Remembering 123456 as your home ULA prefix isn't too challenging, is it? You can then set up an NPT rule like the one above on your router to translate this prefix fd12:3456::/64 with whatever your public prefix is from your ISP. Most wouldn't do this though, as its essentially the Fisher Price of networking designs.