IPv6 only VPS ... setting up IPv4 connection
It seems that IPv6 only vps services will become the next very big thing in the (inexpensive) VPS world.
I've never had a IPv6 only VPS. I was just wondering how to set up IPv4 connectivity to the IPv6 only vps.
I have read this:
https://iblog.ovh/how-to-get-ipv4-connectivity-on-an-ipv6-only-vps/
It seems not too difficult -- or would there be more to do here?
ta, t
Tagged:
Comments
Here's another way - using vxlan
https://yoursunny.com/t/2020/EUserv-IPv4/
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
Tailscale.
Cloudflare WARP could be a possible option too.
NAT64 makes it fairly painless, but it bemuses me that providers will sell you an IPv6-only service without running any sort of NAT64/DNS64 gateway for stupid parts of the internet that refuse to enter the 21st century (yes, GitHub, I'm looking at you).
Yes, there are public services, but it should be a no-brainer for any decent provider to provide something more local for their customers.
There are even providers who want to sell some IPv6-only services, but other services they also want to sell are IPv4-only. Makes for a perfect combination if you want to access one service from the other.
Too bad Microsoft bought them. MS is super weird when it comes to IPv6 support. Some of their services are available through v6. However here comes the irony: their login is ipv4 only... at least that's what it used to be 6 months ago. There have been some blog posts about this. I highly doubt Github will get native ipv6 any time soon. Gitlab on the other hand fully supports ipv6
I would always suggest to connect an ipv6 only server do a dual stack server through a tunnel or whatsoever and avoid any pain.
Offering IPv6 support shouldn't be hard for vast majority anyway.
I don't think it's fair to blame Microsoft for Github's insane resistance to IPv6 - they've been saying "oh yeah we're working on it" for literally decades.
Ipv4 is not expensive enough to be worth my time yet...
Action and Reaction in history
oh the horrors of setting up IPv6 on my azure vm.
youtube.com/watch?v=k1BneeJTDcU
Yeah don't get started on that. Simple solution to that is actually not using ipv6 on any azure server or service at all. Azure overall is quite overpriced for what they deliver tbh but that's just my opinion. In the end it is the company paying for it.
Btw do they still do the Nat thing for ipv6 on azure servers? All I heard was that ipv6 is at least free now and they won't charge 12$+ for a single ipv6 address-
There is quite literally nothing about IPv6 on servers. The docs are too technical. I am trying to add an IP, not setup a Cisco Router through command line (even that is easier).
youtube.com/watch?v=k1BneeJTDcU
As a provider, we do NAT64 and DNS64. Our IPv6 only VPS can reach v4 only destination, with that addition.
F4 Networks | Reliable BGP enabled Colocation, Dedicated & VPS
What packages/stack are you using to achieve this?
how about BW? limited? or full speed of VPS Link?
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
IPv4 hoarders have no interest in pushing IPv6. Microsoft bought 667,000 IPv4 addresses in 2011 from Nortel for $7.5 million on top of what they had already.
They made another purchase of 1.8 million IPv4 addresses [20.160.0.0/12,20.180.0.0/14, 20.184.0.0/13] from Computer Science Corporation (currently known as DXC Technolgy) in February 2017.
https://github.com/Ne00n/wg-mesh
Connect these 2, add a default route on your IPv6 only machine, profit.
Free NAT KVM | Free NAT LXC | Bobr
ITS WEDNESDAY MY DUDES
Yeah, yeah, I get it. Microsoft evil.
I'm just saying, Github's distaste for IPv6 massively predates any involvement from Microsoft; it really has nothing to do with them.
I get it too. Just wanted to say that from a business perspective solely there's not much incentive for MS to push IPv6. At least not for now.
Unlike some newer businesses, they don't feel shortage because they were/are capable of investing in IPv4 hoarding.
We use Tayga for NAT64 and Unbound for DNS64
F4 Networks | Reliable BGP enabled Colocation, Dedicated & VPS
We give 5TB at 500Mbps on our v6 only VPS
F4 Networks | Reliable BGP enabled Colocation, Dedicated & VPS
Besides, they'd devalue their investments by pushing IPv6...
Having a VPS that is connected via mesh in Russia is really useful.
Github is barely usable, no way to update wg-mesh.
ip route add 140.82.112.3 via 10.0.251.1
3 files changed, 37 insertions(+), 13 deletions(-)
Profit
Free NAT KVM | Free NAT LXC | Bobr
ITS WEDNESDAY MY DUDES
I think that IPv4 also helps people centralize the internet in their control so they can censor/deplatform/control the narrative/etc.
Start self hosting with an external IP with IPv6rs.
The only thing between your host and your data is trust. Trust is not security.
wuss
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
I disagree. I don't think providers will ever do IPv6 only
If it's just hobby and staff is free (aka minecraft staff members) it might work. If it's an actual business where you have to pay wages it won't work
People will buy it seeing the price tag, some things won't work because of it being IPv6 only and it will result in either tons of support tickets and refund or cancellation right away. If you outsource support you're paying 3 USD per ticket. Leasing IPv4 from IPXO costs 0.35 USD per IP per month so yeah.. it really doesn't make sense.
Also if you're advertising on Google ads etc it might cost you 30 USD to get a customer. If having IPv6 only leads to worse user experience & higher cancellation rate it's not worth it there either.
"no support" (C1V / MicroNode) and "no refounds" (AliPay and crypto only).
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
But not every server is customer-facing. The important thing is that you don't end up having some IPv6-only and some IPv4-only servers.
I like your absolute confidence that those IPv4's will never ever change in price. You're absolutely wrong but I like your confidence nonetheless.
I don't see v4 ever costing more than the ever increasing paypal tx fees (I hate them. But just like with v6 only, convincing people to pay for their vps via SEPA will probably cost more than it's worth).
They were literally 0.50 USD a couple of months ago when IPv4 entered an all-time high...
The future is IPv6, or at the bare minimum a double stack. On the server used for our sale I was testing until near launch with a NAT + IPv6, but SolusVM doesn't like NAT for no apparent reason and it turns out that demand on NAT is absolutely scarce on that platform, so I went IPv6-only.
Obviously I was preoccupied with accessing the VM, not everyone has residential ISPs with IPv6 yet, but since the management server is double stack and actually allows access from IPv4 via VNC, that sorts things out to a very relevant extent for those on IPv4.
The remainder of it is tunnels, Tailscale, current applications supporting different address formats, etc etc etc. Github is not the best example, apparently keeps several legacy things for no good reason for such a simple platform, and Microsoft... well... if you've invested over 10 million Euros on IPv4 wouldn't you want to protect your investment? I mean, when was even the last time Microsoft made a truly disruptive product, 1995?
It's open source driving IPv6 - closed source will get there. We're already at 45.7% worldwide and when some big guy jumps the gun we'll pass the 50s very, very soon. I don't believe IPv4 will disappear, but I frankly believe it will turn a near-worthless commodity and honestly? It was about time. I mean, they're addresses.