Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. B

    IPV6 Instability in 380.57

    Left CTF disabled for about 40 hours and pinged Google's IPV6 address every two minutes during this time. haven't had any complete loss of IPv6 internet access apart from a few occasional dropped packets.
  2. B

    IPv6 tunnel instability with 378.51 on RT-N66U

    Same thing here on AC56 with 380.57. I didn't notice this on 378.56_2 though. Luckily my WAN speed doesn't warrant the need for CTF so I'll have it disabled for now and will have to see if IPV6 connectivity remains stable.
  3. B

    IPV6 Instability in 380.57

    Well shame on me. A simple Google search turned this up: http://www.snbforums.com/threads/ipv6-tunnel-instability-with-378-51-on-rt-n66u.23553/ CTF might be the culprit. I have it disabled for now, will see if it actually fixes the issue.
  4. B

    IPV6 Instability in 380.57

    I'm not sure, but rebooting fixes the issue and it wasn't present in the previous version of the firmware. Also clients are seeing an IPV6 interface with not internet connectivity, rather than a working tunnel w/ discarded packets or whatever GFW does to mess things up, so I'm leaning towards...
  5. B

    IPV6 Instability in 380.57

    EDIT: apparently CTF is incompatible with IPV6 tunnels. Disabling CTF fixed the problem. I've been happily using a HE IPV6 tunnel on my AC56 running 378.56_2 to circumvent GFW for a while. After updating to 380.57 I've noticed that once in a couple hours, my Windows 10 client would report that...
Top