Quoc Huynh
Regular Contributor
All three features should work fine with each other.
Thank you very much, Adamm! It is really great to know that they can work with each other.
P/S: Take care my friend, and best wishes to you.
All three features should work fine with each other.
sh /jffs/scripts/firewall stats search reports
Hey @Adamm is there a way to look through the outgoing blocked traffic? I had a look through your instructions in post #1 and can't seem to find anything relevant. Ideally I would like to watch the blocks as they happen. This sounds like a watch command in post #1 but I'm not sure. I want to watch a specific ip on my network at home and its outgoing blocks. Thanks again for your script and support it's fantastic!
The watch command would be the one you are looking for, anything in yellow are inbound connections, red are outbound. I'll look into customising this more in future updates.
This may be a dumb question but the debug and watch logs are sent to system logs or are they saved somewhere else?Yes, the "watch" feature is just a filtered version of the syslog output.
This may be a dumb question but the debug and watch logs are sent to system logs or are they saved somewhere else?
@Adamm, would it be possible to add a filter to the watch command? I mean a grep style search string. Many times I need to monitor a specific port, protocol or IP, and that would work perfectly by filtering the output to only entries of interest.
sh /jffs/scripts/firewall debug watch ip xxx.xxx.xxx.xxx
sh /jffs/scripts/firewall debug watch port xxxxx
Just tried this out @Adamm this is freaking awesome! Just what I need right now!!I've made a start on this in v5.7.9, you can now filter logs from a specific IP or port. The functionality is quite basic for now, I will look to improve on it in future when I get some free time. Currently catching up on 4 days of no internet
Code:sh /jffs/scripts/firewall debug watch ip xxx.xxx.xxx.xxx sh /jffs/scripts/firewall debug watch port xxxxx
I've made a start on this in v5.7.9, you can now filter logs from a specific IP or port. The functionality is quite basic for now, I will look to improve on it in future when I get some free time. Currently catching up on 4 days of no internet
Code:sh /jffs/scripts/firewall debug watch ip xxx.xxx.xxx.xxx sh /jffs/scripts/firewall debug watch port xxxxx
Is it normal for skynet.log not to have been modified for over 24 hours and only have one autoban?
Can't say I've ever seen the error before, seems more like a firmware thing. Was this just a one time occurrence or can it be reproduced? @RMerlin
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!