netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: aj@dungeon.inka.de
Cc: netdev@oss.sgi.com
Subject: Re: ipsec 2.5.70 trouble
Date: Thu, 29 May 2003 14:14:10 -0700 (PDT)	[thread overview]
Message-ID: <20030529.141410.85405194.davem@redhat.com> (raw)
In-Reply-To: <1054235155.596.9.camel@simulacron>

   From: Andreas Jellinghaus <aj@dungeon.inka.de>
   Date: 29 May 2003 21:05:55 +0200
   
   but on the target machine (same lan), I see the
   packets encrypted, but where is that second packet in tcpdump
   comming from?

After we do the transformation, we stick it back into
the nework stack input to prevent stack exhaustion.

And yes it is on purpose and not changing.

  reply	other threads:[~2003-05-29 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 19:05 ipsec 2.5.70 trouble Andreas Jellinghaus
2003-05-29 21:14 ` David S. Miller [this message]
2003-05-29 23:39   ` Andreas Jellinghaus
2003-05-29 23:47     ` David S. Miller

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=20030529.141410.85405194.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aj@dungeon.inka.de \
    --cc=netdev@oss.sgi.com \
    /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).