All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Assigning IPv6 to Debian VPS ... How?
Not quite sure what I'm doing wrong here, but after two failed attempts and bricking the fucking network on my box and reinstalling I'm coming here for help.
Got a BuyVM KVM box.
I have:
- Enabled IPv6 in the control panel.
- Added a random IPV6 from my subnet to my VPS, and enabled it.
I then build a VM.
Okay, no IPV6 connectivity on this box.
Read the docs, see: https://wiki.buyvm.net/doku.php/networking
So I update my /etc/network/interfaces to look like this, which I guess I'm supposed to do based on the wiki page? Not entirely sure. Previously was using a Ubuntu box and Netplan made me want to fucking drag my computer behind a truck and gun it down a gravel road.
So, this is what my /etc/network/interfaces looks like in an attempt to get one IPV6 address to work and IPV6, just in general.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# Below is what I add for Luxembourg BuyVM
iface eth0 inet6 static
address THE_IP_I_GENERATED_IN_STALLION/48
netmask 48
gateway 2605:6400:3:fed5::1
And when I restart via systemctl restart networking.service, it just locks up. I can't SSH into the box anymore and as far as I'm concerned it's just easier to start fresh.
I don't want to be frustrated for a third time. What in the hell am I doing wrong? I've read multiple guides on adding IPV6 to a Debian VPS and nothing is standing out as clear to me.
EDIT: So I reinstalled it. I haven't touched /etc/network/interfaces or anything yet.
Out of the box, with IPV6 all enabled in Stallion BEFORE the rebuild, I have no out-of-the-box IPV6 connectivity from the box. Should I?
ip -6 route show | grep default
Nothing.
traceroute -6 dns.google.com
traceroute to dns.google.com (2001:4860:4860::8844), 30 hops max, 80 byte packets
connect: Network is unreachable
lsmod | grep ipv6
Nothing.
ping6 2600::
Network unreachable. And it should work, that's Sprint's network. They just happen to have a really short IPV6 address. But even OpenDNS doesn't work, for good measure checked it too.
ping6 2620:0:ccd::2
Comments
@yoursunny 's show time
lol
Have you reboot the VPS and or access from Stallion console?
So to be clear, I need to enable IPV6 before I build the VPS and make sure it's all assigned (I did that already). Then build the VPS. No IPV6 network connectivity. Then reboot it after I just built it?
Hell, might as well try it. Not sure it'll do anything though.
Ok, I added IPv6 after installing debian 10. First, I change DHCP IPv4 to static IPv4 address. Also I did not use CIDR format for IPv6. Below are my
/etc/network/interfaces
configurationAnd this is MTR to Google.com
@chocolateshirt are you in Luxembourg?
You edited out the part of your IPV6 gateway that'd help me determine if your IPV4 settings would work for me too. Their wiki doesn't publish anything other than the Vegas settings for IPV4 and I don't want to copy your settings (with changing the obvious to my stuff) if the gateway and netmask is going to be incorrect for my location.
Yes, my VPSBin Luxembourg. You could get details of IP address, netmask, and gateway for IPv4 & IPv6 from Stallion.
Go to Networking tab, select IPv4 tab, then find your IP address (make sure Status toggle button is ON) and click Gear icon on right side of it, then click Network Settings. You will get a popup window with detailed IP Address Information above.
You can repeat the same step for IPv6.
@chocolateshirt thanks for the tip about where to find the network info in stallion. I was looking at their wiki and didn't see that mentioned.
I adjusted my
/etc/network/interfaces
to look like yours, pulling data from Stallion of course for my own IPs in question.Saved it. Ran
systemctl restart networking.service
Bricked the network again. I don't get it.
Rebooting now to see if that's some sort of magic fix. I guess I've just been babied in the past with OVZ containers just 'working' with IPs assigned to them so having to mess with this is a bit new to me.
@chocolateshirt hallelujah! That worked. I had to reboot because restarting the service just kills the network but it works now. I have IPV6 capability.
I have another Debian VPS that I want to add multiple IPV6 to. Would I just:
Would that be the appropriate way to add 4 different IPV6 to a box?
Great to see your IPv6 working. Unfortunately I never had a chance to setup multiple IPv6 address so I could not give you any advice.
I've seen this before in Debian, restarting networking just hangs.
Normally I just add a
up ip -6 address add 2a0b:abab:xxxx::xx/64 dev eth0
to just below the gateway line in the relevant section. You can then add one line for as many IPs as you want.Is the VPS provider using a /48 on the outside interface? That's really broken. An IPv6 interface should never be larger than a /64. If you get a /48 then they should route it to you.
Lol.. 😆