Menu
What's new
By:
Filters Better Search

Recent content by JoeHz

  • 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. JoeHz

    VPN Configuration Truncated

    Using an RT-AC86U running 384.15 of Asus-Merlin I've been provided a .ovpn file to connect to a VPN and it works fine on Android clients. When I try to use it on the router though it fails, and I'm noticing that the "-----BEGIN CERTIFICATE-----" section is getting truncated about half way...
  2. JoeHz

    [Release] Asuswrt-Merlin 384.13 is now available

    Okay, it was suspicious but not damning. Back on latest firmware and the machine no longer has the Killer Control Panel, et al, and now can connect. It was fine for a while before too, so I'll chime in if it loses its little silicon mind again.
  3. JoeHz

    [Release] Asuswrt-Merlin 384.13 is now available

    I'll be giving that a shot in a moment, but what I found troubling was that I could generate a hotspot from my 4G phone and the machine could connect to it but not the 86U with the recent firmware. That , and downgrading it would resolve the issue. I'm happy to do what it takes to rule this out...
  4. JoeHz

    [Release] Asuswrt-Merlin 384.13 is now available

    Well, yes, but its curious that the firmware change seems to have quite the correlation to issue with Killer. I'll try the driver only route.
  5. JoeHz

    [Release] Asuswrt-Merlin 384.13 is now available

    I just had to back out of 384.13 to 384.12. Running an AC-RT86U. Wife's relatively new Alienware M17 with a just as recent Killer Networking card could see the SSID but all connections to it were met with Win10 responding, "Can't connect to this network". Could connect to others. Tried changing...
  6. JoeHz

    [Release] Asuswrt-Merlin 384.7 is now available

    In my case, I did, but I expected that. Tunnelbroker.net, if you're not connecting to their ddns update page over https, you had to use your user id (which is a not-human-readable string), rather than your username. And the old firmware *never* used https. Now that it's using https, you should...
  7. JoeHz

    [Release] Asuswrt-Merlin 384.7 is now available

    That was exactly it. ty. It had DST ending 2nd sunday of October (yesterday). Not first Sunday of November (as in the US)
  8. JoeHz

    [Release] Asuswrt-Merlin 384.7 is now available

    Looks like I can create a custom script if necessary. That might do it. Doubt it can get the LetsEncrypt cert that way, but it's better than nothing. Still the UI really shouldn't make such an assumption. I was happy to initially see the change to using https on this. It forces everyone using...
  9. JoeHz

    [Release] Asuswrt-Merlin 384.7 is now available

    1) I've noticed that my NTP setting is off. I've set it correctly (US East Coast, GMT -5), but all the logs claim the current time is an hour ago. Might have been that way before the upgrade. Dunno. 2) I use tunnelbroker.net for an IPv6 tunnel -- and their DDNS service to keep the tunnel...
See more
Top