6 ms·
> We cannot issue an IPv4 address to each machine without blowing out the cost of the subscription. We cannot use IPv6-only as that means some of the internet c
by miyuru 7mo ago
> We cannot issue an IPv4 address to each machine without blowing out the cost of the subscription. We cannot use IPv6-only as that means some of the internet cannot reach the VM over the web. That means we have to share IPv4 addresses between VMs.
Give a user a option for use IPv6 only, and if the user need legacy IP add it as a additional cost and move on.
Trying to keep v4 at the same cost level as v6 is not a thing we can solve. If it was we wouldn't need v6.
- YesThatTom2 7mo agoThis is the way.
- TZubiri 7mo agoOp solved a problem and your comment is "I wouldn't have solved the problem". >legacy IP lol
- 9dev 7mo agoIt's a nice solution for sure, but a problem by choice. You could just have an AAAA record for the domain in addition to the A record, and as GP pointed out, resolve SSH sessions via the IPv6. If the user wants SSH to work with IPv4 for whatever reason—I see the point that there may be some web visitors without IPv6 still, but devs?—they could pay a small extra for a dedicated IPv4 address.
- lifthrasiir 7mo agoThey could buy a dedicated IPv4 address, but that address still has to be tunneled through [EDIT:] IPv6 networks if that dev has no access to [EDIT:] IPv4 networks. Thus DX still suffers. [ADDENDUM: I mistakenly swapped "IPv4" and "IPv6" there. See comments.]
- 9dev 7mo agoI'm not sure I understand your point; if exe.dev operates a dedicated IP solely so a specific mythical IPv6-less developer can connect to a specific server, then there's no tunnelling involved at all.
- lifthrasiir 7mo agoOops, I think I mixed up two sentences in the middle. A fixed comment is available. But I also probably misinterpreted what you were saying: > they could pay a small extra for a dedicated IPv4 address. Did you mean that the dedicated IPv4 address to connect via SSH? Then my objection doesn't apply.
- michaelt 7mo agoProducts targeted at developers like to get a foothold in large corporations "by stealth" - let the developers experience what a great product it is first, before they have to do the approval paperwork. With this IPv4 trick, if your employer or university only provides IPv4 you can use the product anyway.
- jim33442 7mo agoI've worked in big companies long enough to know that "deprecated" or "legacy" mean "the thing we actually rely on"
- _cenw 7mo agoThis is great if you have IPv6 support from your ISP. Not so great if you don't. Before someone mentions tunnels: Last time I tried to set up a tunnel Happy Eyeballs didn't work for me at all; almost everything went through the tunnel anyway and I had to deal with non-residential IP space issues and way too much traffic.
- miyuru 7mo agoI complained as a yearly tradition for couple of years to get v6 enabled in my ISP. They had the core network enabled on World IPv6 Launch in 2012, but not deployed to end customers. One simple way to check if your ISP have some kind of IPv6 netowork is to see if CDN domains given by YouTube and Facebook have AAAA records. We shouldn't have to ask for ISPs to add IPv6 support but here we are.
- jeroenhd 7mo agoISPs won't bother with IPv6 until they've either run out of IPv4 space or the internet starts to use IPv6's advantages. Discussions about IPv6 quickly end with "we have enough v4 space and there are no services that require v6 anyway". As long as the extra cruft for v4 support remains free or even supported, large ISPs won't care. We're at the point where people need to deal with things like peer to peer connectivity with two sides behind CGNAT which require dedicated effort to even work. I know it sucks if none of the ISPs in your area support IPv6 and you're left with suboptimal solutions like tunnels from HE, but I think it's only reasonable all this extra cost or effort becomes visible at some point. Half the world is on v6, legacy v4-only connections are becoming the minority now.
- rjsw 7mo agoI have has native IPv6 since 2010, from two different ISPs. It is also available for one of my phone contracts but not tried enabling it yet.
- ralferoo 7mo agoConversely, I had IPv6 for about 5 years from an ISP and when I switched providers, the new ISP was IPv4 only. A few years later and they now support IPv6, but my firewall setup is now IPv4 only, so I've not bothered to update it.
- johannes1234321 7mo agoThey could have done that in addition (and maybe they do), but for some of their customers it then may not work, for reasons hard to understand as a customer. Especially when changing locations frequently it may sometimes work and sometimes not ... not good for keeping customers
- jcgl 7mo agoYou could also provide a dual stack jump host. Then v4-only clients just set the ProxyJump option to get to all the v6-only hosts via the jump host.
- crawshaw 7mo ago(exe.dev co-founder here) IPv6 does not work on the only ISP in my neighborhood that provides gigabit links. I will not build a product I cannot use. Even when IPv6 is rolled out, it is only tested for consumer links by Happy Eyeballs. Links between DCs are entirely IPv4 even when dual stacked. We just discovered 20 of our machines in an LAX DC have broken IPv6 (because we tried to use Tailscale to move data to them, which defaults to happy eyeballs). Apparently the upstream switch configuration has been broken for months for hundreds of machines and we are the first to notice. I am a big believer in: first make it work. On the internet today, you first make it work with IPv4. Then you have the luxury of playing with IPv6.
- Imustaskforhelp 7mo agoHave you looked at each service running through a cloudflare tunnel or (HE offers something similar too)? (PS: I use exe.dev quite a lot whenever I want to have a project and basic scripting doesn't work and I want to have a full environment, really thanks for having this product I really appreciate it as someone who has been using it since day one and have recommended/talked about your service in well regards to people :>)
- crawshaw 7mo agoYou can get this effect today by installing Tailscale on your exe.dev VM. :) The reason we put so much effort into exposing these publicly is for sharing with a heterogeneous team without imposing a client agent requirement. The web interface should be easy to make public, easy to share with friends with a Google Docs-style link, and ssh should be easy to share with teammates. That said, nothing wrong with installing tunneling software on the VM, I do it!
- bigstrat2003 7mo agoA service that only does IPv6 is not "working" any more. I'm not saying to go v6 only, but there's no excuse to not support IPv6.
- znpy 7mo ago> IPv6 does not work on the only ISP in my neighborhood that provides gigabit links. I will not build a product I cannot use. Cool. Somebody else will, and will likely have a better price (due to the abundance of ipv6 addresses) and you’ll go out of business. > because we tried to use Tailscale to move data to them, which defaults to happy eyeballs Not gonna lie, to me that reads like “because we don’t know how to use ipv6”
- metadat 7mo agoWhy not just assign across different ports? Seems like a straightforward solution.
- miyuru 7mo agoMy guess is that they want to keep the url clean. I have seen that port technique used in NAT servers.