From: Mark Smith <lk-netdev@lk-netdev.nosense.org>
To: hawk@comx.dk
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [net-next PATCH] net: RFC3069, private VLAN proxy arp support
Date: Thu, 7 Jan 2010 01:05:24 +1030 [thread overview]
Message-ID: <20100107010524.6f577367@opy.nosense.org> (raw)
In-Reply-To: <1262787442.22735.10.camel@jdb-workstation>
On Wed, 06 Jan 2010 15:17:22 +0100
Jesper Dangaard Brouer <hawk@comx.dk> wrote:
> On Wed, 2010-01-06 at 23:22 +1030, Mark Smith wrote:
> > On Wed, 06 Jan 2010 10:49:29 +0100
> > Jesper Dangaard Brouer <hawk@comx.dk> wrote:
> > >
> > > This patch solved the issue by doing proxy arp'ing on the router against
> > > the "local" network, thus making it possible for customers to
> > > communicate, but via the router. This also gives the ability to do
> > > firewalling on the router between customers on an Ethernet. (In our
> > > solution the Linux router also have a personal firewall configurable per
> > > customer.)
> > >
> >
> > I can see value in that - you're forcing all traffic through the
> > upstream router for policy enforcement purposes, without having to have
> > point-to-point (simulated or otherwise) links between customers and the
> > router, and avoiding IP address waste by not using /30s. You're pretty
> > much making the ethernet a Non-broadcast Multi-Access link.
>
> Yes, its actually a quite nice trick, and several switch vendors have
> supported this technology for years (although they all annoying call it
> something differently). And we/ComX have actually also been using this
> for years, including my patch (sorry for being so slow with upstream
> submission).
>
Do you have any issues with router redundance e.g. VRRP? I can't really
think of any, as long as the proxy-arp responses are using the VRRP
virtual router address, rather than the actual NIC's address, and the
routers can see each other via the switch.
> --
> Med venlig hilsen / Best regards
> Jesper Brouer
> ComX Networks A/S
> Linux Network Kernel Developer
> Cand. Scient Datalog / MSc.CS
> Author of http://adsl-optimizer.dk
> LinkedIn: http://www.linkedin.com/in/brouer
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-06 14:35 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 [this message]
2010-01-06 18:59 ` Jan Ceuleers
2010-01-07 8:59 ` David Miller
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=20100107010524.6f577367@opy.nosense.org \
--to=lk-netdev@lk-netdev.nosense.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).