From: "Jeffrey B. Ferland" <jeff@storyinmemo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Some questions
Date: Tue, 13 Dec 2005 15:46:39 +0000 [thread overview]
Message-ID: <8B21CCE6-493E-49BC-B9E8-4E4705F88361@storyinmemo.com> (raw)
In-Reply-To: <5c6851530512130443j3a4ac990l59c6ac7552557966@mail.gmail.com>
On Dec 13, 2005, at 7:43 AM, Robb Bossley wrote:
> Anyways, I have two questions related to the use of iptables.
>
> 1. I read on a post somewhere that it is smart to put the following
> two rules at the end of one's iptables ruleset:
> iptables -A INPUT -p tcp -i eth0 -j REJECT --reject-with tcp-reset
> iptables -A INPUT -p udp -i eth0 -j REJECT --reject-with tcp-reset
> The reasoning was that it would not look like a software firewall, but
> rather would look like a machine that had no open ports. Does this
> sound reasonable? What would all of you do?
>
I only have one comment about that.... reject udp packets with a tcp
reset? I think that would look more like a very inventive
implementation of tcp/udp over ip ;)
OK, second comment: it really depends on what you want your box to
appear as.
> 2. I also read on some website that it is important to use this line
> in the setup for iptables:
> echo "1" > /proc/sys/net/ipv4/conf/eth0/rp_filter
> What does this do (it said something about spoofing, but I did not
> understand), and is it necessary?
It ensures that you don't generate "martian packets." If your ip is
10.0.0.1, your interface will only spit out packets with that ip
address, and silently drop the rest.
-Jeff
SIG: HUP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-13 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 12:43 [LARTC] Some questions Robb Bossley
2005-12-13 15:46 ` Jeffrey B. Ferland [this message]
2005-12-13 21:06 ` Georgi Alexandrov
2005-12-14 6:11 ` Georgi Alexandrov
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=8B21CCE6-493E-49BC-B9E8-4E4705F88361@storyinmemo.com \
--to=jeff@storyinmemo.com \
--cc=lartc@vger.kernel.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.