mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: saw@saw.sw.com.sg (Andrey Savochkin)
Cc: linux-kernel@vger.kernel.org, cfriesen@nortelnetworks.com
Subject: Re: how to see manually specified proxy arp entries using "ip neigh"
Date: Sun, 21 Oct 2001 21:21:32 +0400 (MSK DST)	[thread overview]
Message-ID: <200110211721.VAA31390@ms2.inr.ac.ru> (raw)
In-Reply-To: <20011020145515.A17623@castle.nmd.msu.ru> from "Andrey Savochkin" at Oct 20, 1 02:55:15 pm

Hello!

> What do you think will happen when a broadcast ARP request for 1.2.3.4
> arrives to both eth0 and eth2?

Nothing. Linuxes attached to the segment even will not notice this.
Just check and guess why. :-)

Windows will dump a funny popup saying that someone uses
their address, but however will continue to work. Probably
with short periods of service deaths if the router is not a router
really, but drops everything instead.


> How can it be done better?

I permanently remind that the situation when a part of protocol
is firewalled, and part of it has _no_ firewall hooks does not smell well.
Proxy arp rules are essentially some underdeveloped private ARP-only
firewall rules.

So, if you rely on core facilities, believe to them and do not break
them with some additional filters.

If you broke them f.e. announcing a pseudo-router with forwarding
enabled but dropping everything with a firewall rule, ARP must not
take care of this. That part of code which drops IP is responsible
for ARPing being in sync to its rules.

Alexey

  reply	other threads:[~2001-10-21 17:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 19:15 how to see manually specified proxy arp entries using "ip neigh" command? Christopher Friesen
2001-10-18 19:25 ` how to see manually specified proxy arp entries using "ip neigh" kuznet
2001-10-18 20:02   ` Richard B. Johnson
2001-10-18 20:08   ` Christopher Friesen
2001-10-19 16:40     ` kuznet
2001-10-19 18:44     ` Matthew G. Marsh
2001-10-19 19:57       ` Christopher Friesen
2001-10-19 13:32   ` Andrey Savochkin
2001-10-19 17:13     ` kuznet
2001-10-20 10:55       ` Andrey Savochkin
2001-10-21 17:21         ` kuznet [this message]
2001-10-23 10:33           ` Andrey Savochkin
2001-10-20 19:56 Julian Anastasov
2001-10-21 17:44 ` kuznet
2001-10-23  8:47 ` Andrey Savochkin

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=200110211721.VAA31390@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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®