3 ms·

I'm glad that someone is finally doing this. We all really need someone to force us to migrate to v6 finally, and I only did that once I realized I couldn't acc

I'm glad that someone is finally doing this. We all really need someone to force us to migrate to v6 finally, and I only did that once I realized I couldn't access my home network over cellular anymore.

ohazi 8y ago
What do you do if your cellular provider goes IPv6-only, but your home ISP will only give you a v4 address?
- y0ghur7_xxx 8y ago
  > What do you do if your cellular provider goes IPv6-only, but your home ISP will only give you a v4 address? Get a tunnel from he[1] and access the home network through that. [1]https://tunnelbroker.net/ https://tunnelbroker.net/
  - icebraining 8y ago
    Or use a Tor hidden service, and get end-to-end encryption for free (see https://github.com/AnarchoTechNYC/meta/wiki/Connecting-to-an-authenticated-Onion-service https://github.com/AnarchoTechNYC/meta/wiki/Connecting-to-an...)
    - floatboth 8y ago
      I've tried to use onioncat to get from anywhere to NATed home. Performance sucked too much. Switched to an openvpn instance on a VPS :D
    - eeZah7Ux 8y ago
      ...and server authentication, and optional client authentication.
- alex_duf 8y ago
  I don't think your cellular provider would stop you from accessing ipv4 addresses, it just starts the first hop on ipv6, then tunnels it for you to wherever you're trying to reach. The ultimate goal being decommissioning the tunnel once the rest of the world is ready (few decades obviously)
  - kazen44 8y ago
    a variaty of methods exists that accomplish this, including DS-lite, 6in4, 6to4 and XSLAT tunneling.
  - neojima 8y ago
    a) It's a translator, not a tunnel. b) You're ultimately still right that it enables connectivity to IPv4-only resources, but depending on the IPv6 client device, you may NEED to use a DNS 'A' record to get the traffic to use NAT64/DNS64, rather than trying to connect to a bare IPv4 address.
- moduspwnens14 8y ago
  Apple has been requiring all apps on the App Store work on IPv6-only networks for two years now [1]. They require it work on a network with NAT64 and DNS64 set up. Essentially your device gets only an IPv6 address and the router translates IPv4 addresses to IPv6 ones. Your DNS server does the same thing. The end result is that your device talks only native IPv6, but the router is translating back and forth as necessary for IPv4. It's actually pretty easy to test if you have an extra Mac laying around. There's a hidden checkbox on the Network preferences pane that lets any Mac create a NAT64 / DNS64 WiFi network [2]. [1] https://developer.apple.com/support/ipv6/ https://developer.apple.com/support/ipv6/ [2] https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW16 https://developer.apple.com/library/archive/documentation/Ne...

ohazi 8y ago

What do you do if your cellular provider goes IPv6-only, but your home ISP will only give you a v4 address?

y0ghur7_xxx 8y ago
> What do you do if your cellular provider goes IPv6-only, but your home ISP will only give you a v4 address? Get a tunnel from he[1] and access the home network through that. [1]https://tunnelbroker.net/ https://tunnelbroker.net/
- icebraining 8y ago
  Or use a Tor hidden service, and get end-to-end encryption for free (see https://github.com/AnarchoTechNYC/meta/wiki/Connecting-to-an-authenticated-Onion-service https://github.com/AnarchoTechNYC/meta/wiki/Connecting-to-an...)
  - floatboth 8y ago
    I've tried to use onioncat to get from anywhere to NATed home. Performance sucked too much. Switched to an openvpn instance on a VPS :D
  - eeZah7Ux 8y ago
    ...and server authentication, and optional client authentication.
alex_duf 8y ago
I don't think your cellular provider would stop you from accessing ipv4 addresses, it just starts the first hop on ipv6, then tunnels it for you to wherever you're trying to reach. The ultimate goal being decommissioning the tunnel once the rest of the world is ready (few decades obviously)
- kazen44 8y ago
  a variaty of methods exists that accomplish this, including DS-lite, 6in4, 6to4 and XSLAT tunneling.
- neojima 8y ago
  a) It's a translator, not a tunnel. b) You're ultimately still right that it enables connectivity to IPv4-only resources, but depending on the IPv6 client device, you may NEED to use a DNS 'A' record to get the traffic to use NAT64/DNS64, rather than trying to connect to a bare IPv4 address.
moduspwnens14 8y ago
Apple has been requiring all apps on the App Store work on IPv6-only networks for two years now [1]. They require it work on a network with NAT64 and DNS64 set up. Essentially your device gets only an IPv6 address and the router translates IPv4 addresses to IPv6 ones. Your DNS server does the same thing. The end result is that your device talks only native IPv6, but the router is translating back and forth as necessary for IPv4. It's actually pretty easy to test if you have an extra Mac laying around. There's a hidden checkbox on the Network preferences pane that lets any Mac create a NAT64 / DNS64 WiFi network [2]. [1] https://developer.apple.com/support/ipv6/ https://developer.apple.com/support/ipv6/ [2] https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW16 https://developer.apple.com/library/archive/documentation/Ne...