Solved IPv6 misconfigured?

M

Mayhem30

I've enabled ( or have I ..? ) IPv6 on my dedicated server and it doesn't appear to be working properly.

Note that the IP addresses below have been changed. I did not want to expose my real IP's.

/etc/rc.conf :
Code: 
hostname="localhost"

defaultrouter="70.1.121.1"
ipv6_defaultrouter="2101:AC00:0000:03ba::1"

ifconfig_bge0="inet 70.1.121.30 netmask 255.255.255.0"
ifconfig_bge0_ipv6="inet6 2101:AC00:0000:03ba::160 prefixlen 64"

ifconfig_bge0_alias0="inet 70.1.121.70 netmask 255.255.255.255"
ifconfig_bge0_alias1="inet6 2101:AC00:0000:03ba::170 prefixlen 64"

I can ping the IP locally just fine:

Code: 
$ ping6 2101:AC00:0000:03ba::170
PING6(56=40+8+8 bytes) 2101:AC00:0000:03ba::170 --> 2101:AC00:0000:03ba::170
16 bytes from 2101:AC00:0000:03ba::132, icmp_seq=0 hlim=64 time=0.060 ms
16 bytes from 2101:AC00:0000:03ba::132, icmp_seq=1 hlim=64 time=0.037 ms
16 bytes from 2101:AC00:0000:03ba::132, icmp_seq=2 hlim=64 time=0.036 ms

I am not able to ping or traceroute to 2101:AC00:0000:03ba::160 or 2101:AC00:0000:03ba::170 from my home machine.

Code: 
Pinging example.com [2101:AC00:0000:03ba::160] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2101:AC00:0000:03ba::160:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

I can ping Google, Youtube, etc just fine using IPv6 from home.

Code: 
Pinging youtube.com [2607:f8b0:400a:806::200e] with 32 bytes of data:
Reply from 2607:f8b0:400a:806::200e: time=12ms
Reply from 2607:f8b0:400a:806::200e: time=12ms
Reply from 2607:f8b0:400a:806::200e: time=12ms
Reply from 2607:f8b0:400a:806::200e: time=13ms

Ping statistics for 2607:f8b0:400a:806::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 13ms, Average = 12ms

pf firewall has been disabled.

What am I doing wrong?
 
Mayhem30 said:
Code: 
ipv6_defaultrouter="2101:AC00:0000:03ba::1"
ifconfig_bge0_ipv6="inet6 2101:AC00:0000:03ba::160 prefixlen 64"
Click to expand...
Your default router address doesn't seem correct. May want to double check the information from the provider.

Mayhem30 said:
I can ping the IP locally just fine:
Click to expand...
If you can't ping your own IP address then something's seriously wrong. This never leaves the host, so should always work. From the VPS try to ping something outside your local prefix. Try pinging 2001:4860:4860::8888 for example, that's the IPv6 equivalent of 8.8.8.8 (Google's DNS servers)
 
I can ping the Google DNS servers just fine from my server.

Code: 
2101:AC00:0000:03ba::170 --> 2001:4860:4860::8888
16 bytes from 2001:4860:4860::8888, icmp_seq=0 hlim=59 time=1.286 ms
16 bytes from 2001:4860:4860::8888, icmp_seq=1 hlim=59 time=1.267 ms
16 bytes from 2001:4860:4860::8888, icmp_seq=2 hlim=59 time=1.267 ms
16 bytes from 2001:4860:4860::8888, icmp_seq=3 hlim=59 time=1.254 ms
16 bytes from 2001:4860:4860::8888, icmp_seq=4 hlim=59 time=1.251 ms
 
Did you update your firewall on the host too? You're going to need specific rules for IPv6. Maybe that's what's blocking the pings from your home system?
 
It appears this is a routing issue. My ISP and the datacenter where my dedicated server resides are still trying to figure out what is causing the issue.

The server pings fine from the east coast, but not the west.
 
Mayhem30 said:
It appears this is a routing issue. My ISP and the datacenter where my dedicated server resides are still trying to figure out what is causing the issue.

The server pings fine from the east coast, but not the west.
Click to expand...
That sounds like a peering issue at your ISP.
 
Problem solved.

It ended up being a forward path issue (My ISP -> data centre) via Unitas AS1828.
 
You must log in or register to reply here.
Back
Top