Unfortunately my experience was pretty bad. I updated to this build from beta and it fubar'd
Ok I'll bite. Why are you using ip6?IPV6 seems to be broken in this release. Flashed and did FR. All settings redone from scratch. Was working fine on previous stable build.
Using AC87U.
Huh? Why shouldn't someone use IPV6?Ok I'll bite. Why are you using ip6?
Sent from my SM-G925W8 using Tapatalk
Just curious because i rarely see it used but maybe where you live it is. It was an honest curiosity and not meant negatively.Huh? Why shouldn't someone use IPV6?
IPV6 seems to be broken in this release. Flashed and did FR. All settings redone from scratch. Was working fine on previous stable build.
Using AC87U.
Mar 24 22:34:39 openvpn[3574]: RESOLVE: Cannot resolve host address: <vpn_host>: Name or service not known
Mar 24 22:34:54 openvpn[3574]: RESOLVE: Cannot resolve host address: <vpn_host>: Name or service not known
Mar 24 22:35:14 openvpn[3574]: RESOLVE: Cannot resolve host address: <vpn_host>: Name or service not known
Mar 24 22:35:34 openvpn[3574]: RESOLVE: Cannot resolve host address: <vpn_host>: Name or service not known
Mar 24 22:34:19 openvpn[3574]: read TCPv4_CLIENT: Connection timed out (code=110)
Mar 24 22:34:19 openvpn[3574]: Connection reset, restarting [0]
Mar 24 22:34:19 openvpn[3574]: SIGUSR1[soft,connection-reset] received, process restarting
Mar 24 22:34:19 openvpn[3574]: Restart pause, 5 second(s)
Mar 24 22:34:24 openvpn[3574]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mar 24 22:34:24 openvpn[3574]: Socket Buffers: R=[87380->87380] S=[16384->16384]
I had RT-AC68U and it did consolidating of space as well. Not sure about other partitions but it might.First time I've seen in Asus/Merlin firmware NVRAM partition being consolidated. Is this true to all other partitions? This is cool!
Code:Mar 24 16:46:46 kernel: nvram: consolidating space!
I noticed a strange thing: if I enable a guest network, then disable it, in wirelessly general settings I see the that guest network instead of my personal Wi-Fi (SSID)
IPV6 is not working reliably for me with 380.58 and Time Warner on my AC88U. The router seems to be getting the proper addresses from TWC and usually seems to be assigning them correctly to a few devices on my network. However, after 10 or 15 minutes, the router will show that no clients have IPV6 addresses. My MacBook Pro, for instance, can connect fine with IPV6 for a little while and pass all tests at any of the IPV6 testing websites, but it then loses the IPV6 address. My assumption is that the router is revoking the IPV6 address that it assigned. I tried setting ipv6_debug setting to 1 in the nvram (and rebooting), but that hasn't provided any helpful information. I also tried unsetting all of the nvram variables with ipv6 in the name and re-configuring IPV6 through the GUI. That didn't help either. I have DHCP logging turned off, but may turn that back on to see if that gives any clues.
When the IPV6 addresses go away for the clients, it appears that the IPV6 settings under the IPV6 Log tab, such as the WAN address, LAN address, and gateway, are still set properly. It just no longer shows any clients with IPV6 addresses.
Mar 24 21:34:19 openvpn-routing: Removing rule 1401 from routing policy
Mar 24 21:34:19 openvpn-routing: Removing rule 1501 from routing policy
Mar 24 21:34:19 openvpn-routing: Adding route for 192.168.1.1 to 0.0.0.0 through WAN
Mar 24 21:34:20 openvpn-routing: Adding route for 192.168.1.0/24 to 0.0.0.0 through VPN client 3
Mar 24 21:34:20 openvpn-routing: Tunnel re-established, restoring WAN access to clients
Mar 24 21:34:20 openvpn-routing: Completed routing policy configuration for client 3
Mar 24 21:34:20 openvpn[1779]: Initialization Sequence Completed
I had the same issue, albeit with 2 separate VPN providers.Eric, off the VPN clients 1, 3 and 5. I was doing some experiments on the router and tried setting the same configuration as client 1 on client 3.
System logs:
Code:Mar 24 21:34:19 openvpn-routing: Removing rule 1401 from routing policy Mar 24 21:34:19 openvpn-routing: Removing rule 1501 from routing policy Mar 24 21:34:19 openvpn-routing: Adding route for 192.168.1.1 to 0.0.0.0 through WAN Mar 24 21:34:20 openvpn-routing: Adding route for 192.168.1.0/24 to 0.0.0.0 through VPN client 3 Mar 24 21:34:20 openvpn-routing: Tunnel re-established, restoring WAN access to clients Mar 24 21:34:20 openvpn-routing: Completed routing policy configuration for client 3 Mar 24 21:34:20 openvpn[1779]: Initialization Sequence Completed
On The VPN page it said I am connected. Above system log said everything was ok.
However there were no Tun/Tap Read or writes. None of the systems connected to the router had internet.
The settings I copied to Client 3 were exactly the same as client 1. But no matter what I did, the connection would not come back.
In the mean time after completing my experiments on client 1, when I reset the settings on it as it was before, internet connection was restored to all the systems.
is there a problem with the other VPN clients?
First time I've seen in Asus/Merlin firmware NVRAM partition being consolidated. Is this true to all other partitions? This is cool!
Code:Mar 24 16:46:46 kernel: nvram: consolidating space!
I was very excited about this release, but it appears something ASUS (Wi-Fi driver?) have introduced after 378.55 makes my 2.4 Wi-Fi flaky, as soon as I go back to 378.55, 2.4 is again stable for all devices, its a shame as direct link to router is perfect with the new builds, just the Wi-Fi isn't.
We use essential cookies to make this site work, and optional cookies to enhance your experience.