Re: TCP Connection hang - MSS again

2021-04-06 Thread Michael Tuexen
> On 6. Apr 2021, at 19:02, Rodney W. Grimes > wrote: > >> 06.04.2021 19:54, Rodney W. Grimes wrote: 05.04.2021 19:44, Rozhuk Ivan wrote: >>> As I understand, in some cases remote host does not reply with MSS >>> option, and host behind router continue use mss 8960, that

Re: TCP Connection hang - MSS again

2021-04-06 Thread Rodney W. Grimes
> 06.04.2021 19:54, Rodney W. Grimes wrote: > >> 05.04.2021 19:44, Rozhuk Ivan wrote: > >> > > As I understand, in some cases remote host does not reply with MSS > > option, and host behind router continue use mss 8960, that dropped > > by router. > If the peer does not provide

Re: TCP Connection hang - MSS again

2021-04-06 Thread Eugene Grosbein
06.04.2021 19:54, Rodney W. Grimes wrote: >> 05.04.2021 19:44, Rozhuk Ivan wrote: >> > As I understand, in some cases remote host does not reply with MSS > option, and host behind router continue use mss 8960, that dropped > by router. If the peer does not provide an MSS option,

Re: TCP Connection hang - MSS again

2021-04-06 Thread Rodney W. Grimes
> 05.04.2021 19:44, Rozhuk Ivan wrote: > > >>> As I understand, in some cases remote host does not reply with MSS > >>> option, and host behind router continue use mss 8960, that dropped > >>> by router. > >> If the peer does not provide an MSS option, your local FreeBSD based > >> host should

Re: TCP Connection hang - MSS again

2021-04-06 Thread Eugene Grosbein
05.04.2021 19:44, Rozhuk Ivan wrote: >>> As I understand, in some cases remote host does not reply with MSS >>> option, and host behind router continue use mss 8960, that dropped >>> by router. >> If the peer does not provide an MSS option, your local FreeBSD based >> host should use an MSS of

Re: TCP Connection hang - MSS again

2021-04-05 Thread Eugene Grosbein
05.04.2021 16:44, Rozhuk Ivan wrote: > Is any other other options to work around this? Yes. Each entry in the routing table has "mtu" attribute limiting TCP MSS, too. You should use default route with -mtu 1500 attribute. For example, in /etc/rc.conf: defaultroute="X.X.X.X -mtu 1500"

Re: TCP Connection hang - MSS again

2021-04-05 Thread Rozhuk Ivan
On Mon, 5 Apr 2021 13:04:19 +0200 tue...@freebsd.org wrote: > > As I understand, in some cases remote host does not reply with MSS > > option, and host behind router continue use mss 8960, that dropped > > by router. > If the peer does not provide an MSS option, your local FreeBSD based > host

Re: TCP Connection hang - MSS again

2021-04-05 Thread tuexen
> On 5. Apr 2021, at 11:44, Rozhuk Ivan wrote: > > Hi! > > > TCP Connection hang then I try to open > https://online.sberbank.ru/CSAFront/index.do#/ > > FreeBSD 13 desktop + FreeBSD 13 router (pf). > http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/13/base/etc/sysctl.conf > FreeBSD

Re: TCP Connection hang - MSS again

2021-04-05 Thread Rozhuk Ivan
On Mon, 5 Apr 2021 17:23:39 +0700 Eugene Grosbein wrote: > > Is any other other options to work around this? > > Yes. Each entry in the routing table has "mtu" attribute limiting TCP > MSS, too. You should use default route with -mtu 1500 attribute. For > example, in /etc/rc.conf: > >

Re: TCP Connection hang - MSS again

2021-04-05 Thread Rozhuk Ivan
On Mon, 5 Apr 2021 12:44:50 +0300 Rozhuk Ivan wrote: > FreeBSD 13 desktop have no known problems with other websites. > Only with one remonte FreeBSD 12 with same sysctl.conf and mtu 9k. Forgot. FreeBSD 12 reply with MSS 8960, and I fix it in PF: > scrub in on $ext_v4_if0 all max-mss 1400 so

TCP Connection hang - MSS again

2021-04-05 Thread Rozhuk Ivan
Hi! TCP Connection hang then I try to open https://online.sberbank.ru/CSAFront/index.do#/ FreeBSD 13 desktop + FreeBSD 13 router (pf). http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/13/base/etc/sysctl.conf FreeBSD 13 desktop have no known problems with other websites. Only with one