我买了一个新的专用服务器,它有两个IPv4地址和一个/56 IPv6子网。当我在专用服务器上切换到我的域名时,我会得到一条消息。但当我从外面弹奏的时候什么也没发生。
所以我通过IPv6.nl等进行了测试,除了连接到我的web服务器之外,一切都很好。测试无法到达我的服务器。我试过打开防火墙的端口,但似乎不起作用。
我的主机名是cp.hshweb.eu,它运行在一个专用服务器(CentOS6.6)上,为虚拟主机安装了Odin。我可以做哪些步骤,并尝试使用IPv6从外部访问我们的服务器?
当我重设网络时,我会收到这样的信息:
[root@cp network-scripts]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... done.
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Determining if ip address 85.214.148.249 is already in use for device eth0...
[ OK ]ip addr显示如下:
[root@cp ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 40:61:86:ee:be:3f brd ff:ff:ff:ff:ff:ff
inet 85.214.208.177/32 brd 85.214.208.177 scope global eth0
inet 85.214.148.249/32 brd 85.214.148.249 scope global eth0:1
inet6 2a01:238:4317:d800:cafe:dead:beef:0/128 scope global
valid_lft forever preferred_lft forever
inet6 2a01:238:4317:d800::feed/128 scope global
valid_lft forever preferred_lft forever
inet6 2a01:238:4317:d800::/56 scope global
valid_lft forever preferred_lft forever
inet6 2a01:238:4317:d800:0:bad:a55:cafe/128 scope global
valid_lft forever preferred_lft forever
inet6 2a01:238:4317:d800:d108:898c:628f:a199/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4261:86ff:feee:be3f/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 40:61:86:ee:be:40 brd ff:ff:ff:ff:ff:ff这是我的ifcfg-eth0文件:
DEVICE="eth0"
BOOTPROTO="dhcp"
DHCPV6C="no"
IPV6INIT="yes"
IPV6_AUTOCONF="no"
IPV6_ROUTER="yes"
NM_CONTROLLED="no"
ONBOOT="yes"
HWADDR=40:61:86:EE:BE:3F
IPV6ADDR="2a01:238:4317:d800:d108:898c:628f:a199/128"
IPV6ADDR_SECONDARIES="2a01:238:4317:d800:0:bad:a55:cafe/128 2a01:238:4317:d800::/56 2a01:238:4317:d800::feed/128 2a01:238:4317:d800:cafe:dead:beef:0/128 2a01:238:4317:d800:d108:898c:628f:a199/128 2a01:238:4317:d800::feed/128 2a01:238:4317:d800:0:bad:a55:cafe/128 2a01:238:4317:d800:cafe:dead:beef:0/128 2a01:238:4317:d800:d108:898c:628f:a199/128 2a01:238:4317:d800::/0"
IPV6_DEFAULTGW=2a01:238:4317:d800::1
IPV6FORWARDING=yes我的网络配置是:
HOSTNAME=cp.domain.tld
NETWORKING=yes
NETWORKING_IPV6=yes
IPV6_DEFAULTDEV=eth0
IPV6FORWARDING=yes
IPV6_AUTOCONF=no
IPV6_AUTOTUNNEL=no
IPV6_DEFAULTGW=2a01:238:4317:d800::1ip -6路线:
[root@cp ~]# ip -6 route
::/96 via :: dev sit0 metric 256 mtu 1480 advmss 1420 hoplimit 4294967295
unreachable ::/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
2a01:238:4317:d800::feed dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
2a01:238:4317:d800:0:bad:a55:cafe dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
2a01:238:4317:d800:cafe:dead:beef:0 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
2a01:238:4317:d800:d108:898c:628f:a199 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
2a01:238:4317:d800::/56 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
default via 2a01:238:4317:d800::1 dev eth0 metric 1 mtu 1500 advmss 1440 hoplimit 4294967295Ping到google返回:
[root@cp ~]# ping6 ipv6.google.com -c 6
PING ipv6.google.com(ham02s13-in-x07.1e100.net) 56 data bytes
From 2a01:238:4317:d800:cafe:dead:beef:0 icmp_seq=2 Destination unreachable: Address unreachable
From 2a01:238:4317:d800:cafe:dead:beef:0 icmp_seq=3 Destination unreachable: Address unreachable
From 2a01:238:4317:d800:cafe:dead:beef:0 icmp_seq=4 Destination unreachable: Address unreachable
From 2a01:238:4317:d800:cafe:dead:beef:0 icmp_seq=5 Destination unreachable: Address unreachable
From 2a01:238:4317:d800:cafe:dead:beef:0 icmp_seq=6 Destination unreachable: Address unreachable
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, +5 errors, 100% packet loss, time 15001ms发布于 2015-06-22 22:51:21
最好的方法是检查是否可以从服务器上与IPv6站点(如ipv6.google.com )进行对话。这将帮助您确定问题是本地配置还是IPv6连接--如果您可以平移远程IPv6站点,问题可能是防火墙或HTTP守护进程,但如果不能,则是连接。
你有一个可路由的地址。因此,这可能是您的主机或您的传输提供商的问题,或其他地方的路由问题。
不管它的价值如何,在编写本报告时,我无法从我的HE.net隧道中访问您的服务器。
考虑到最新的信息,我还记得我遗漏了一些东西。如果您已经显式地配置了地址(即它不是由RA自动配置的),它看起来就像一个助记符地址,我在您的静态配置中看到了它,它可能不知道它的网关配置。配置它的方式取决于您的发行版,但是它应该就在您配置IP的位置旁边。
对于您的用户,只需在ifcfg-eth0中添加一行:
IPV6_DEFAULTGW=2a01:238:4317:d800::1如果地址是其他的,用正确的网关替换它。检查您是否也可以使用ping6来平那个网关。
Bizzarely,看起来您的发行版也没有为您配置的静态地址添加本地网络路由(因此,它找不到网关)。因此,您需要将其添加到/etc/sysconfig/network-scripts/route6-eth0中:
2a01:238:4317:d800::/56 dev eth0https://serverfault.com/questions/700821
复制相似问题