All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devaraj Das <ddas@india.hp.com>
To: netfilter@lists.netfilter.org
Subject: libipq
Date: Thu, 08 Apr 2004 14:02:45 +0530	[thread overview]
Message-ID: <40750E2D.2E4DA20@india.hp.com> (raw)
In-Reply-To: 9723.1081409292@zworg.com

Hi all,
If I have an application (using libipq) that's waiting for packets, and I
want to inspect the payload, will the payload be encrypted in case I use
esp/transport with kernel 2.6 (with built-in ipsec)?
Thanks,
Devaraj.

__ Radien__ wrote:

> Dear All
>
>    I have read some about ISA server from it's documentation. There were
> listed some facilities for example Circuit Level and App Level
> filtering and gateway.
>
>    Circuit level filtering and gateway were strange for me. What are
> they?
>    How can I see such capabilities in iptables? How they get mapped in
> iptables?
>
>    Is iptables sth other than what ip_conntrack_ftp.o mudule do in
> Application Layer?
>
> Regards
> __Radien__



  reply	other threads:[~2004-04-08  8:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  7:28 Circuit Level Gateway & Filtering!? __ Radien__
2004-04-08  8:32 ` Devaraj Das [this message]
2004-04-08  8:48   ` libipq Antony Stone
2004-04-08  8:40 ` Circuit Level Gateway & Filtering!? Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2007-08-14 17:33 libipq Micheal Scofield
2007-08-14 20:02 ` libipq Eric Leblond
2007-06-09 17:46 libipq Simon
2007-06-09 18:15 ` libipq Eric Leblond
2007-06-09 19:29   ` libipq Simon
     [not found] <OFD0D60AB8.75553E41-ON65256E7C.001E4C71@hss.hns.com>
2004-04-20 12:21 ` libipq Jee J.Z.
2004-04-19 13:13 libipq aksingh
2003-12-17 14:57 libipq Oumer Teyeb
2003-12-16 12:27 ftos why obsolate CoyoteTM
2003-12-17 14:49 ` libipq Oumer Teyeb
2003-08-11 13:05 libipq Bogaerts Bart

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=40750E2D.2E4DA20@india.hp.com \
    --to=ddas@india.hp.com \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.