Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Jan 2017 22:17:20 +0100
From:      "Kristof Provost" <kp@FreeBSD.org>
To:        "Ermal =?utf-8?q?Lu=C3=A7i?=" <eri@freebsd.org>
Cc:        "Bakul Shah" <bakul@bitblocks.com>, "FreeBSD Net" <freebsd-net@freebsd.org>, "Alan Somers" <asomers@freebsd.org>
Subject:   Re: pf & NAT issue
Message-ID:  <C40A590C-610E-4283-83AB-6CDF65EEDE86@FreeBSD.org>
In-Reply-To: <CAPBZQG3sFKRTPbRGh7KSh1bsp2FHNX84Baw0dV3-QXKBhZQVvw@mail.gmail.com>
References:  <20170120083555.ACCF9124AEA4@mail.bitblocks.com> <7C29D00C-94C0-4550-B1B2-CE307482B544@FreeBSD.org> <CAOtMX2hTcEkw_WzgtcEEipGY391zB=skrk7O=dknRMMG%2BDa%2BBA@mail.gmail.com> <20170120203106.CD2C8124AEA4@mail.bitblocks.com> <FB01B6F5-5269-4FE4-9B22-51A6AA60705E@FreeBSD.org> <20170120205933.8948A124AEA3@mail.bitblocks.com> <CAPBZQG3sFKRTPbRGh7KSh1bsp2FHNX84Baw0dV3-QXKBhZQVvw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Jan 2017, at 22:12, Ermal Luçi wrote:
> Most probably your timeouts are aggressive on states garbage 
> collection.
> Give a look to those state limit teardown it might improve things.
>
Less than 30 seconds seems extremely quick to time out.
I also wouldn’t expect pf to set up NAT state in the middle of a TCP 
connection.

It’s certainly worth a try to play with the timeouts though.

It might be interesting to see what they’re set to right now. `pfctl 
-s all` should show them.

Regards,
Kristof



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C40A590C-610E-4283-83AB-6CDF65EEDE86>