netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Ruppert <idl0r@qasl.de>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: SYNPROXY *NAT/redirects etc.
Date: Wed, 24 Jun 2015 20:07:35 +0200	[thread overview]
Message-ID: <8abd0f5b62a44563cb0de95f9a39ee6c@qasl.de> (raw)
In-Reply-To: <5589D08C.1000601@plouf.fr.eu.org>

Hi Pascal,

On 2015-06-23 23:33, Pascal Hambourg wrote:
> Christian Ruppert a écrit :
>> 
>> I noticed that neither *NAT nor redirects will work when using the
>> SYNPROXY module with e.g. those settings:
>> net.netfilter.nf_conntrack_tcp_loose=0
>> sysctl -w net.ipv4.tcp_syncookies=1
>> sysctl -w net.netfilter.nf_conntrack_tcp_loose=0
>> sysctl -w net.ipv4.tcp_timestamps=1
>> 
>> iptables -t raw -I PREROUTING -p tcp -m tcp --syn -j CT --notrack
> 
> This rule disables connection tracking which is required for stateful
> NAT operation.

Thanks! From what I've seen/read, this rule is required or am I wrong? 
It needs to do the complete handshake and upon success it will 
pass/forward the connection or act somehow like a real proxy.

> 
>> iptables -I INPUT -p tcp -m tcp -m conntrack --ctstate 
>> INVALID,UNTRACKED
>> -j SYNPROXY --sack-perm --timestamp --wscale 7 --mss 1460
>> iptables -A INPUT -m conntrack --ctstate INVALID -j DROP

-- 
Regards,
Christian Ruppert

  reply	other threads:[~2015-06-24 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 13:32 SYNPROXY *NAT/redirects etc Christian Ruppert
2015-06-23 21:33 ` Pascal Hambourg
2015-06-24 18:07   ` Christian Ruppert [this message]
2015-06-24 21:57     ` Pascal Hambourg
2015-07-28 15:34       ` Christian Ruppert

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=8abd0f5b62a44563cb0de95f9a39ee6c@qasl.de \
    --to=idl0r@qasl.de \
    --cc=netfilter@vger.kernel.org \
    --cc=pascal@plouf.fr.eu.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;
as well as URLs for NNTP newsgroup(s).