Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Taylor Grant <gtaylor@riverviewtech.net>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Cleanest way to deal with loopback interface?
Date: Wed, 13 Apr 2005 20:09:46 -0500	[thread overview]
Message-ID: <425DC2DA.7010608@riverviewtech.net> (raw)
In-Reply-To: <20050413211349.GA31336@bender.817west.com>

> allow traffic on the loopback interface unconditionally,  and allow the
> linux routing code 'martian' checks to drop 127.0.0.0/8 packets received
> 'on the wire' as it does by default.

I don't think this is such a good idea.  I could reconfigure my system such that it's loop back interface was not in the 127.0.0.0/8 network and set a route to the 127.0.0.0/8 network to be via your IP on the LAN.  Assuming that your system and my system were on the same LAN and subnet and we could ping each other I would be able to access your 127.0.0.1 address as your kernel would forward traffic to the loop back network in your system.



Grant. . . .


  parent reply	other threads:[~2005-04-14  1:09 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
2005-04-14  1:32       ` Taylor Grant
2005-04-14  2:43         ` Jason Opperisano
2005-04-14  1:09   ` Taylor Grant [this message]
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=425DC2DA.7010608@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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