Why is the IPV6-WAN so much slower than the IPV4-connection!?
-
Since a long time, so not specially related to 2.7 I notice that the IPV6-WAN response times are much slower than the equivalent IP4-one's
At the top line IPV4 at the bottum IPV6.
Can someone explain if that is normal and what is causing those differences?
-
@louis2 said in Why is the IPV6-WAN so much slower than the IPV4-connection!?:
Since a long time, so not specially related to 2.7 I notice that the IPV6-WAN response times are much slower than the equivalent IP4-one's
At the top line IPV4 at the bottum IPV6.
Can someone explain if that is normal and what is causing those differences?
This is probably due to your ISP. On my systems, there is no difference between IPv4 and IPv6.
-
@louis2 Most probably your ipv6 gateway is slow on replying to pings. Not necessarily a problem.
Try pinging something else at the gateway, maybe your next hop if you traceroute a bit, and see if it gets any better
-
@louis2 said in Why is the IPV6-WAN so much slower than the IPV4-connection!?:
Since a long time, so not specially related to 2.7 I notice that the IPV6-WAN response times are much slower than the equivalent IP4-one's
At the top line IPV4 at the bottum IPV6.
Can someone explain if that is normal and what is causing those differences?
The numbers shown are not a speed indication.
Its shows the result of a up-down ping trajectory.
And you get it : not some destination at the other side of the world.
The tools used, "dpinger" pings probably your upstream 'next-hop' local ISP router next to the pfSense device : that will produce very low values : you are testing the connection between pfSense and your ISP router : and that doesn't make sense.Edit your System > Routing > Gateways > Edit and add a more reasonable IPv4 :
or any other known, rather close but on the internet, IPv4 that you know will reply on pingv4.
Same thing for IPv6 : where is it pinging to ?
-
I just do not know which addresses are used by default. Could be the dhcp-provided DNS-addressess ????
What ever I did a ping test to Google and Cloudfare results below. Not so much differences between IP4 and IP6
GOOGLE
8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=61 time=2.227 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=61 time=2.081 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=61 time=2.147 ms--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.081/2.152/2.227/0.060 ms2001:4860:4860::8844
PING6(56=40+8+8 bytes) 2a02:a468:c48e:1::1 --> 2001:4860:4860::8844
16 bytes from 2001:4860:4860::8844, icmp_seq=0 hlim=119 time=3.987 ms
16 bytes from 2001:4860:4860::8844, icmp_seq=1 hlim=119 time=3.888 ms
16 bytes from 2001:4860:4860::8844, icmp_seq=2 hlim=119 time=3.840 ms--- 2001:4860:4860::8844 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 3.840/3.905/3.987/0.061 msCloudflare
1.0.0.1
PING 1.0.0.1 (1.0.0.1): 56 data bytes
64 bytes from 1.0.0.1: icmp_seq=0 ttl=57 time=5.759 ms
64 bytes from 1.0.0.1: icmp_seq=1 ttl=57 time=5.623 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=57 time=5.689 ms--- 1.0.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.623/5.690/5.759/0.055 ms2606:4700:4700::1001
PING6(56=40+8+8 bytes) 2a02:a468:c48e:1::1 --> 2606:4700:4700::1001
16 bytes from 2606:4700:4700::1001, icmp_seq=0 hlim=57 time=4.406 ms
16 bytes from 2606:4700:4700::1001, icmp_seq=1 hlim=57 time=2.773 ms
16 bytes from 2606:4700:4700::1001, icmp_seq=2 hlim=57 time=2.612 ms--- 2606:4700:4700::1001 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 2.612/3.264/4.406/0.810 ms -
@louis2 said in Why is the IPV6-WAN so much slower than the IPV4-connection!?:
I just do not know which addresses are used by default. Could be the dhcp-provided DNS-addressess ????
On my system, the addresses are the respective ISP gateway addresses.
