6 ms·

I'm running my home network IPv6-only since some time and it works fine thanks to DNS64/NAT64. I think once more ISPs start offering DNS64/NAT64 internally the

I'm running my home network IPv6-only since some time and it works fine thanks to DNS64/NAT64. I think once more ISPs start offering DNS64/NAT64 internally the transition will be quite unnoticeable for endusers. Software that still does not work because it uses hardcoded ipv4 addresses or sockets: Steam, WoW (probably many other Games too), node/npm (before version 17), but for the most part it works! The offenders can also mostly be fixed using clatd.

tialaramex 5y ago
WoW used to work. A bunch of people at my (IPv6 friendly) ISP used to play it and made a big deal about the fact that WoW was actually IPv6-enabled. At some point they broke it [Edited to clarify: Blizzard broke it, not my ISP]
- hansel_der 5y ago
  i guess the outcry over the breakage was ... limited?
- havkd 5y ago
  There’s a checkbox in the wow client to connect through ipv6. I used it a few months ago and it worked properly. Was it broken recently?
phaer 5y ago
> The offenders can also mostly be fixed using clatd. I had not heard of https://github.com/toreanderson/clatd https://github.com/toreanderson/clatd before, might be new to others as well: " It allows an IPv6-only host to have IPv4 connectivity that is translated to IPv6 before being routed to an upstream PLAT (which is typically a Stateful NAT64 operated by the ISP) and there translated back to IPv4 before being routed to the IPv4 internet. "
- naranha 5y ago
  I think Android includes it too, because some services bind to clat-like ipv4s. But I have not investigated this further so far.
  - ignoramous 5y ago
    Yep, see: https://sites.google.com/site/tmoipv6/464xlat https://sites.google.com/site/tmoipv6/464xlat
LeoPanthera 5y ago
I want to do this, but Comcast's prefix isn't stable, I get a different one every time my lease renews, which means it is impossible to have a static IP for all my network devices, since neither pfSense nor OPNsense support NPTv6 to a dynamic prefix.
- throw0101a 5y ago
  > neither pfSense nor OPNsense support NPTv6 to a dynamic prefix. If you wish to keep track, I believe this is where pfSense is working on this: * https://redmine.pfsense.org/issues/4881 https://redmine.pfsense.org/issues/4881
  - LeoPanthera 5y ago
    A 6 year old bug, that depends on a 5 year old bug. I won't hold my breath!
- naranha 5y ago
  Hmm yes I have several static prefixes, so that helps. I'm in the EU though...
- gerdesj 5y ago
  That is pretty dreadful. You may be able to use RFC 4193 (ULA) addresses to get some stability but then what you get is a sort of buggered up IPv4 experience with really long addresses. It would make a worthy challenge, the struggle would be legendary etc 8)
  - sedachv 5y ago
    > the struggle would be legendary You just assign a ULA address to an interface and that's it. There is no "struggle."
    - gerdesj 5y ago
      Quite. I was making a rather bad joke.
mey 5y ago
What network equipment do you use inside your home? Ubiquity has driven me nuts with the poor IPv6 support. I expect the US consumer home network gear is in just as bad of shape. Trying to upgrade my Comcast modem to IPv6 gave me a device that hard crashed every 6 days to 1 month, that had to be replaced 6 times until they finally would give me the next model up to fix the problem properly. Edit: This is for a business modem owned by Comcast, needed because of a static IP config.
- naranha 5y ago
  Just a $40 openwrt router basically. It uses Jool.mx for NAT64. And I simply use Google or Cloudflare for DNS64.
- toast0 5y ago
  > Trying to upgrade my Comcast modem to IPv6 gave me a device that hard crashed every 6 days to 1 month, Could be worse. The CenturyLink CPE I had would crash and reboot if a fragmented ipv6 packet touched it. The replacement didn't do that, but had some trigger that ended up with massive extra latency.
- judge2020 5y ago
  Residential AT&T Fiber with their own equipment seems to work pretty flawlessly for me - stable v4 IP and v6 prefix even across hours-long disconnects.
