netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Fedoryschenko <denys@visp.net.lb>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [RFC] arp announce, arp_proxy and windows ip conflict verification
Date: Sun, 5 Jul 2009 01:00:08 +0300	[thread overview]
Message-ID: <200907050100.08148.denys@visp.net.lb> (raw)
In-Reply-To: <m13a9c6rhv.fsf@fess.ebiederm.org>

On Sunday 05 July 2009 00:57:32 Eric W. Biederman wrote:
>
> How can that possibly be a correct network configuration?
>
> Eric
It is a problem to have different networks, who doesn't communicate one with 
each other, in same ethernet segment?

Does it violate anything?

  reply	other threads:[~2009-07-04 22:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 11:44 [RFC] arp announce, arp_proxy and windows ip conflict verification Denys Fedoryschenko
2009-03-13 23:02 ` David Miller
2009-06-30 22:55 ` Eric W. Biederman
2009-06-30 22:54   ` Denys Fedoryschenko
     [not found]     ` <m1iqicyjmr.fsf@fess.ebiederm.org>
2009-07-01  9:00       ` Denys Fedoryschenko
2009-07-01  9:42       ` Denys Fedoryschenko
2009-07-01 17:40         ` Eric W. Biederman
2009-07-01 18:12           ` Denys Fedoryschenko
2009-07-01 19:01           ` Denys Fedoryschenko
2009-07-02 20:36             ` Eric W. Biederman
2009-07-02 20:51             ` Eric W. Biederman
2009-07-02 21:22               ` Denys Fedoryschenko
2009-07-02 22:18                 ` Eric W. Biederman
2009-07-02 23:03                   ` Denys Fedoryschenko
2009-07-02 23:23                     ` Eric W. Biederman
2009-07-02 23:46                       ` Denys Fedoryschenko
2009-07-03  1:38                         ` David Miller
2009-07-03  3:14                         ` Eric W. Biederman
2009-07-03 11:02                           ` Denys Fedoryschenko
2009-07-03 20:20                             ` David Miller
2009-07-03 20:37                               ` Denys Fedoryschenko
2009-07-04  0:46                                 ` Eric W. Biederman
2009-07-04  7:55                                   ` Denys Fedoryschenko
2009-07-04 15:00                                     ` Eric W. Biederman
2009-07-04 15:03                                       ` Denys Fedoryschenko
2009-07-04 21:57                                         ` Eric W. Biederman
2009-07-04 22:00                                           ` Denys Fedoryschenko [this message]
2009-07-04 23:22                                             ` Mark Smith
2009-07-05  0:07                                               ` Eric W. Biederman
2009-07-05  0:28                                                 ` Denys Fedoryschenko
2009-07-05  6:16                                                 ` Mark Smith
2009-07-04 23:47                                             ` Eric W. Biederman
2009-07-03  1:34                     ` David Miller
2009-07-02 23:13                   ` Denys Fedoryschenko
2009-07-01  2:27   ` [PATCH] Revert "ipv4: arp announce, arp_proxy and windows ip conflict verification" Eric W. Biederman
2009-07-01  3:10     ` David Miller

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=200907050100.08148.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).