From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: netdev@oss.sgi.com, kuznet@ms2.inr.ac.ru
Subject: Re: Change proxy_arp to respond only for valid neighbours
Date: Mon, 9 Feb 2004 12:19:26 -0800 [thread overview]
Message-ID: <20040209121926.6f016ebf.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402082234110.6268@u.domain.uli>
On Sun, 8 Feb 2004 22:44:05 +0200 (EET)
Julian Anastasov <ja@ssi.bg> wrote:
> - the 'skb->pkt_type == PACKET_HOST' check has no semantic anymore,
> the requestor should have same information no matter the packet
> type. In all cases we add response delay for all requests, broadcast
> or unicast, to help other authoritative hosts to reply before us.
Do we really want to reply to all the garbage tcpdump causes us
to capture?
That is what the pkt_type is dealing with. If we're in promiscuous
mode, we'll hear ARP requests meant not for any of our devices, we
should not proxy for them right?
RTCF_*NAT is dead wood, the existing route nating stuff is totally broken
an unusable in 2.6.x, the eventual plan was to code up XFRM engine version
of that feature but this is of course not done. Since nobody is complaining
about lack of routing NAT in 2.6.x, I think we should just kill off all references
and if someone gets inspired they can code up the XFRM engine version.
next prev parent reply other threads:[~2004-02-09 20:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 20:44 Change proxy_arp to respond only for valid neighbours Julian Anastasov
2004-02-08 21:14 ` David S. Miller
2004-02-08 21:38 ` Julian Anastasov
2004-02-08 22:44 ` Julian Anastasov
2004-02-09 6:08 ` Pekka Savola
2004-02-09 11:30 ` Julian Anastasov
2004-02-09 15:01 ` jamal
2004-02-09 22:23 ` Julian Anastasov
2004-02-09 22:50 ` jamal
2004-02-09 23:52 ` Julian Anastasov
2004-02-10 1:21 ` jamal
2004-02-10 9:44 ` Julian Anastasov
2004-02-10 10:48 ` jamal
2004-02-11 1:52 ` Julian Anastasov
2004-02-11 13:11 ` jamal
2004-02-11 14:32 ` Julian Anastasov
2004-02-12 4:48 ` jamal
2004-02-12 9:46 ` Julian Anastasov
2004-02-12 14:21 ` jamal
2004-02-12 19:37 ` kuznet
2004-02-13 0:34 ` Julian Anastasov
2004-02-11 13:40 ` jamal
2004-02-11 14:53 ` Julian Anastasov
2004-02-09 20:19 ` David S. Miller [this message]
2004-02-09 21:26 ` James Morris
2004-02-09 21:39 ` Ben Greear
2004-02-09 21:45 ` David S. Miller
2004-02-09 22:42 ` Julian Anastasov
2004-02-09 22:45 ` David S. Miller
2004-02-09 22:32 ` Julian Anastasov
2004-02-09 21:58 ` David S. Miller
2004-02-09 22:49 ` Julian Anastasov
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=20040209121926.6f016ebf.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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).