Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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 wish you luck in finding the solution dude though don't expect the bosses to understand that much. Oh by the way I am sorry I am a newbie so I can't be of much help.
Ta
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Well you really can't do a whole lot about it if the attacker is outside your network and using IPs outside your network. The good news is that it's somewhat difficult to have a TCP connection spoof IPs, since you need to know both sides of it.
What you can do is setup your firewall rules so you never allow one of your networks on the wrong side of your firewall. Your external interface should block incoming packets "from" your internal network, and vis versa. It's also a good idea to block all the RFC1918 networks on your Internet interface, as well as the bogon networks.
There is a built-in spoofing filter in /proc/sys/net/ipv4/conf/all/rp_filter.
This is designed to drop packets from spoofed addresses automatically.
In /etc/sysctl.conf add net.ipv4.conf.default.rp_filter = 1 to have it start at boot..
and echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter to make itactive immediately..
As far as the bogus emails are concerned, what exactly are you receiving?
DOS prevention can be handled with an iptables rule, eg iptables -t nat -I PREROUTING -i ethx -m ! limit --limit 10/sec --limit-burst 10 -j DROP
This drops any new packets of any kind if more than 10 per second come in.
10 is a low number, so do iptables-save -c to see how many packets have been dropped by the rule and make the 10 a bit bigger for normal usage..
Be aware though, that flooding your internet connection cannot be prevented at your end, you need help from the ISP..
But your pc won't curl up and die from the traffic...
Last edited by peter_robb; 03-01-2004 at 01:33 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.