Hello there,
Regarding RTT v4 vs v6 I did something "interesting" recently,
would like to know your thoughs.
If you ping6 your loopback (let´s say 1000 packets) interface
with Windows or Linux, v6 is faster.
Now try the same on MAC (El capitan for example).., v6 is 20-25% slower.
I did the above with many devices (and asked some friends) and
the behavior was pretty much the same.
MAC:
--- 127.0.0.1 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.037/0.098/1.062/0.112 ms
--- ::1 ping6 statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.058/0.120/0.194/0.027 ms
Linux:
--- 127.0.0.1 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time
98999ms
rtt min/avg/max/mdev = 0.015/0.021/0.049/0.007 ms
--- ::1 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time
99013ms
rtt min/avg/max/mdev = 0.019/0.031/0.040/0.004 ms
Windows 10:
Ping statistics for ::1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping statistics for 127.0.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 0ms
Bye,
wetheitteam.com
Where to order pain Relief without prescription
vivo v15 pro
Site dedicated mainly to internetworking. The goal is to share experiences, teach IP, IPv6. Talk about Linux, IP services, servers, promote IPv6 adoption, routing protocols, security and in some cases just some thoughts. Keywords: linux, cisco, ospf, bgp, eigrp, ip, ipv6, sla, link, routers, routings, telco, telecommunications, security, ipv4
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Monday, August 21, 2017
Friday, January 1, 2016
Virtualbox in Windows. Bridge adapter + IPv6 not working
Introduction:
When trying to use IPv6 in Virtualbox inside a guest where the adapter is bridge to the wireless interface of the host, the VM does SLAAC correctly but HTTP or ping6 does not work.
Solution:
To solve this issue just reinstall/repair your current Virtualbox instalattion (version 5) adding the following parameters to the installer: "-Win.exe -msiparams NETWORKTYPE=NDIS5"
The result would be something like:
G:\>VirtualBox-5.0.12-104815-Win.exe -msiparams NETWORKTYPE=NDIS5
So, you cannot double click on the installer, you need to do it from command line with admin privileges.
Workaround:
The problem is only with the bridging to the wireless adapter, you, if possible, you could bridge to a non-wireless interface and IPv6 should work perfectly.
References:
https://www.virtualbox.org/ticket/14457
Good luck,
When trying to use IPv6 in Virtualbox inside a guest where the adapter is bridge to the wireless interface of the host, the VM does SLAAC correctly but HTTP or ping6 does not work.
Solution:
To solve this issue just reinstall/repair your current Virtualbox instalattion (version 5) adding the following parameters to the installer: "-Win.exe -msiparams NETWORKTYPE=NDIS5"
The result would be something like:
G:\>VirtualBox-5.0.12-104815-Win.exe -msiparams NETWORKTYPE=NDIS5
So, you cannot double click on the installer, you need to do it from command line with admin privileges.
Workaround:
The problem is only with the bridging to the wireless adapter, you, if possible, you could bridge to a non-wireless interface and IPv6 should work perfectly.
References:
https://www.virtualbox.org/ticket/14457
Good luck,
Subscribe to:
Posts (Atom)