Re: Blocking incoming IP address immediately
From: Cameron L. Spitzer (spambait_at_merde.greens.org)
Date: 11/29/04
- Next message: Sundial Services: "Re: My Linux server got hacked last night -- please help!"
- Previous message: Colin McKinnon: "Re: My Linux server got hacked last night -- please help!"
- In reply to: repo: "Re: Blocking incoming IP address immediately"
- Next in thread: Nico Declerck: "Re: Blocking incoming IP address immediately"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 Nov 2004 22:04:11 GMT
In article <slrncqmhtv.u14.news@cannabis.beginnerslinux.org>, repo wrote:
>
> you can use the route command
> /sbin/route add -host $TARGET$ reject
Huh? man route:
SYNOPSIS
route [-v] [-A family] add [-net|-host] target [netmask Nm] [gw Gw]
[metric N] [mss M] [window W] [irtt I] [reject] [mod] [dyn]
[reinstate] [[dev] If]
OPTIONS
reject install a blocking route, which will force a route lookup to
fail. This is for example used to mask out networks before
using the default route. This is NOT for firewalling.
EXAMPLES
route add -net 10.0.0.0 netmask 255.0.0.0 reject
This installs a rejecting route for the private network
"10.x.x.x."
I don't think a reject route does what you want here.
Cameron
- Next message: Sundial Services: "Re: My Linux server got hacked last night -- please help!"
- Previous message: Colin McKinnon: "Re: My Linux server got hacked last night -- please help!"
- In reply to: repo: "Re: Blocking incoming IP address immediately"
- Next in thread: Nico Declerck: "Re: Blocking incoming IP address immediately"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|