mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tomc@teamics.com
To: Gerhard Mack <gmack@innerfire.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem:  RFC1166 addressing
Date: Mon, 16 Sep 2002 12:33:54 -0500	[thread overview]
Message-ID: <OFE0F05D6B.6256F71D-ON86256C36.006060FE@teamics.com> (raw)


You are correct sir.   I was just quite surprised to find that it works,
and that I can reassign the 127 network to any interface I like.

tc


                                                                                                                
                    Gerhard Mack                                                                                
                    <gmack@innerfi       To:     tomc@teamics.com                                               
                    re.net>              cc:     linux-kernel@vger.kernel.org                                   
                                         Subject:     Re: Problem:  RFC1166 addressing                          
                    09/16/02 12:25                                                                              
                    PM                                                                                          
                                                                                                                
                                                                                                                




On Mon, 16 Sep 2002 tomc@teamics.com wrote:

> Date: Mon, 16 Sep 2002 11:50:36 -0500
> From: tomc@teamics.com
> To: linux-kernel@vger.kernel.org
> Subject: Problem:  RFC1166 addressing
>
> RFC 1166 states that:
>
>
>  The class A network number 127 is assigned the "loopback"
>          function, that is, a datagram sent by a higher level protocol
>          to a network 127 address should loop back inside the host.  No
>          datagram "sent" to a network 127 address should ever appear on
>          any network anywhere.
>
>  Linux does not enforce this.  I have uncovered some users using this
> function to attempt to circumvent the firewall.  I am able to "create"
127
> network traffic as follows:
>
> Machine 1:   ifconfig eth0:1 127.1.2.3   [ running kernel 2.2.14 ]
>
> Machine 2:   ifconfig eth0:1 127.1.2.4  [ running kernel 2.4.19 ]
>
> Machine 2:  ping 127.1.2.3
>
> Packets move between the hosts.    Also seems to work on Macintosh.


I would call that a bug in the firewall rules.  Depending on the hosts to
behave in such a way as to make life easier for the firewall makes for a
losing proposition.

     Gerhard


--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.





             reply	other threads:[~2002-09-16 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 17:33 tomc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-16 16:50 tomc
2002-09-16 17:04 ` Russell King
2002-09-16 17:25 ` Gerhard Mack
2002-09-16 17:26 ` Richard B. Johnson
2002-09-16 23:06 ` Alan Cox

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=OFE0F05D6B.6256F71D-ON86256C36.006060FE@teamics.com \
    --to=tomc@teamics.com \
    --cc=gmack@innerfire.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®