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: Fri, 19 Oct 2001 21:13:12 +0400 (MSK DST) [thread overview]
Message-ID: <200110191713.VAA03502@ms2.inr.ac.ru> (raw)
In-Reply-To: <20011019173233.A12919@castle.nmd.msu.ru> from "Andrey Savochkin" at Oct 19, 1 05:32:33 pm
Hello!
> 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!),
Andrey, do not fuck me brains. :-) (translate this to English :-))
No "serious" consequences exist. And not serious ones are surely covered
by the same mistakes which you can make forced to add useless element
to configuration.
I am sorry, but each additional item to configure increases
probability of mistake by... count yourselves. :-)
> Or you just want to cripple `ip'? :-)
Rather to cure it amputating dead flesh alien for "ip".
"ip neigh add proxy" was added as a demo of "right" interface
to this feature mostly to have a reason to say several words
about sense of proxy arp in manual. As soon as people do not read docs
anyway (or I wrote some unintellibible shit there) this function
loses its sense.
Alexey
next prev parent reply other threads:[~2001-10-19 17:13 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 [this message]
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=200110191713.VAA03502@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®