Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by steve1515, October 08, 2015, 06:36:18 PM
Quote from: steve1515 on October 21, 2015, 04:34:01 PMDoes this link work for you?http://[2620:106:e001:f00f::34]/images/public/amz/5/2/1/0/4003091900125_500W_500H.jpgUnfortunately, I'm not familiar with SonicWall, so I don't know how to set MTU/MSS. Maybe someone else can chime in?
Quote from: steve1515 on October 22, 2015, 12:09:13 PMYou could try and lower the MTU on your WAN interface to see if that forces the packets going thought the tunnel to be lowered as well. I'm interested to see if this would work for you.I told Pandora everything works with the MSS change, but haven't heard back if they are still looking at anything. I think they are declaring it fixed though.--Steve
Quote from: steve1515 on October 22, 2015, 05:26:21 PMYou should be able to use a smaller MTU than 1500 on your IPv4 WAN interface. Try something like 1280 to test it out. Because the tunnel is over IPv4, it should force your packets to be smaller for both IPv4 and IPv6. If that works, you can then start increasing it until it breaks again.I used the contact page. It was a web form to start and then they contacted me via email. It took a couple of days for them to get back to me. How many days have you waited? Maybe you could try again. Also check your spam folder, I had one support email end up in there. I almost missed it.--Steve
QuoteThanks for writing in. Our Network Operations team is aware of the issue with IPv6. It looks like you might also be aware of the MSS settings. Most of our listeners have had luck with MSS set to 1440 or 1420, which has been recommended by our Network team. I'm afraid other than this setting, our Network team does not have another fix at the moment. They are currently investigating a longer term solution. Sorry for any inconvenience. Please let me know if I can help with anything else. Thanks so much for listening!
QuoteI'm afraid we don't have an ETA as of now, but I can assure you our Network team is currently looking into this issue. They hope to have a solution, or at least more troubleshooting to offer, soon. Sorry again for any trouble. Feel free to drop us another line in if you have questions in the future.