linux – KVM虚拟机无法访问IPv6网站

linux – KVM虚拟机无法访问IPv6网站,第1张

概述我有一个新安装的 Windows Server 2008 R2 SP1虚拟机,尽管显然具有正确的IPv6连接,但它完全无法访问任何IPv6网页.此外,其他 Linux VM也无法访问IPv6网站. 此设置以前已在虚拟机中实现完全IPv6连接,并且在没有明显原因的情况下停止工作. 我的所有虚拟机都桥接到物理以太网,并从主机上的radvd接收通知. IPv6可在主机上正常运行,主机也是IPv6路由器. 我有一个新安装的 Windows Server 2008 R2 SP1虚拟机,尽管显然具有正确的IPv6连接,但它完全无法访问任何IPv6网页.此外,其他 Linux VM也无法访问IPv6网站.

此设置以前已在虚拟机中实现完全IPv6连接,并且在没有明显原因的情况下停止工作.

我的所有虚拟机都桥接到物理以太网,并从主机上的radvd接收通知. IPv6可在主机上正常运行,主机也是IPv6路由器. Wireshark显示主机在收到http SYN数据包后发送回ICMPv6目标无法访问(管理禁止).

Internet Explorer报告无法显示网页,Google Chrome仅显示Oops! Chrome无法连接到网页,没有错误编号.

我甚至能够Ping本地网关和Google的IPv6地址并执行IPv6 DNS查找.

PS C:\Users\administrator> Ping -6 fe80::6e62:6dff:fed1:dfadPinging fe80::6e62:6dff:fed1:dfad with 32 bytes of data:Reply from fe80::6e62:6dff:fed1:dfad: time<1msReply from fe80::6e62:6dff:fed1:dfad: time<1msReply from fe80::6e62:6dff:fed1:dfad: time<1msReply from fe80::6e62:6dff:fed1:dfad: time<1msPing statistics for fe80::6e62:6dff:fed1:dfad:    Packets: Sent = 4,Received = 4,Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 0ms,Maximum = 0ms,Average = 0msPS C:\Users\administrator> Ping -6 www.Google.comPinging www.l.Google.com [2001:4860:800a::67] with 32 bytes of data:Reply from 2001:4860:800a::67: time=43msReply from 2001:4860:800a::67: time=42msReply from 2001:4860:800a::67: time=46msReply from 2001:4860:800a::67: time=42msPing statistics for 2001:4860:800a::67:    Packets: Sent = 4,Approximate round trip times in milli-seconds:    Minimum = 42ms,Maximum = 46ms,Average = 43ms

我的虚拟机配置如下所示:

PS C:\Users\administrator> ipconfig /allwindows IP Configuration   Host name . . . . . . . . . . . . : WIN-CRLO5NIQB72   Primary Dns Suffix  . . . . . . . :   Node Type . . . . . . . . . . . . : HybrID   IP Routing Enabled. . . . . . . . : No   WINS Proxy Enabled. . . . . . . . : No   DNS Suffix Search List. . . . . . : localEthernet adapter Local Area Connection 2:   Connection-specific DNS Suffix  . : local   Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter   Physical Address. . . . . . . . . : 52-54-00-DD-DF-3E   DHCP Enabled. . . . . . . . . . . : Yes   autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:db8:1600:80bf:5054:ff:fedd:df3e(Preferred)   link-local IPv6 Address . . . . . : fe80::5054:ff:fedd:df3e%13(Preferred)   IPv4 Address. . . . . . . . . . . : 192.168.12.146(Preferred)   subnet Mask . . . . . . . . . . . : 255.255.255.0   Lease Obtained. . . . . . . . . . : Monday,July 09,2012 1:59:42 PM   Lease Expires . . . . . . . . . . : Tuesday,July 10,2012 1:59:42 PM   Default Gateway . . . . . . . . . : fe80::6e62:6dff:fed1:dfad%13                                       192.168.12.1   DHCP Server . . . . . . . . . . . : 192.168.12.1   DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888                                       2001:4860:4860::8844                                       192.168.12.1   NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter isatap.local:   Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix  . : local   Description . . . . . . . . . . . : Microsoft ISATAP Adapter   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   autoconfiguration Enabled . . . . : YesTunnel adapter Teredo Tunneling Pseudo-Interface:   Connection-specific DNS Suffix  . :   Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:10d1:317d:3f57:f36d(Preferred)   link-local IPv6 Address . . . . . : fe80::10d1:317d:3f57:f36d%12(Preferred)   Default Gateway . . . . . . . . . :   NetBIOS over Tcpip. . . . . . . . : DisabledPS C:\Users\administrator> netsh interface ipv6 show routePublish  Type      Met  Prefix                    IDx  Gateway/Interface name-------  --------  ---  ------------------------  ---  ------------------------No       Manual    256  ::/0                       13  fe80::6e62:6dff:fed1:dfadNo       Manual    256  ::1/128                     1  Loopback Pseudo-Interface 1No       Manual    8    2001::/32                  12  Teredo Tunneling Pseudo-InterfaceNo       Manual    256  2001:0:4137:9e76:10d1:317d:3f57:f36d/128   12  Teredo Tunneling Pseudo-InterfaceNo       Manual    8    2001:db8:1600:80bf::/64   13  Local Area Connection 2No       Manual    256  2001:db8:1600:80bf:5054:ff:fedd:df3e/128   13  Local Area Connection 2No       Manual    256  fe80::/64                  13  Local Area Connection 2No       Manual    256  fe80::/64                  12  Teredo Tunneling Pseudo-InterfaceNo       Manual    256  fe80::5efe:192.168.12.146/128   11  isatap.localNo       Manual    256  fe80::10d1:317d:3f57:f36d/128   12  Teredo Tunneling Pseudo-InterfaceNo       Manual    256  fe80::5054:ff:fedd:df3e/128   13  Local Area Connection 2No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface 1No       Manual    256  ff00::/8                   13  Local Area Connection 2No       Manual    256  ff00::/8                   12  Teredo Tunneling Pseudo-InterfacePS C:\Users\administrator> netsh interface ipv6 show prefixpolicIEsquerying active state...Precedence  Label  Prefix----------  -----  --------------------------------        50      0  ::1/128        40      1  ::/0        30      2  2002::/16        20      3  ::/96        10      4  ::ffff:0:0/96         5      5  2001::/32

到目前为止我在VM中尝试过:

netsh interface ipv6 set global randomizeIDentifIErs=Disabled

没变.

禁用Teredo适配器:无更改.它以某种方式重新启用.

使用the Microsoft Fix-It to prefer IPv6 over IPv4:没有变化.

到目前为止,我尝试过的东道主:

检查IPv6转发sysctl:

net.ipv6.conf.all.forwarding = 1net.ipv6.conf.br0.forwarding = 1net.ipv6.conf.default.forwarding = 1net.ipv6.conf.em1.forwarding = 1net.ipv6.conf.lo.forwarding = 1net.ipv6.conf.sit0.forwarding = 1net.ipv6.conf.sixxs.forwarding = 1net.ipv6.conf.virbr0.forwarding = 1net.ipv6.conf.virbr0-nic.forwarding = 1net.ipv6.conf.vnet0.forwarding = 1net.ipv6.conf.vnet1.forwarding = 1net.ipv6.conf.vnet2.forwarding = 1

重启radvd:没有变化.

解决方法 ICMPv6目标不可达数据包有助于将问题识别为防火墙问题.

添加规则以在br0上转发IPv6数据包修复了该问题:

ip6tables -I FORWARD 6 -i br0 -s 2001:db8:1600:80bf::/64 -j ACCEPT
总结

以上是内存溢出为你收集整理的linux – KVM虚拟机无法访问IPv6网站全部内容,希望文章能够帮你解决linux – KVM虚拟机无法访问IPv6网站所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。

欢迎分享,转载请注明来源:内存溢出

原文地址: http://outofmemory.cn/yw/1040373.html

(0)
打赏 微信扫一扫 微信扫一扫 支付宝扫一扫 支付宝扫一扫
上一篇 2022-05-24
下一篇 2022-05-24

发表评论

登录后才能评论

评论列表(0条)

保存