public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Platte <lists@naasa.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPSEC and bridged interfaces
Date: Tue, 31 Oct 2006 17:19:20 +0100	[thread overview]
Message-ID: <200610311719.20636.lists@naasa.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0610310927270.23540@yvahk01.tjqt.qr>

Am Dienstag, 31. Oktober 2006 09:30 schrieb Jan Engelhardt:
Hi,

> Sounds like those packets are bridged rather than routed (or so it
> sounds). See if that's the case. Check
> http://www.imagestream.com/~josh/PacketFlow-new.png for details.

It looks like my router is able to re-map its IP to the corresponding private 
IP but then this packet is bridged instead of routed (or encrypted). 
Unfortunately, IPSEC routing is not listet in this image.

> You could try `ebtables -t broute -j DROP` to force all packets to be
> routed.

I tried 
ebtables -t broute -A BROUTING -p ipv4 --ip-destination 192.168.0.0/16 -j DROP
but this does not change anything (192.168.0.0/16 is my private, masqueraded 
network).  But nothing changed. I'm thinking about replacing my IPSEC VPN 
with an openvpn tunnel. Maybe then I'll have less problems.

regards,
Jörg

-- 
PGP Key: send mail with subject 'SEND PGP-KEY' PGP Key-ID: FD 4E 21 1D
PGP Fingerprint: 388A872AFC5649D3 BCEC65778BE0C605

      reply	other threads:[~2006-10-31 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 16:29 IPSEC and bridged interfaces Joerg Platte
2006-10-31  8:30 ` Jan Engelhardt
2006-10-31 16:19   ` Joerg Platte [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=200610311719.20636.lists@naasa.net \
    --to=lists@naasa.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jplatte@naasa.net \
    --cc=linux-kernel@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