gorgoiler 5y ago
My cell provider does the same thing.
slownews45 5y ago
How did you get your ISP to give you a static IP block or prefix? I can get an IPv4 block, but despite the yelling of the IPv6 fanatics regarding how many IPv6 addresses are available, I can't get anyone to allocate me even 20 or so (much less a prefix!). Is there something in the spec that makes this hard to do. It's been 20 years.
- naranha 5y ago
  Luckily here in France there are 8 static /64 prefixes included in a standard DSL or Fiber offering. Just luck i guess...
- zamadatix 5y ago
  You don't need a static address or block to NAT and for the internal side there is private space just like v4.
  - slownews45 5y ago
    I am asking, under IPv4 I can trivially get a static block of IPs. I can then trivially * put some devices on a VLAN (ie, a VOIP phone) and it will have a public IP, globally routable. This works well in my experience, latency is super annoying on VoIP and for some reason behind a NAT sometimes it seems to route media through a third party server! For a small business you can put a PBX on the VLAN and folks can remote register to it trivially (ie, phone.companyZ.com) - with COVID this is great. You can VPN terminate more easily with a static ip block. At home I can do a game server on the static IP block or I can host some of the simultaneous music composition stuff (trivially). My question is simple - how do I get a static IPv6 block so I can do all this if I want to on IPv6. I get IPv4 is outdated, but how do I do some of this stuff in the fancy IPv6? You are telling me IPv6 means I don't need any public static IPs and can use some private IPv6 space (10.x was already plenty for that for me in ipv4) with a dynamic public IPv6. Fine, how does this work. Seriously, what VPN endpoint am I configuring? How does my VOIP / SIP play with this? Do I need to go back to poking weird holes in a NAT? My OWN experience was this all doesn't play well together. Firewalls seem not to play well with dynamic prefixes - and that's just the start. Devices pick up the wrong IP's internally (SIP etc). In short - 20 years into this, when I try to do something simple -> stick my VoIP phone on a static public IP and VLAN -> its a total pain. At a small biz, if I try and put a PBX on a static public IPv6 - it's a total pain (and BTW - the SIP IPv6 support in most hardware and softphones is terrible). This should be the winning use case. Phone calls / person to person audio would benefit TREMENDOUSLY from direct peering connections without any NAT! But despite an insane number if IPv6 addresses at least in the US they won't assign you a block of even 20.
amaccuish 5y ago
I did this with bind and static routing but Spotify refused to work :(

tialaramex 5y ago

WoW used to work. A bunch of people at my (IPv6 friendly) ISP used to play it and made a big deal about the fact that WoW was actually IPv6-enabled. At some point they broke it [Edited to clarify: Blizzard broke it, not my ISP]

hansel_der 5y ago
i guess the outcry over the breakage was ... limited?
havkd 5y ago
There’s a checkbox in the wow client to connect through ipv6. I used it a few months ago and it worked properly. Was it broken recently?

phaer 5y ago

> The offenders can also mostly be fixed using clatd. I had not heard of https://github.com/toreanderson/clatd https://github.com/toreanderson/clatd before, might be new to others as well: " It allows an IPv6-only host to have IPv4 connectivity that is translated to IPv6 before being routed to an upstream PLAT (which is typically a Stateful NAT64 operated by the ISP) and there translated back to IPv4 before being routed to the IPv4 internet. "

naranha 5y ago
I think Android includes it too, because some services bind to clat-like ipv4s. But I have not investigated this further so far.
- ignoramous 5y ago
  Yep, see: https://sites.google.com/site/tmoipv6/464xlat https://sites.google.com/site/tmoipv6/464xlat

LeoPanthera 5y ago

I want to do this, but Comcast's prefix isn't stable, I get a different one every time my lease renews, which means it is impossible to have a static IP for all my network devices, since neither pfSense nor OPNsense support NPTv6 to a dynamic prefix.

throw0101a 5y ago
> neither pfSense nor OPNsense support NPTv6 to a dynamic prefix. If you wish to keep track, I believe this is where pfSense is working on this: * https://redmine.pfsense.org/issues/4881 https://redmine.pfsense.org/issues/4881
- LeoPanthera 5y ago
  A 6 year old bug, that depends on a 5 year old bug. I won't hold my breath!
naranha 5y ago
Hmm yes I have several static prefixes, so that helps. I'm in the EU though...
gerdesj 5y ago
That is pretty dreadful. You may be able to use RFC 4193 (ULA) addresses to get some stability but then what you get is a sort of buggered up IPv4 experience with really long addresses. It would make a worthy challenge, the struggle would be legendary etc 8)
- sedachv 5y ago
  > the struggle would be legendary You just assign a ULA address to an interface and that's it. There is no "struggle."
  - gerdesj 5y ago
    Quite. I was making a rather bad joke.

