Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am looking for help on building a Linux based filtering tap for my IDS implementation. I would love to purchase a hardware driven filtering tap but they are too expensive so I know want to try and build a Linux box that can do the same thing.
The idea is to have a network tap or span port connected to the server and then the server will filter and/or redirect the mirrored traffic to the appropriate tool. This will help me control what tools see what traffic.
The traffic from user 1 would be forwarded out the interfaces connected to tool1 and tool3. User2 would be forwarded to tool2, user3 would be forwarded to tool3 and user4's traffic would just be dropped. The interfaces on the tool servers would be configured to listen only would not do any routing of traffic back to the users, this is strictly to copy the data and pass it to my tools.
I don't see any particular reason why this couldn't be accomplished with iptables and a decent router. That being said you've not really asked any specific question that someone can answer other than "is it possible?"
I'd check out DaemonLogger, and maybe Linux Interface Bonding and other pages on that site. The problem with not purchasing a tap is that you will add a single point of failure if your monitoring box is inline. Real taps will continue to pass traffic even if they aren't powered on.
The idea is to use a tap to mirror the data to the Linux server. Then the Linux server would use iptables to filter the traffic and forward it out additional interfaces to the appropriate servers that are connected via cross-over cables. The IDS servers will then have a promiscuous port to listen to the traffic. What would an example config be for this type of configuration on the Linux server? I currently do not have a config started.