All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
How does IPv6 even work?
Okay, so I was working on tidying up my servers and stuff when I decided to finally try out IPv6 on a couple of NAT servers. This way i can use my only IPv6+IPv4 server to proxy all the stuff from the servers and be a happy fox.
However, I'm so stupid that i can't even make two vpses ping each other.
I used netstat -A inet6 -rn
to discover my external IPv6 addresses.
```ed@yiff:~$ netstat -A inet6 -rn
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
fe80::/64 :: U 256 0 0 ens3
::/0 :: !n -1 1 68065 lo
::1/128 :: Un 0 2 478 lo
fe80::33ff:fef0:2081/128 :: Un 0 1 0 lo
ff00::/8 :: U 256 1255870 ens3
::/0 :: !n -1 1 68065 lo
Nice, it looks like we have an ip address. Let's fire up the other machine so we can ping the server.
ed@murr:~$ ping6 fe80::33ff:fef0:2081
connect: Invalid argument
Mkay. So I've read online a couple of pages to try to learn more about IPv6 and it looks like that the address i have is actually a whole subnet just for my vps!
http://www.gestioip.net/cgi-bin/subnet_calculator.cgi
Using this nice calculator i discover that i can use any address between fe80::33ff:fef0:2081:0 and fe80::33ff:fef0:2081:ffff!
```ed@murr:~$ ping6 fe80::33ff:fefe:3801::0
ping: fe80::33ff:fefe:3801::0: Name or service not known
Fuck. Now i'm stuck here. What am i doing wrong?
Comments
ifconfig -a | grep inet6
Your "route" is ::/0.
That's the link local.
You are on a local link, dude..
inet6 fe80::33ff:fef0:2081/64 scope link
Welp, don't make me feel more like a retard
fe80 is a link-local address. Its not your public IP.
curl -6 icanhazip.com will tell you your public IP.
What OS/dhcp are you using? What provider?
Everyone starts somewhere. What's the output of
ifconfig
curl: (7) Couldn't connect to server
on both my machinesI'm using Debian Stretch/Testing, provider is Wishosting
I don't think a publicly routable IPv6 is configured on your system.
@edfox Then you dont have ipv6 working currently.
I dont think wishosting actually does ipv6 on their nat servers. Or am I mistaken?
So. are you starting a dhcp daemon capable of taking an IPv6? What's your /etc/network/interfaces look like (even if it is deprecated)
I remember sending a ticket telling @exception0x876 that IPv6 didn't work properly and he fixed it in some way.
My Wishosting NAT have IPv6 just fine, and I can see it using your curl command.
There's not a single ipv6 dhcp request in there.
Add: iface eth0 inet6 dhcp
ed@murr:~$ sudo ifconfig [sudo] password for ed: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.5.xxx netmask 255.255.255.0 broadcast 192.168.5.255 inet6 fe80::216:3cff:fe29:83eb prefixlen 64 scopeid 0x20<link> ether 00:16:3c:29:83:eb txqueuelen 1000 (Ethernet) RX packets 1974 bytes 154192 (150.5 KiB) RX errors 0 dropped 13 overruns 0 frame 0 TX packets 111 bytes 15849 (15.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Done but nothing happened (i restarted network, and rebooted just to make sure)
Is your IPv6 not working at all? Or you just can't find your address?
Can you curl -6 google.com?
On my Online.net dedi, I have no IPv6 connection at all, so curl -6 have no results.
Assuming that your route hasn't changed. I'd ask WIS to see if your MAC is even being vended an address. I'd try to be more helpful but I refuse to endure systemd without pay, so.. I'm outta.
Do they even provide a IPv6 address? Only shows a local IPv6 address. Could set up a tunnel for it, but you should double check with your host.
It's not necessarily so that you need to use DHCPv6 to obtain IPv6. It varies between hosts, and those requiring DHCPv6 are actually in a minority. Check with yours.
And yes currently you do not have any global IPv6 on that machine.
+1 Your hosting company must offers ipv6 on the service you're using to be able to set it up on your server.
@edfox Pass https://ipv6.he.net/certification/ it's really fun and it teaches you while you learn.