Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
I have been reading here a lot and finally registered since I didn't find an answer to my question.
We have the following setup: A linux software router/firewall running SuSe and 9 machines using it to access the net. Some of these machines are DualOS (Linux/Win) machines and I want to prevent internet access if the machines boot into windows. My idea right now is, since we do not use DHCP, to give a different IP to the machine if it boots into Windows and easily block access for these IPs.
I would rather have it another way though. Is there any way to make an ipchains script / rule that detects if a machine is broadcasting on any ports 137-139 and then block internet access for a given amout of minutes?
You could set up portsentry on the inward facing interface, add port 139 to its list of "evil ports" and watch it drop those boxes from the routing table :-)
Originally posted by cyber-worx You could set up portsentry on the inward facing interface, add port 139 to its list of "evil ports" and watch it drop those boxes from the routing table :-)
You can basically tell port sentry to ignore boxes outputting on certain ports.
You could implement the same sort of functionality with iptables and much scripting, most likely involving netcat. but that really would be making life difficult.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.