Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "David C. Hart" <DCH@TQMcube.com>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: Iptables Mailing List <netfilter@lists.netfilter.org>
Subject: Re: IP Spoofing
Date: Wed, 05 Nov 2003 15:08:23 -0500	[thread overview]
Message-ID: <1068062902.1494.25.camel@main.tqmcube.com> (raw)
In-Reply-To: <200311051951.hA5Jpdr13332@agate.rockstone.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

On Wed, 2003-11-05 at 14:51, Antony Stone wrote:
> On Wednesday 05 November 2003 7:31 pm, Leandro Takashi Hirano wrote:
> 
> > Now I would like to know about the IP Spoofing rule, how does it works?
> >
> > -	iptables -A INPUT -s 192.168.1.0/24 -i ! eth0 -j DROP
> 
> Any packet with a source address in the Class C range 192.168.1.x which does 
> not come from eth0 will be DROPped.

Funny I was similarly confused. What happens to packets from the LAN
given that they don't originate from eth0?
> 
> > I don´t know how can it block ip spoofing attack...
> 
> These rules assume that eth0 is your internal network, and your internal 
> network range is 192.168.1.0/24.
> 
> No packets with your own source address should come from outside (rule 1) and 
> all packets from inside should have your own source address (rule 2).
> 
> Therefore these two rules stop people on the outside pretending that they 
> live on your network, and people on the inside pretending that they don't.
> 
> Antony.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-05 20:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 19:31 IP Spoofing Leandro Takashi Hirano
2003-11-05 19:51 ` Antony Stone
2003-11-05 20:08   ` David C. Hart [this message]
2003-11-05 20:10     ` Antony Stone
2003-11-05 20:26     ` Jeffrey Laramie
2003-11-05 20:57       ` David C. Hart
2003-11-05 21:22         ` Jeffrey Laramie
2003-11-05 20:19   ` Leandro Takashi Hirano
2003-11-05 20:39     ` Antony Stone
2003-11-07 12:26       ` Ted Kaczmarek
2003-11-07 12:32         ` Antony Stone
2003-11-07 13:34         ` David C. Hart
2003-11-07 13:56           ` Antony Stone
2003-11-07 14:04             ` David C. Hart
2003-11-08 18:06           ` Ted Kaczmarek
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 20:53 bmcdowell
2003-04-10 20:39 IP spoofing Daniel Chemko
2003-04-10 20:26 Farshad
2003-04-10 21:10 ` Peteris Krumins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1068062902.1494.25.camel@main.tqmcube.com \
    --to=dch@tqmcube.com \
    --cc=Antony@Soft-Solutions.co.uk \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox