All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: conntrack and IKE confused on 2.6.16
Date: Wed, 22 Mar 2006 18:47:03 +0100	[thread overview]
Message-ID: <44218D97.6000002@trash.net> (raw)
In-Reply-To: <BAY103-F14003302261358DE14249BB2D90@phx.gbl>

Marco Berizzi wrote:
> Patrick McHardy wrote:
> 
>> I'm not sure I understand you correctly. The notebook users
>> establishes a VPN to the remote side.
> 
> 
> Yes.
> 
>> Why shouldn't the
>> IKE-traffic be directed back to him?
> 
> 
> lnx and lnx2.6.16 must talk each other to
> establish/renew the ike/ipsec sa, but lnx2.6.16
> is directing packets for itself to the notebook.
> Is this clear?

Not exactly. Is the tunnel between the notebook user and
the remote gateway, between the two gateways or both?

  reply	other threads:[~2006-03-22 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 16:03 conntrack and IKE confused on 2.6.16 Marco Berizzi
2006-03-22 17:24 ` Patrick McHardy
2006-03-22 17:31   ` Marco Berizzi
2006-03-22 17:47     ` Patrick McHardy [this message]
2006-03-23  9:16       ` Marco Berizzi
2006-03-23 18:22         ` Patrick McHardy

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=44218D97.6000002@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pupilla@hotmail.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 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.