4 ms·

Once upon a time I had an original iPhone and a router that did nor have ipv6, but the App Store worked. So I don’t understand your "ipv4 addresses can’t be rea

by rynes 5y ago

Once upon a time I had an original iPhone and a router that did nor have ipv6, but the App Store worked. So I don’t understand your "ipv4 addresses can’t be reached" part.

tialaramex 5y ago
On some people's phones IPv4 addresses can't be reached. Their carrier doesn't bother moving IPv4 over a network that doesn't need IPv4. It does translation at the edge, and the iPhone is OK with that. Apple's requirement is that even though you know your server is definitely 10.20.30.40† on the public network, and you hate IPv6 you must not hard code 10.20.30.40 inside the app and ship that to the App Store. Once you reluctantly change it to a DNS name ten-twenty-thirty-forty.fuck-off-apple.example that resolves to 10.20.30.40 - Apple allows that. Because now when your app is used on some IPv6-only carrier network, the carrier goes "ten-twenty-thirty-forty.fuck-off-apple.example ?" and it gets 10.20.30.40 and it says that's an IPv4 address, don't use those around here, and it adds a translator step, it gives the phone an IPv6 address for ten-twenty-thirty-forty.fuck-off-apple.example and the phone connects to that address, which is a translator that connects to 10.20.30.40 on the IPv4 Internet. This stuff happens all the time and you don't notice. But if Apple allowed app vendors to just scribble IPv4 addresses inside their app software it would break. † No that isn't a public IP address. It's an example.
- teddyh 5y ago
  > † No that isn't a public IP address. It's an example. “The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3) are provided for use in documentation.” — RFC 5737, IPv4 Address Blocks Reserved for Documentation https://www.rfc-editor.org/rfc/rfc5737.html https://www.rfc-editor.org/rfc/rfc5737.html
  - tialaramex 5y ago
    Noted, but 10.20.30.40 kinda trips off the tongue.
    - teddyh 5y ago
      So did 1.1.1.1, which led to a lot of trouble when it started being widely used.
      - tialaramex 5y ago
        Unlike 1.1.1.1, 10.20.30.40 is reserved in RFC1918, you mustn't use it on the Network. So I don't have to care (No I don't use RFC1918 addressing at home; Yes, every machine in my home has public IPv4 and/or IPv6 addresses; No that doesn't make it "really easy to break in" because having an address is not the same thing as being accessible)

by rynes 5y ago

Once upon a time I had an original iPhone and a router that did nor have ipv6, but the App Store worked. So I don’t understand your "ipv4 addresses can’t be reached" part.

tialaramex 5y ago

On some people's phones IPv4 addresses can't be reached. Their carrier doesn't bother moving IPv4 over a network that doesn't need IPv4. It does translation at the edge, and the iPhone is OK with that. Apple's requirement is that even though you know your server is definitely 10.20.30.40† on the public network, and you hate IPv6 you must not hard code 10.20.30.40 inside the app and ship that to the App Store. Once you reluctantly change it to a DNS name ten-twenty-thirty-forty.fuck-off-apple.example that resolves to 10.20.30.40 - Apple allows that. Because now when your app is used on some IPv6-only carrier network, the carrier goes "ten-twenty-thirty-forty.fuck-off-apple.example ?" and it gets 10.20.30.40 and it says that's an IPv4 address, don't use those around here, and it adds a translator step, it gives the phone an IPv6 address for ten-twenty-thirty-forty.fuck-off-apple.example and the phone connects to that address, which is a translator that connects to 10.20.30.40 on the IPv4 Internet. This stuff happens all the time and you don't notice. But if Apple allowed app vendors to just scribble IPv4 addresses inside their app software it would break. † No that isn't a public IP address. It's an example.

teddyh 5y ago
> † No that isn't a public IP address. It's an example. “The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3) are provided for use in documentation.” — RFC 5737, IPv4 Address Blocks Reserved for Documentation https://www.rfc-editor.org/rfc/rfc5737.html https://www.rfc-editor.org/rfc/rfc5737.html
- tialaramex 5y ago
  Noted, but 10.20.30.40 kinda trips off the tongue.
  - teddyh 5y ago
    So did 1.1.1.1, which led to a lot of trouble when it started being widely used.
    - tialaramex 5y ago
      Unlike 1.1.1.1, 10.20.30.40 is reserved in RFC1918, you mustn't use it on the Network. So I don't have to care (No I don't use RFC1918 addressing at home; Yes, every machine in my home has public IPv4 and/or IPv6 addresses; No that doesn't make it "really easy to break in" because having an address is not the same thing as being accessible)