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

    Beta Asuswrt-Merlin 386.1 Beta is now available

    Even after you read RMerlin's description of the bug you ran into, due to differences between the firmwares and how they handle missing options? Perhaps you might want to read it again.
  2. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    you forgot the key phrase: who move over without doing a reset
  3. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    I'm not seeing any problems with IPv6 in beta3. It's more than 70% of the traffic going through the node. Can you share some specifics of what you are seeing? $ ping6 geode.netconsonance.com PING6(56=40+8+8 bytes) 2601:646:8000:346:9c74:a4fc:470:ab80 --> 2001:1868:a108:1::8 16 bytes from...
  4. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    @RMerlin probably need to rename this thread "386.1 Beta(s)" ;) or make a new thread for beta4 at least. Frankly, this one is quite long...
  5. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    WPA2 is trivially easy to crack. ARP is easy to spoof. Absolutely nothing about this is difficult for someone in any nearby house (and I have lots of bored, house-bound kids within wifi range) But that's not the real threat. We've seen malware installed from browser extensions play the spoofing...
  6. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    ...for people who had upgraded without a reset. Sorry, my reply was subject to a thing that I see sometimes here where it seems to filter the view, and thus your later posts weren't visible to me. After I'd posted suddenly 10 more pages of comments appeared :( Still-- the type of questions I...
  7. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    I was seeing the same problem. I found that the LE certificate was properly generated in /jffs/.le/ so I manually removed /etc/cert.pem and /etc/key.pem and stuff, then redid the authorization from the panel and it worked. Seems like there's something in the code that won't replace a valid...
  8. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    Certainly MitM is easiier :p
  9. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    You must isolate the problem. Right now it's somewhere between the end user and the far side :D * Could clients communicate with the router? Ping or TCP test. * Could ethernet clients communicate with the router? * Could the router communicate with the Internet? That would at least identify...
  10. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    That might qualify for the least amount of debugging (or at least information provided) I've ever seen from someone who wants an explanation of something they didn't even describe. I mean seriously, start at the top: 1. Did the router boot up? 2. Did it get communication from your upstream...
  11. jorhett

    Beta Asuswrt-Merlin 386.1 Beta is now available

    only necessary if you overlap with DFS channels... that timeout/check is built into the spec. And if someone runs anything that looks like radar through there, your wifi is gonna go off for 10 minutes too. So look back at this post when you come back to tell us it keeps disappearing :p It's...
  12. jorhett

    Asus RT-AC-88U Merlin 361.1 beta 2 big problem

    smbd is the daemon transfering the file for you. That behavior seems entirely normal. "Use all free memory to transfer files" is how a file server operates, as several people have told you. But using a router as a file server makes it hard to distinguish if there is perhaps a memory leak...
  13. jorhett

    386.1_beta2 on AX86U doesn't allow IPv4 filters

    IPv6 filters work fine. When trying to enter an IPv4 destination address you get the following error every time, no matter what IPv4 address, whether you use a mask, or even if IPv6 firewall is disabled. So it seems likely to be a UI input validation error
  14. jorhett

    Asus RT-AC-88U Merlin 361.1 beta 2 big problem

    ...why I don't provide file service on my core router :p
  15. jorhett

    Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

    Understood. And I did go back and do a reset. I'm just a stickler for making things clear in the docs ;) and/or suggestions. I used your advice earlier in the thread for updating my aimesh node: installed the stock 386 image using the aimesh update interface (on the router I was replacing)...
  16. jorhett

    Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

    I know what a factory default reset is. I've been using asuswrt for coming up on a decade, and Tomato before that. I also do backbone engineering / BGP peering for a living so I'm not a newbie to this ;) What I was trying to say is that the upgrade instructions clearly state that the changelog...
  17. jorhett

    Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

    You mean reset the settings / flash? No. I was surprised to find that it wasn't mentioned as required in the changelog. That being said, it was a brand new unit thus stock except for a LAN IP so there wasn't much to reset.
  18. jorhett

    Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

    Got a new AX86U and the upgrade to beta2 was both fast (~2min db update) and seamless. How many people using this in production... er, production-ish :p home use yet?
  19. jorhett

    Release Asuswrt-Merlin 384.19 is now available

    Also, after upgrade to 384.19 it is claiming there is new firmware available? Doesn't appear to be true...
  20. jorhett

    Release Asuswrt-Merlin 384.19 is now available

    Weird error viewed when upgrading 384.18 to 384.19 ... it says it failed, but then proceeds to go through the process and reboot the unit. Sure enough, it rebooted to 384.18 Redoing the exact same upgrade with the exact same file worked, no problems.
View older results
Top