From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Cleanest way to deal with loopback interface?
Date: Wed, 13 Apr 2005 21:35:25 -0400 [thread overview]
Message-ID: <20050414013525.GA32192@bender.817west.com> (raw)
In-Reply-To: <1113436673.3544.186.camel@seberino.spawar.navy.mil>
On Wed, Apr 13, 2005 at 04:57:53PM -0700, Christian Seberino wrote:
> Thank you very much!
> Are you saying that there is no reason for firewalls to check for and
> drop packets addressed to and from 127.0.0.1 because Linux TCP stack
> already drops those automatically? I didn't know source IP addresses
> were checked by default. This is almost like a built in 'always on'
> firewalling on Linux!?
>
> In other words, if I tried to spoof packets to your LAN from 127.0.0.1,
> they would never get through even with no firewalls?
yeah--somewhere around line 1434 of:
/usr/src/linux-2.4.28/net/ipv4/route.c
on the machine i'm looking at.
-j
--
"Chris: Hi, my name is Chris. Mom and dad said that I'm supposed to be
on my best behavior tonight and not say "poop". Oh god. What have I
done?"
--Family Guy
next prev parent reply other threads:[~2005-04-14 1:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 20:50 Cleanest way to deal with loopback interface? Christian Seberino
2005-04-13 21:00 ` Alexander Samad
2005-04-13 21:13 ` Jason Opperisano
2005-04-13 23:57 ` Christian Seberino
2005-04-14 1:35 ` Jason Opperisano [this message]
2005-04-14 1:32 ` Taylor Grant
2005-04-14 2:43 ` Jason Opperisano
2005-04-14 1:09 ` Taylor Grant
2005-04-17 23:27 ` seberino
2005-04-18 0:04 ` Thomas Jones
2005-04-18 20:02 ` Christian Seberino
2005-04-18 20:05 ` Taylor, Grant
2005-04-18 21:16 ` Thomas Jones
2005-04-18 20:09 ` Christian Seberino
2005-04-18 20:42 ` Taylor, Grant
2005-04-14 1:23 ` Taylor Grant
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=20050414013525.GA32192@bender.817west.com \
--to=opie@817west.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox