From: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
To: IPTables Mailing List <netfilter@lists.netfilter.org>
Subject: Re: IP Spoofing
Date: Wed, 05 Nov 2003 15:26:52 -0500 [thread overview]
Message-ID: <3FA95D0C.5080306@Loudoun-Fairfax.com> (raw)
In-Reply-To: <1068062902.1494.25.camel@main.tqmcube.com>
David C. Hart wrote:
>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?
>
>
In this setup the packets from the LAN have to enter from eth0 as Antony
indicates. Eth1 would have to be the external interface. Keep in mind
that these rules only affect traffic to and from the firewall host
itself. Traffic between the LAN and the internet is handled on the
FORWARD chain.
Jeff
next prev parent reply other threads:[~2003-11-05 20:26 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
2003-11-05 20:10 ` Antony Stone
2003-11-05 20:26 ` Jeffrey Laramie [this message]
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=3FA95D0C.5080306@Loudoun-Fairfax.com \
--to=jalaramie@loudoun-fairfax.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.