From: Blizbor <kernel@globalintech.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 native IPsec implementation question
Date: Mon, 15 Nov 2004 15:48:04 +0100 [thread overview]
Message-ID: <4198C1A4.8080707@globalintech.pl> (raw)
In-Reply-To: <Pine.LNX.4.53.0411151455020.17543@yvahk01.tjqt.qr>
;) My question wasn't "how does ipsec rules looks" but "why its
implemented such a way".
These almost exactly are rules I want to implement.
But, when you run tcpdump -nni eth0 you can see ESP traffic _and_ one
direction of something going through IPsec.
Imagine, that on eth0 five IPsec tunnels are "ended" and only one I wish
to allow tcp/389.
It seems not possible to just allow tcp/389 from only one VPN because IP
addresses are changing daily
in all 5 remote locations.
Moreover "-i eth0 -j DROP" blocks IPsec traffic ... (or -o eth0 i don't
remember direction)
Jan Engelhardt wrote:
>>2. Why IPsec in 2.6 doesn't creates entries in the route tables ?
>>
>>
>
>Because it doesnot create a device ipsecN?
>
>
And thats the issue - WHY it is implemented such a way ?
Which developement considerations caused that choice ?
Regards,
Blizbor
next prev parent reply other threads:[~2004-11-15 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 13:44 2.6 native IPsec implementation question Blizbor
2004-11-15 14:02 ` Jan Engelhardt
2004-11-15 14:48 ` Blizbor [this message]
2004-11-15 15:05 ` Jan Engelhardt
2004-11-15 16:47 ` Blizbor
2004-11-16 17:47 ` Andreas Unterkircher
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=4198C1A4.8080707@globalintech.pl \
--to=kernel@globalintech.pl \
--cc=jengelh@linux01.gwdg.de \
--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