From: David Miller <davem@davemloft.net>
To: hawk@comx.dk
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH] net: RFC3069, private VLAN proxy arp support
Date: Thu, 07 Jan 2010 00:59:19 -0800 (PST) [thread overview]
Message-ID: <20100107.005919.138283009.davem@davemloft.net> (raw)
In-Reply-To: <20100105155047.13309.79610.stgit@firesoul.comx.local>
From: Jesper Dangaard Brouer <hawk@comx.dk>
Date: Tue, 05 Jan 2010 16:50:47 +0100
> This is to be used together with switch technologies, like RFC3069,
> that where the individual ports are not allowed to communicate with
> each other, but they are allowed to talk to the upstream router. As
> described in RFC 3069, it is possible to allow these hosts to
> communicate through the upstream router by proxy_arp'ing.
>
> This patch basically allow proxy arp replies back to the same
> interface (from which the ARP request/solicitation was received).
>
> Tunable per device via proc "proxy_arp_pvlan":
> /proc/sys/net/ipv4/conf/*/proxy_arp_pvlan
>
> This switch technology is known by different vendor names:
> - In RFC 3069 it is called VLAN Aggregation.
> - Cisco and Allied Telesyn call it Private VLAN.
> - Hewlett-Packard call it Source-Port filtering or port-isolation.
> - Ericsson call it MAC-Forced Forwarding (RFC Draft).
>
> Signed-off-by: Jesper Dangaard Brouer <hawk@comx.dk>
Applied.
prev parent reply other threads:[~2010-01-07 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 15:50 [net-next PATCH] net: RFC3069, private VLAN proxy arp support Jesper Dangaard Brouer
2010-01-06 6:03 ` Eric Dumazet
2010-01-06 9:49 ` Jesper Dangaard Brouer
2010-01-06 10:28 ` Eric Dumazet
2010-01-06 12:52 ` Mark Smith
2010-01-06 14:17 ` Jesper Dangaard Brouer
2010-01-06 14:35 ` Mark Smith
2010-01-06 18:59 ` Jan Ceuleers
2010-01-07 8:59 ` David Miller [this message]
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=20100107.005919.138283009.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hawk@comx.dk \
--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).