mey 5y ago

What network equipment do you use inside your home? Ubiquity has driven me nuts with the poor IPv6 support. I expect the US consumer home network gear is in just as bad of shape. Trying to upgrade my Comcast modem to IPv6 gave me a device that hard crashed every 6 days to 1 month, that had to be replaced 6 times until they finally would give me the next model up to fix the problem properly. Edit: This is for a business modem owned by Comcast, needed because of a static IP config.

naranha 5y ago
Just a $40 openwrt router basically. It uses Jool.mx for NAT64. And I simply use Google or Cloudflare for DNS64.
toast0 5y ago
> Trying to upgrade my Comcast modem to IPv6 gave me a device that hard crashed every 6 days to 1 month, Could be worse. The CenturyLink CPE I had would crash and reboot if a fragmented ipv6 packet touched it. The replacement didn't do that, but had some trigger that ended up with massive extra latency.
judge2020 5y ago
Residential AT&T Fiber with their own equipment seems to work pretty flawlessly for me - stable v4 IP and v6 prefix even across hours-long disconnects.

gorgoiler 5y ago

My cell provider does the same thing.

slownews45 5y ago

How did you get your ISP to give you a static IP block or prefix? I can get an IPv4 block, but despite the yelling of the IPv6 fanatics regarding how many IPv6 addresses are available, I can't get anyone to allocate me even 20 or so (much less a prefix!). Is there something in the spec that makes this hard to do. It's been 20 years.

naranha 5y ago
Luckily here in France there are 8 static /64 prefixes included in a standard DSL or Fiber offering. Just luck i guess...
zamadatix 5y ago
You don't need a static address or block to NAT and for the internal side there is private space just like v4.
- slownews45 5y ago
  I am asking, under IPv4 I can trivially get a static block of IPs. I can then trivially * put some devices on a VLAN (ie, a VOIP phone) and it will have a public IP, globally routable. This works well in my experience, latency is super annoying on VoIP and for some reason behind a NAT sometimes it seems to route media through a third party server! For a small business you can put a PBX on the VLAN and folks can remote register to it trivially (ie, phone.companyZ.com) - with COVID this is great. You can VPN terminate more easily with a static ip block. At home I can do a game server on the static IP block or I can host some of the simultaneous music composition stuff (trivially). My question is simple - how do I get a static IPv6 block so I can do all this if I want to on IPv6. I get IPv4 is outdated, but how do I do some of this stuff in the fancy IPv6? You are telling me IPv6 means I don't need any public static IPs and can use some private IPv6 space (10.x was already plenty for that for me in ipv4) with a dynamic public IPv6. Fine, how does this work. Seriously, what VPN endpoint am I configuring? How does my VOIP / SIP play with this? Do I need to go back to poking weird holes in a NAT? My OWN experience was this all doesn't play well together. Firewalls seem not to play well with dynamic prefixes - and that's just the start. Devices pick up the wrong IP's internally (SIP etc). In short - 20 years into this, when I try to do something simple -> stick my VoIP phone on a static public IP and VLAN -> its a total pain. At a small biz, if I try and put a PBX on a static public IPv6 - it's a total pain (and BTW - the SIP IPv6 support in most hardware and softphones is terrible). This should be the winning use case. Phone calls / person to person audio would benefit TREMENDOUSLY from direct peering connections without any NAT! But despite an insane number if IPv6 addresses at least in the US they won't assign you a block of even 20.

amaccuish 5y ago

I did this with bind and static routing but Spotify refused to work :(