Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for all the help these past few months. I am using ipchains to filter packets. This works nicely. I would now like to have rules to filter pesky banners and popups without using a proxy like junkbusters etc.
I am currently writing rules that DENY the source IP addresses but what is happening is the servers continue to push the packets. This makes for continued logging and lengthy /var/log/messages. I was able to do this quite affectively in my windows box with ZoneAlarmPro. Is there anyway to BLOCK specific IP's and eliminate the excessive logging of DENY'd packets without removing the -l?
Could someone give me a rule for this example:
-A input -s 192.168.206.10/192.168.206.29 -d 0.0.0.0/0.0.0.0 -j DENY -l
No, u cant.
It would be a failure for Ipchains to parse a rule, find a match, and then *not* log it when -l is specified...
Btw whats ure argument against junkbuster?
Its way more efficient & flexible, ipchains is a *crude* solution.
Using 'junkbuster', pages are slow to load. Half to quarter speed or from average 4KB's/sec down to 1-2KB's/sec. I assume this to be a normal sacrifice since 'junkbuster' examines every image on a web page. Unfortunately, I only have a 56K 'linmodem' and a dial-up. Maybe when we move in August I can look into a higher speed connection.
What are your stats?
I also have ipchains and 'portsentry' running. I'm not sure that I need 'portsentry' any longer since building the chains, but I have it in -atcp/-audp mode. I thought it to be a good secondary defense.
I do like the way 'junkbuster' crunches cookies, it took a little configuring to allow sites like 'linukquestions', to use cookies for ID/etc. I also had to change the file names on some of my own *.gifs since 'junkbuster' generically filters anything named *banner*.
I just wondered if anything could be done to improve the speed a little. Besides more up2date hardware. I'm not ready for that just yet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.