netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: David Miller <davem@davemloft.net>
Cc: hpa@zytor.com, netdev@vger.kernel.org
Subject: Re: ProxyARP and IPSec
Date: Thu, 24 Aug 2006 12:50:37 +0200	[thread overview]
Message-ID: <20060824105037.GL3470@postel.suug.ch> (raw)
In-Reply-To: <20060823.151424.78711856.davem@davemloft.net>

* David Miller <davem@davemloft.net> 2006-08-23 15:14
> From: Thomas Graf <tgraf@suug.ch>
> Date: Wed, 23 Aug 2006 21:14:25 +0200
> 
> > * H. Peter Anvin <hpa@zytor.com> 2006-08-22 17:31
> > > Specifically, Linux will not ProxyARP for an address unless it has a 
> > > route for it, *and* that route either has a DNAT marking or points to a 
> > > different interface than the input interface:
> > 
> > I can think of a very ugly way: Use netfilter to match on the
> > arp packet prerouting, set nfmark to some value, create a routing
> > rule matching the fwmark again, have it look up a separate table
> > with a dummy route pointing to a dummy device. Make sure to have
> > a proxy neighbour entry as using the device proxy_arp sysctl would
> > fail again.
> 
> This shows we have a usability problem if that's the only way
> to do this :-)

What about adding blackhole device to be used for such routes.
I believe it would be good architecture to always use devices
to state directions packets are being received from and sent to.

  parent reply	other threads:[~2006-08-24 10:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  0:31 ProxyARP and IPSec H. Peter Anvin
2006-08-23 19:14 ` Thomas Graf
2006-08-23 22:14   ` David Miller
2006-08-23 23:18     ` Alexey Kuznetsov
2006-08-24  1:12       ` H. Peter Anvin
2006-08-24  1:14         ` H. Peter Anvin
2006-08-24  2:20           ` Andy Gay
2006-08-24  4:14             ` H. Peter Anvin
2006-08-24 12:50               ` Alexey Kuznetsov
2006-08-26  4:16                 ` H. Peter Anvin
2006-09-02 15:36                   ` Stephen J. Bevan
2006-09-02 17:30                     ` H. Peter Anvin
2006-09-02 20:54                       ` Stephen J. Bevan
2006-09-05  5:17                         ` H. Peter Anvin
2006-09-04 22:27                       ` Alexey Kuznetsov
2006-09-05  5:12                         ` H. Peter Anvin
2006-09-05  9:05                           ` Alexey Kuznetsov
2006-09-22 20:36                             ` David Miller
2006-09-23  4:22                               ` Stephen J. Bevan
2006-09-06  2:25                         ` Stephen J. Bevan
2006-08-24 10:50     ` Thomas Graf [this message]
2006-09-07 22:28       ` H. Peter Anvin
2006-09-08  7:37         ` Thomas Graf

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=20060824105037.GL3470@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --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).