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. E

    DDNS "Forced refresh interval (in days)" setting not working?

    But isn't a "forced refresh interval" supposed to mean that it will attempt to refresh, even if the IP hasn't changed? DNS-o-matic will record and keep track of each update, even if the IP hasn't changed... so the router hasn't attempted to register the IP again.
  2. E

    DDNS "Forced refresh interval (in days)" setting not working?

    Well I did wait another day - and still no update. The router last updated the record at dnsomatic on Feb 16th at 5:22am and hasn't since then, now 16 days later, while the config I've set says it should happen every 15 days.. Known bug/issue?
  3. E

    DDNS "Forced refresh interval (in days)" setting not working?

    I'm using 380.65 on an AC68U, and noticed that even though I've got DDNS set up, and it worked/ran on boot to update dns-o-matic, the router's now been running for longer than the configured interval (15 days) and there's been no update, nor any error in the logs to indicate that anything went...
  4. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    (...snip...) I used this guide: https://helpdesk.privateinternetaccess.com/hc/en-us/articles/227852327-Setting-up-an-Asus-Router-running-Merlin-Firmware , figuring it was newer and on my VPN provider's site. But I guess it couldn't hurt to set reneg-sec to 0, and it may actually help, based on...
  5. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    I have "-1" and "30" set in those fields... but setting that to "0" and "-1"... wouldn't that effectively mask problems? And why would I have no problems at all for a week and just start having periodic every 2 hours issues then, requiring a reboot?
  6. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    I wonder whether others have noticed/seen this behavior, and I'm not entirely sure it will reproduce, but... I had a VPN client running for a while, not having any issues for a week, and then I noticed every 2 hours (+ a minute or two) I'd get this logged: Dec 27 17:16:49 openvpn[11452]: TLS...
  7. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    OK, I narrowed the problem down... somehow the behavior on your fork must be a bit different still, as I had an openvpn-event script that was _also_ mangling the routing table (in addition to the "route " command in the custom config)... and of course once it had run once, it's damage was done...
  8. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    AC68U, 800MHz. And on closer inspection of my logs from running openvpn on your fork, I _didn't_ see the same errors, but other route-related errors in the logs. Sorry for the confusion there. I was seeing: Dec 10 19:13:55 openvpn[4157]: ERROR: Linux route delete command failed: external...
  9. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Here's the /etc/openvpn/client1/config.ovpn on the current Merlin firmware, showing the problem: # Automatically generated configuration daemon client dev tun11 proto udp remote uk-london.privateinternetaccess.com 1198 resolv-retry 30 nobind persist-key persist-tun comp-lzo no cipher...
  10. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    That test will likely "work" as it probably won't put any routes in place, since "plextv" isn't a valid host/domain to look up. But that'll result in a non-working config w/o the routes added.
  11. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Must be some other setting (not in custom config) then... I'll have to fire up the router with that setup on it to see what else was set there. I do have "policy rules" as the setting for "redirect internet traffic" in the gui, as I only put specific IPs through the tunnel.
  12. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Sure: route plex.tv 255.255.255.255 net_gateway
  13. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Even after removing those 3 options and leaving just the "route" line in the custom config, the problem still persists. No problem on reboot, but if you "apply" config and openvpn is reloaded the stale routes are left behind and this error state occurs.
  14. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    No, I don't have that set in my custom config. All I have in there, in addition to the "route" line is: persist-key persist-tun disable-occ Maybe one of those has the same side-effect? Those settings were mentioned in a howto for setting up openvpn with Merlin for PIA. The problem is...
  15. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Just rebooted, and the problem doesn't happen on a fresh boot, but simply "apply" the config (no need to change it) and it'll report errors and leave the vpn client status as "Error connecting - IP/Routing conflict"
  16. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    That's all very interesting, and I see you've got a complicated script that'll fix things/clean up routes when switching client configs (and I knew I could manually switch the status to "2" for the vpn client from the command line to show that it's up...) but the fact that adding a single...
  17. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Except that the additional info is obscuring the fact that the status is in fact "up"... it's not _just_ additional.
  18. E

    [Release] Asuswrt-Merlin 380.64_2 is now available

    Probably not an issue with the specific build, but I've just switched from John's fork of Merlin to this build, and have noticed that if I have something like this in the custom configuration pane of a vpn client: route plex.tv 255.255.255.255 net_gateway The routes do get added and things...
Top