Thanks for confirming this. I'm glad that I'm not the only one and/or I'm not completely inept. I'll sit down later today and play with the various MTU settings (WAN, HEv6 tunnel, and the setting on the "advanced tab" of Tunnel Broker's site) and see what, if anything, I can get to work consistently.
I don't know what browser you use but I found a simple Chrome extension that has been helpful in determining what protocol (v4/v6) is being using used to connect to any specific site. It's called IPvFoo and is available in the webstore (http://goo.gl/kxKVhx). It adds a little 4 or 6 icon on the right of the URI bar that when clicked on shows what portions of the page were served using what protocol. Again, thanks for confirming this. At certain points I was beginning to doubt myself as things would work on second and break for seemingly no reason the next. --adam On Thu, Aug 15, 2013 at 9:51 AM, Adam Thompson <[email protected]>wrote: > I'm having the same problem as a recent reporter (whose email I already > can't find). > I've got a tunnel set up to HE.NET, and experience difficulty browsing to > (e.g.) redmine.pfsense.org. > Testing shows that the largest ICMP payload I can exchange is 1232 bytes > ("ping -l 1232 redmine.pfsense.org" works, 1233 doesn't). > If I stop and reload the page in my browser, everything works fine - I > don't know yet if that's because the browser falls back to IPv4 or because > the MTU problem suddenly fixes itself. > > -Adam Thompson > [email protected] > Tel: (204) 291-7950 > Fax: (204) 489-6515 > > > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
