netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: Topher Fischer <javert42@cs.byu.edu>, netdev@vger.kernel.org
Subject: Re: ARP Spoofing
Date: Wed, 02 May 2007 14:39:04 -0600	[thread overview]
Message-ID: <4638F6E8.3060609@nortel.com> (raw)
In-Reply-To: <4638DEB9.90608@hp.com>

Vlad Yasevich wrote:

> If by arp spoofing you mean receiving arp replies from multiple sources and
> trusting all of them, then I haven't seen anything.
> 
> I don't know the history as to why nothing has has been done.

This concept is a valuable tool to allow for fast publishing of IP 
address takeover in redundant-server situations.

There are ways in which it can be misused, but that doesn't make it an 
invalid technique.

Chris

  reply	other threads:[~2007-05-02 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 17:44 ARP Spoofing Topher Fischer
2007-05-02 18:55 ` Vlad Yasevich
2007-05-02 20:39   ` Chris Friesen [this message]
2007-05-02 20:45     ` Vlad Yasevich
2007-05-02 23:45     ` Topher Fischer
2007-05-03  0:16       ` Stephen Hemminger

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=4638F6E8.3060609@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=javert42@cs.byu.edu \
    --cc=netdev@vger.kernel.org \
    --cc=vladislav.yasevich@hp.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;
as well as URLs for NNTP newsgroup(s).