4 ms·

If anyone wants to use GitHub from their IPv6 only VMs I would recommend a SSH reverse tunnel. It works like this: https://unix.stackexchange.com/questions/1161

If anyone wants to use GitHub from their IPv6 only VMs I would recommend a SSH reverse tunnel. It works like this: https://unix.stackexchange.com/questions/116191/give-server-access-to-internet-via-client-connecting-by-ssh https://unix.stackexchange.com/questions/116191/give-server-...

zokier 3y ago
You don't actually need ssh tunnel here though, you can just connect directly to the proxy server?
- nromiun 3y ago
  In this case the PC is the proxy, which sometimes does not have a public IP address (behind ISP NAT).
- p1mrx 3y ago
  Some sort of NAT64 is probably a better idea, because that applies below the TLS layer. When people complain about IPv6 and IPv4 being incompatible, the fact that you can establish a cross-protocol TCP+TLS session with just a NAT is a remarkable counterexample. It could've been a lot worse.
  - zokier 3y ago
    Sure, there never was a shortage of different ipv4/ipv6 transition/interop mechanisms. Problem has been that many of them haven't been all that great, and understanding the use-cases, compromises, and tradeoffs between the options can be very difficult, especially when vendors and operators like to tout their own tech. To this day I'm not sure what are the best options available now for different scenarios. 4rd/MAP-T/MAP-E/464XLAT/Dslite, nat64/siit/a+p, these things are enough to get your head spinning
    - p1mrx 3y ago
      "Reality has a surprising amount of detail"
    - ianburrell 3y ago
      The transition mechanisms that need to worry about now are NAT64, MAP-T, and XLAT. Only the first do you have to worry about setting up unless you are ISP. The rest are obsolete. NAT64 is used for IPv6-only networks to talk to IPv4. It puts the IPv4 address in the IPv6 address. The downside is that doesn't work with old IPv4-only software. XLAT is used on mobile phones, and does the translation on the device. It only works for devices where translator can be installed. MAP-T can be used for IPv6 ISP to provide IPv4 access. It is basically CGNAT but using IPv6 as stateless transport.
      - wmf 3y ago
        That's for outbound; don't forget SIIT-DC for inbound.
  - ianburrell 3y ago
    AWS NAT Gateways support NAT64/DNS64. I'm not sure if it is on by default or have to enable it. You have to pay for it, but paying for NAT Gateway for IPv4.
nextaccountic 3y ago
why isn't github accessible through ipv6 without a reverse tunnel?
- wmf 3y ago
  Extreme laziness.
- supertrope 3y ago
  It is more profitable to defer upgrades that do not immediately yield more revenue.

zokier 3y ago

You don't actually need ssh tunnel here though, you can just connect directly to the proxy server?

nromiun 3y ago
In this case the PC is the proxy, which sometimes does not have a public IP address (behind ISP NAT).
p1mrx 3y ago
Some sort of NAT64 is probably a better idea, because that applies below the TLS layer. When people complain about IPv6 and IPv4 being incompatible, the fact that you can establish a cross-protocol TCP+TLS session with just a NAT is a remarkable counterexample. It could've been a lot worse.
- zokier 3y ago
  Sure, there never was a shortage of different ipv4/ipv6 transition/interop mechanisms. Problem has been that many of them haven't been all that great, and understanding the use-cases, compromises, and tradeoffs between the options can be very difficult, especially when vendors and operators like to tout their own tech. To this day I'm not sure what are the best options available now for different scenarios. 4rd/MAP-T/MAP-E/464XLAT/Dslite, nat64/siit/a+p, these things are enough to get your head spinning
  - p1mrx 3y ago
    "Reality has a surprising amount of detail"
  - ianburrell 3y ago
    The transition mechanisms that need to worry about now are NAT64, MAP-T, and XLAT. Only the first do you have to worry about setting up unless you are ISP. The rest are obsolete. NAT64 is used for IPv6-only networks to talk to IPv4. It puts the IPv4 address in the IPv6 address. The downside is that doesn't work with old IPv4-only software. XLAT is used on mobile phones, and does the translation on the device. It only works for devices where translator can be installed. MAP-T can be used for IPv6 ISP to provide IPv4 access. It is basically CGNAT but using IPv6 as stateless transport.
    - wmf 3y ago
      That's for outbound; don't forget SIIT-DC for inbound.
- ianburrell 3y ago
  AWS NAT Gateways support NAT64/DNS64. I'm not sure if it is on by default or have to enable it. You have to pay for it, but paying for NAT Gateway for IPv4.

nextaccountic 3y ago

why isn't github accessible through ipv6 without a reverse tunnel?

wmf 3y ago
Extreme laziness.
supertrope 3y ago
It is more profitable to defer upgrades that do not immediately yield more revenue.