What's new
  • 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!

Beta Asuswrt-Merlin 3006.102.4 Beta is now available

Status
Not open for further replies.
Sul mio ASUS GT-AX6000 funziona tutto senza nessun problema, tranne che non si riesce più ad accedere al modem connesso alla WAN.
Ho reinstallato la versione 3004 stabile e ho risolto il problema.
 
Sul mio ASUS GT-AX6000 funziona tutto senza nessun problema, tranne che non si riesce più ad accedere al modem connesso alla WAN.
Ho reinstallato la versione 3004 stabile e ho risolto il problema.
Please just in English.
 
Don’t use the MLO tab in the GUI go to Network and create the MLO network manually then you will have the option to unselect 2.4Ghz.
I might be missing something here but I already have 5Ghz/6Ghz bands only enabled for my primary WiFi network, but I believe this is acting like the old “smart connect” where both bands are combined into the one SSID and puts the onus on the client to choose what band to connect to but MLO is not actually enabled.

On the network page for my primary network there is an “MLO fronthaul for clients” toggle which when trying to enable takes me to the main MLO tab which wants the 2.4Ghz radio enabled.
 
To copy dhcp_staticlist from jffs/nvram is another option
Yes copying the following are another option.
Code:
/jffs/nvram/custom_clientlist
/jffs/nvram/custom_usericon
/jffs/nvram/dhcp_staticlist
The question asked was; "what's the benefit of YazDHCP". Another advantage to YazDHCP is it typically increases the number of manual reservations as well from what the firmware normally provides.
 
GUI access to backups is more attractive to the typical user than working over ssh.
 
Last edited:
It would be nice to read a little more about beta2 software...
 
It would be nice to read a little more about beta2 software...
I have an issue that I noticed recently, but I don’t know whether it came with beta 2 or was already happening when/after I installed the first alpha of 3006 (for my GT-AX6000) and made a change to my network setup.

Because we now have better “guest” networks I decided to make my main network WPA3-only and set up an extra network for just my Apple TV HD, which does not support WPA3. However, since doing that, wireless transfers from my MacBook Air M1 to that Apple TV are extremely slow (it takes close to an hour to transfer 2 GB).

I have not noticed any other network slowness. What could be wrong? What are good steps to investigate this?
 
I have an issue that I noticed recently, but I don’t know whether it came with beta 2 or was already happening when/after I installed the first alpha of 3006 (for my GT-AX6000) and made a change to my network setup.

Because we now have better “guest” networks I decided to make my main network WPA3-only and set up an extra network for just my Apple TV HD, which does not support WPA3. However, since doing that, wireless transfers from my MacBook Air M1 to that Apple TV are extremely slow (it takes close to an hour to transfer 2 GB).

I have not noticed any other network slowness. What could be wrong? What are good steps to investigate this?
IoT devices on different networks, especially when segregated via subnets, are often accessed via Internet connection instead of LAN connection. Have you tried connecting temporarily MacBook Air m1 to same network as Apple TV HD to try the 2 GB transfer?
 
@RMerlin and Brains Trust

Recently swapped out my RT-AX86U for an RT-BE86U, am in process of setting it up so loaded up the 3006.102.4_beta2 (after briefly checking it powered up on stock fw), seeing a bunch of these in the log:

Code:
May  1 06:48:37 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[718] match fails entry.dstid[846]
May  1 06:48:46 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[723] match fails entry.dstid[851]
May  1 06:48:56 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[731] match fails entry.dstid[859]
May  1 06:49:06 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[740] match fails entry.dstid[868]
May  1 06:49:09 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[742] match fails entry.dstid[870]
May  1 06:49:11 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[616] match fails entry.dstid[744]
May  1 06:49:13 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[746] match fails entry.dstid[874]
May  1 06:49:25 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[753] match fails entry.dstid[881]
May  1 06:49:29 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[757] match fails entry.dstid[885]
May  1 06:49:46 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[772] match fails entry.dstid[900]
May  1 06:49:49 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[774] match fails entry.dstid[902]
May  1 06:49:52 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[778] match fails entry.dstid[906]
May  1 06:49:53 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[780] match fails entry.dstid[908]
May  1 06:49:56 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[784] match fails entry.dstid[912]
May  1 06:49:59 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[788] match fails entry.dstid[916]
May  1 06:50:02 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[792] match fails entry.dstid[920]
May  1 06:50:05 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[796] match fails entry.dstid[924]
May  1 06:50:08 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[798] match fails entry.dstid[926]
May  1 06:50:08 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[799] match fails entry.dstid[927]
May  1 06:50:11 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[801] match fails entry.dstid[929]

Look like they may be NTP/Time/DST related? Anyone else seeing these?
My NTP/Timezone/DST settings are correct for Sydney Australia and identical to my old AX86U settings (running 3004.388.9_2) so a bit puzzled as to what could be causing it, but there is LOTS of them popping and making my logs less than pristine :D

Anyone found a fix to make them go away (apart from filtering them out with Scribe) or is this a bug?

StephenH
 
Last edited:
Recently swapped out my RT-AX86U for an RT-BE86U, loaded up the 3006.2.4 beta after briefly chexking it worked on srock fw, seeing a bunch of these in the log:

Code:
May  1 06:48:37 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[718] match fails entry.dstid[846]
May  1 06:48:46 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[723] match fails entry.dstid[851]
May  1 06:48:56 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[731] match fails entry.dstid[859]
May  1 06:49:06 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[740] match fails entry.dstid[868]
May  1 06:49:09 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[742] match fails entry.dstid[870]
May  1 06:49:11 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[616] match fails entry.dstid[744]
May  1 06:49:13 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[746] match fails entry.dstid[874]
May  1 06:49:25 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[753] match fails entry.dstid[881]
May  1 06:49:29 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[757] match fails entry.dstid[885]
May  1 06:49:46 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[772] match fails entry.dstid[900]
May  1 06:49:49 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[774] match fails entry.dstid[902]
May  1 06:49:52 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[778] match fails entry.dstid[906]
May  1 06:49:53 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[780] match fails entry.dstid[908]
May  1 06:49:56 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[784] match fails entry.dstid[912]
May  1 06:49:59 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[788] match fails entry.dstid[916]
May  1 06:50:02 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[792] match fails entry.dstid[920]
May  1 06:50:05 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[796] match fails entry.dstid[924]
May  1 06:50:08 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[798] match fails entry.dstid[926]
May  1 06:50:08 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[799] match fails entry.dstid[927]
May  1 06:50:11 AsusRouterBE kernel: blog_get_dstentry_by_id:dstid[801] match fails entry.dstid[929]
Known Broadcom issue and nothing RMerlin can fix
 
Known Broadcom issue and nothing RMerlin can fix
Thanks @Ripshod - guess I'll be adding yet another filter to Scribe/UIScribe when I get that far in the BE86 build later today!
 
I should have mentioned that I am a Windows user and we dislike SSH.
I am a Windows user. I have no problem at all using SSH. I use the Windows version of SSH. I just create a bunch of CMD files to SSH into any server I want.
 
I am a Windows user. I have no problem at all using SSH. I use the Windows version of SSH. I just create a bunch of CMD files to SSH into any server I want.
Ha. I am so old I thought you were talking about OS/2. I still call mine .bat files
 
Status
Not open for further replies.

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Back
Top