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

    [ 386.14_1 Build(s) ] available build(s)

    Builds are still there - try https://www.asuswrt-merlin.net/test-builds
  2. dbell

    Release Asuswrt-Merlin 3004.388.8_2 is now available

    They seem fine. I access my router over https:// but then had to use http:// for the nodes when I had my issue, but as I said the regular https:// links worked again after the release update. What happens if you just enter the node URL directly in browser rather than clicking Upload button ? You...
  3. dbell

    Release Asuswrt-Merlin 3004.388.8_2 is now available

    What is the URL of your router and then what is the url of the popup window when you try to upload to a node ? During the beta (IIRC-might have been alpha) I did see an issue where the node URL was not being constructed properly but it was ok since the actual release. I run a couple of AC5300...
  4. dbell

    Beta Asuswrt-Merlin 3004.388.7 beta is now available

    Updating my AX86Us now and will see if I get any repeats of those problems. Odd that they didn't show up for a while then two times in quick succession.
  5. dbell

    Beta Asuswrt-Merlin 3004.388.7 beta is now available

    My AX86U had been running fine since updating to beta1 the day it was posted, but now twice in last 12 hrs or so my WAN connection has dropped (shown as disconnected) and the AX86U has reported these messages and I've had to reboot to recover: Apr 26 12:46:52 dropbear[1946]: Error forking...
  6. dbell

    [ 3004.388.7 alpha 1 Build(s) ] Testing available build(s)

    Having updated the AC5300 nodes with the 3004.386.13_beta1 drop today, this now seems corrected in the router UI (3004.388.7_alpha1-g4c689dffeb), so maybe the issue was the prior AC5300 firmware sending incomplete version info to the router in the first place. Perhaps a string length limit given...
  7. dbell

    [ 3004.388.7 alpha 1 Build(s) ] Testing available build(s)

  8. dbell

    [ 3004.388.7 alpha 1 Build(s) ] Testing available build(s)

    It's not a styling problem; the actual value is missing the last char in the page source: Seems like it is truncated in the response to this request:
  9. dbell

    [ 3004.388.7 alpha 1 Build(s) ] Testing available build(s)

    Seems to be trimming the last char of the build number - the 386.13_alpha1 entries should end 4451 and a8e4 respectively - the 388.7 entries are correct:
  10. dbell

    Release Asuswrt-Merlin 386.12_6 is now available for AC models

    QNAP NAS supports link aggregation which you won't get on AC5300. I have two QNAP ports aggregated into two AX86U ports for up to 2gbps throughput. Of course if 1 gbps is enough then it doesn't really matter.
  11. dbell

    Release Asuswrt-Merlin 386.12_6 is now available for AC models

    Agreed. I am running with an AX86U router and AC5300 nodes meshed over 5Ghz all running latest Merlin FW. The AC5300s will use 5G radio 2 for the backhaul connection unless you can hard-wire them via Ethernet which is preferable. If you cannot use Ethernet and have to have a wireless connection...
  12. dbell

    Release Asuswrt-Merlin 3004.388.6 is now available

    The item in line 47 is now probably present by default in /etc/dnsmasq.conf, but was previously added by your customization in /jffs/configs/dnsmasq.conf.add. Remove that entry from your /jffs/configs/dnsmasq.conf.add so it only appears in one of the files and retry. There was discussion in the...
  13. dbell

    Release Asuswrt-Merlin 3004.388.4 is now available

    Yup thanks for chiming in. @Damit1 had issues with 36/160 combo in the past but is using AX88's not AX86's like me, so not entirely a good comparison. UPDATE: Turning 160 off for now but I'm concerned there may be a latent issue there on the 86u.
  14. dbell

    Release Asuswrt-Merlin 3004.388.4 is now available

    This is the fixed channel config: and this is the 160mhz capable client connected to it at only 80mhz and dfs idle: Here it is when channel is set to auto, same client connects at 160mhz, dfs remains on ISM and time elapsed counter is running: ISM been active now for 7+ mins: After...
  15. dbell

    Release Asuswrt-Merlin 3004.388.4 is now available

    Is it though; shouldn't the dfs state remain as in-service monitoring unless it is tripped by radar ? Looks like @octopus has had that for 10+ hrs. That has been my prior experience and this time around my laptop wouldn't connect at anything but 80mhz using channel 36 but did connect at 160mhz...
  16. dbell

    Release Asuswrt-Merlin 3004.388.4 is now available

    Couple of logging anomalies but not sure what / if they are affecting anything: Aug 22 10:41:42 dnsmasq-script[1757]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory but that file does exist in /jffs. And then: Aug 22 10:41:38 wlceventd: main(1239)...
  17. dbell

    Release Asuswrt-Merlin 3004.388.4 is now available

    Mine does.
  18. dbell

    Beta Asuswrt-Merlin 3004.388.4 beta is now available

    Had this occur a couple of times today on my AX86U router, within about 7 mins of each other, and dumped back to login screen. This latest time I was refreshing the dhcp server page because it was not displayed properly. Aug 18 12:44:10 dnsmasq-dhcp[1757]: DHCPREQUEST(br0) <ip> <mac> Aug 18...
  19. dbell

    Beta Asuswrt-Merlin 3004.388.4 beta is now available

    No - I am on fixed 36 / 160 and have been for several releases now.
  20. dbell

    Beta Asuswrt-Merlin 3004.388.4 beta is now available

    This is anecdotal at best, but I too think the 5g channel began broadcasting with a shorter delay after a restart in beta 2.
Top