All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: netdev@oss.sgi.com, snortwiz@hotmail.com
Subject: Re: OSDL Bugzilla #2399: A user can remotely route a packet through eth0 on a Linux machine
Date: Tue, 11 May 2004 12:15:18 -0700	[thread overview]
Message-ID: <40A12646.7080605@us.ibm.com> (raw)
In-Reply-To: <OF94DCEE79.E30FBAF0-ON88256E91.0067773D-88256E91.0067C495@us.ibm.com>

David Stevens wrote:
> Routing is something done between different hosts. Hosts normally
> will accept packets for any local  address, regardless of
> which interface it was received on.
> 
> That's not a bug; that's how almost everything works.

I think the only issue here is if an application that
binds to an interface should see packets coming in
from another - if that is what is happening here?.

thanks,
Nivedita

  reply	other threads:[~2004-05-11 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:07 OSDL Bugzilla #2399: A user can remotely route a packet through eth0 on a Linux machine Nivedita Singhvi
2004-05-11 18:53 ` David Stevens
2004-05-11 19:15   ` Nivedita Singhvi [this message]
2004-05-11 20:53     ` Olaf Kirch

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=40A12646.7080605@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    --cc=snortwiz@hotmail.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 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.