384.14 Beta 1 IPv6 reboot required after OpenVPN client use

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Dave Moseley

Occasional Visitor
RT-AC68U: After 14_Beta_1 upgrade and connecting to remote VPN (384-81049), Windows 10 reboot required to regain IPv6 stack. Reboot also required for local Raspbian (stretch & buster). Remote connections made on Windows 10, using both OpenVPN 2.4.7 and 2.4.8

Behavior seems unrelated to OpenVPN use. IPv6 stack is lost, regardless, soon after reboot. Restoring AC68U to 384.13 seems to have resolved the problem. I'll update otherwise.
 
Last edited:

octopus

Very Senior Member
RT-AC68U: After 14_Beta_1 upgrade and connecting to remote VPN (384-81049), Windows 10 reboot required to regain IPv6 stack. Reboot also required for local Raspbian (stretch & buster). Remote connections made on Windows 10, using both OpenVPN 2.4.7 and 2.4.8

Behavior seems unrelated to OpenVPN use. IPv6 stack is lost, regardless, soon after reboot. Restoring AC68U to 384.13 seems to have resolved the problem. I'll update otherwise.
Why don't you post in BETA1 thread?
https://www.snbforums.com/threads/b...eta-is-now-available.60037/page-3#post-525032
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top