From: Philip Craig <philipc@snapgear.com>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: conntrack: UDP NAT vs. VPN tunnel
Date: Fri, 03 Aug 2007 10:25:37 +1000 [thread overview]
Message-ID: <46B27601.8000505@snapgear.com> (raw)
In-Reply-To: <200708021817.38209.thomas.jarosch@intra2net.com>
Thomas Jarosch wrote:
> I've now searched for possible solutions. I could write a program that gets
> called after the VPN tunnel is reestablished and deletes all UDP NAT
> conntracks matching the IPs of the VPN tunnel. This is rather complex,
> but possible. Maybe there is a more simple solution?
Add a filter rule that drops packets with a VPN destination that are
not going over the VPN. Then the conntrack is never created until
the VPN is up. This is good for security too, so that you aren't
leaking private data.
[BTW, the netfilter list is more appropriate for this question.]
next prev parent reply other threads:[~2007-08-03 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 16:17 conntrack: UDP NAT vs. VPN tunnel Thomas Jarosch
2007-08-03 0:25 ` Philip Craig [this message]
2007-08-03 14:13 ` Thomas Jarosch
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=46B27601.8000505@snapgear.com \
--to=philipc@snapgear.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=thomas.jarosch@intra2net.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.