netdev - Re: [net-next PATCH] net: RFC3069, private VLAN proxy arp support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B4427CE.1040203@gmail.com>
Date:	Wed, 06 Jan 2010 07:03:58 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Jesper Dangaard Brouer <hawk@...x.dk>
CC:	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [net-next PATCH] net: RFC3069, private VLAN proxy arp support

Le 05/01/2010 16:50, Jesper Dangaard Brouer a écrit :
> 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.
> 

Reading RFC 3069, I dont understand why it needs support on hosts themselves.

> This patch basically allow proxy arp replies back to the same
> interface (from which the ARP request/solicitation was received).

Could you give me an example of how it is used ?
Last time I played with proxy arp was 6 years ago :)

Thanks
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html