kstamand
Regular Contributor
ModSyslogUI - NEW PRESET functionality added and looking for testers willing to kick the tires, provide feedback, and provide debug information if needed
Change highlights:
This version expands on what is provided by the current v1.0.2 production release.v1.1.0 (22-Feb-2026)
- Added: UI - Filter presets (Save, Edit, Delete)
- Added: UI - inline filter validation
- Added: UI - dynamic help information
- Updated: UI - expanded filter logic capabilities beyond simple AND, OR, AND NOT to now include tag: term OPERATOR term
- Fixed: Script - invalid menu option handling (return to menu, and not exit), to show the latest version info in menu after update
- Added: Script - added debuging to file capabilities
- Included: Script - a default set of PRESETS for reference purposes. Feel free to change or delete to meet your needs.
What I'm asking for is ONE volunteer to test each of the following (one person volunteering for more than one is fine)
To keep my life manageable, I will limit the number of testers and probably only select the first set of volunteers- someone who will test3004.388.* and someone who will test 3006.102.*
- asking for 1 tester for as many router models as possible
- someone to try and find issues with the "modsyslogui" script and all it's functionality
- someone to exercise ALL the System Log page UI filtering capabilities - the original Include | Exclude | Logical AND Presets
Additional DEBUGGING considerations before volunteering to test
In the event script or UI filtering options do not work, I ask that you collect and provide the following information in this ModSyslogUI thread:- screenshot of error either on the UI or script from SSH session
- if the modsyslogui shell script is generating an error, enable the DEBUG option to capture the error, then attached the /jffs/addons/modsylogui/MODSYSLOGUI_DEBUB.TXT to your post in the ModSyslogUI thread of snbforums
- if the UI filtering is not working as expected, open the browser's DEV TOOLS (you may need to enable that first) and capture a screenshot(s) of any CONSOLE errors, then post them in this ModSyslogUI thread
- in certain instances, I may ask for a copy of the /jffs/addons/modsyslogui/Main_LogStatus_Content.asp file (all the filtering magic happens here). In that event, run the following command and attach the log.txt to ModSyslogUI thread explaining the issue
Code:
cat /jffs/addons/modsyslogui/Main_LogStatus_Content.asp > log.txtBeta install command
Code:
/usr/sbin/curl --retry 3 "https://raw.githubusercontent.com/kstamand/modsyslogui/beta/modsyslogui" -o "/tmp/modsyslogui" && chmod +x /tmp/modsyslogui && sh /tmp/modsyslogui installv1.1.0 Screenshots
Last edited:
