How are you handling clients with static IPs that won't possess any DHCP lease?
That's why I suggested tying into the networkmap data instead of relying on dnsmasq's incomplete list. It's the only client list that will be complete (well, it will be once Asus sort out its random behaviour), since it relies on ARP rather than on DHCP leases.
Static devices are pulled from the NVRAM varaible.
Connected devices are pulled from the arp table.
Any remaining devices are pulled from the DHCP tables.
I am not touching networkmap as it never returns the correct or stable ammount of devices!
But I am pulling data from the same source that network map is using.
Take a look. The filter works great. (I have it load devices on initial load but I can expand it to auto update in the background)
@FreshJR One quick question, how can you set more than 4 custom rules? See image below.
View attachment 16357
I'm probably not doing something right, sorry for the dumb question.
Not dumb. Its limited to 4 entries due to limited nvram space. If I get another variable I can add 4 more entries. Currently I hijacked two variables from the feedback page and dont want to take any more.
i used new command for installation and new Classification page is not replaced ...
i see still old one
EDIT:
issue solved, mounted manually, now working fine.
wow, speed is incredible ...
It mounts when firewall-start is executed. Which happens when the QOS is restarted.
A failed mount after installation means you haven’t yet restarted/toggled QoS.
I made it like that on purpose. Maybe I will add your question to the faq.
Thanks for the compliment.
It's bugged - the script is actually looking for these:
Arg. I moved the prompt options around too many times when visually checking how pleasing to the output was to the eye. Seems I forgot fully update the changes in the switch statements.
Can’t believe I messed up something so simple!!
Perfect time to test the update command in action when a revision is released! (Command was already tested prior to release)
The menu was haphazadly thrown in last second for future amtm complience.
I personally prefer diving directly into
/jffs/scripts/FreshJR_QOS -rules