Sushiglobster
Regular Contributor
I decided to create a new thread here. Originally I had been trying to figure out IPv6 issues in the Merlin area within the BETA release thread.
Probably more proper to ask here.
Anyways, I'm trying to figure out why my IPv6 speed tests are half of my IPv4 speeds.
Picture of a test I ran:
I am using ATT UVERSE services and I have my ATT NVG589 in passthrough mode and my RT-N66U is handling everything including Tunnel 6rd with IPv6.
I was told to use this command:
ip6tables -I FORWARD -o vlan1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1420
I added this command via SSH and PuTTY (I have no idea if I even did it right. I was able to login and access the command prompt. I typed in there and pressed enter and then exited. I have no idea if it did anything) Doing a speed test again for IPv6 showed no difference.
I could use some help. Not sure what to do here.
EDIT: Forgot to mention this, I'm cascading my RT-N66U. It is behind my ATT NVG589. If I plug directly into my NVG589, IPv6 speed tests are VERY fast and equal speed of IPv4 testing. So, whatever the issue it is, it's at my RT-N66U.
Probably more proper to ask here.
Anyways, I'm trying to figure out why my IPv6 speed tests are half of my IPv4 speeds.
Picture of a test I ran:

I am using ATT UVERSE services and I have my ATT NVG589 in passthrough mode and my RT-N66U is handling everything including Tunnel 6rd with IPv6.
I was told to use this command:
ip6tables -I FORWARD -o vlan1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1420
I added this command via SSH and PuTTY (I have no idea if I even did it right. I was able to login and access the command prompt. I typed in there and pressed enter and then exited. I have no idea if it did anything) Doing a speed test again for IPv6 showed no difference.
I could use some help. Not sure what to do here.
EDIT: Forgot to mention this, I'm cascading my RT-N66U. It is behind my ATT NVG589. If I plug directly into my NVG589, IPv6 speed tests are VERY fast and equal speed of IPv4 testing. So, whatever the issue it is, it's at my RT-N66U.
Last edited: