From: Andrey Savochkin <saw@saw.sw.com.sg>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org,
Christopher Friesen <cfriesen@nortelnetworks.com>
Subject: Re: how to see manually specified proxy arp entries using "ip neigh"
Date: Fri, 19 Oct 2001 17:32:33 +0400 [thread overview]
Message-ID: <20011019173233.A12919@castle.nmd.msu.ru> (raw)
In-Reply-To: <3BCF2A44.60B295FD@nortelnetworks.com> <200110181925.XAA04814@ms2.inr.ac.ru>
In-Reply-To: <200110181925.XAA04814@ms2.inr.ac.ru>; from "A.N.Kuznetsov" on Thu, Oct 18, 2001 at 11:25:42PM
Alexey,
On Thu, Oct 18, 2001 at 11:25:42PM +0400, A.N.Kuznetsov wrote:
>
> > I (and others) have asked this a couple times here and on the netdev list, and
> > so far nobody has answered it (not even negatively).
>
> :-) And me answered to this hundred of times: "no way". :-)
>
> Ability to add/delete them with "ip neigh" will be removed in the next
> snapshot as well. The feature is obsolete.
Well, in solutions I ship to customers I need to use some proxy-arp features.
I don't want to turn on proxy arp on an interface basis, because subtle
mistakes in network configuration with proxy arp turned on may have serious
consequences, including arp storm (sic!), and people, especially those called
customers, do make mistakes.
So far, the solution has been to manually create proxy arp entries, that are
known to be safe.
Are you opposing the idea of proxy arp entries being created not by an
automatic discovery (arp on other interface)?
Or you just want to cripple `ip'? :-)
Andrey
next prev parent reply other threads:[~2001-10-19 13:24 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 [this message]
2001-10-19 17:13 ` kuznet
2001-10-20 10:55 ` Andrey Savochkin
2001-10-21 17:21 ` kuznet
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=20011019173233.A12919@castle.nmd.msu.ru \
--to=saw@saw.sw.com.sg \
--cc=cfriesen@nortelnetworks.com \
--cc=kuznet@ms2.inr.ac.ru \
--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®