linux-kernel - Re: IPSEC and bridged interfaces

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] [day] [month] [year] [list]

Message-Id: <200610311719.20636.lists@naasa.net>
Date:	Tue, 31 Oct 2006 17:19:20 +0100
From:	Joerg Platte <lists@...sa.net>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: IPSEC and bridged interfaces

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/