Re: TCP connection ignore RST

> On 7 Sep 2021, at 04:11, Rozhuk Ivan wrote: > > On Sat, 4 Sep 2021 13:19:52 +0200 > Michael Tuexen wrote: > On 4. Sep 2021, at 01:37, Rozhuk Ivan wrote: >>> >>> Hi! >>> >>> >>> I have strange case: FreeBSD 12.2 ignore TCP RST from windows host >>> and continue retransmitting packe

Re: NFS Mount Hangs

fs.nfsd.request_space_throttle_count vfs.nfsd.request_space_throttle_count: 0 I see that you are testing a patch and I look forward to seeing the results. Jason Breitman On Mar 21, 2021, at 6:21 PM, Rick Macklem mailto:rmack...@uoguelph.ca>> wrote: Youssef GHORBAL mailto:youssef.ghor...@pasteur.fr>>

Re: NFS Mount Hangs

> On 21 Mar 2021, at 23:21, Rick Macklem wrote: > > Youssef GHORBAL wrote: >> Hi Jason, >> >>> On 17 Mar 2021, at 18:17, Jason Breitman >>> wrote: >>> >>> Please review the details below and let me know if there is a setting that

Re: NFS Mount Hangs

result=$? >if [ ${result} -ne 0 ] ; then >/usr/bin/logger -s -i -p local7.notice -t ${progName} "NFS > Connection is OK." >/usr/bin/logger -s -i -p local7.error -t ${progName} "Disabling > firewall to allow access to ${nfs_ip}!"

Re: NFS Mount Hangs

Hi Jason, > On 17 Mar 2021, at 18:17, Jason Breitman > wrote: > > Please review the details below and let me know if there is a setting that I > should apply to my FreeBSD NFS Server or if there is a bug fix that I can > apply to resolve my issue. > I shared this information with the linux-nf

Re: DUP ACKs sent with no reason

On 28 Dec 2018, at 07:37, Muenz, Michael mailto:m.mu...@spam-fetish.org>> wrote: Am 27.12.2018 um 19:32 schrieb Youssef GHORBAL: What can explain those DUP ACKs sent by the FreeBSD host? (DUP ACKs sent by the client are "normal" in a way to report missing packet loss and

DUP ACKs sent with no reason

those sent by the BSD stack are hard to explain) How can I push the investigation further ? Youssef Ghorbal [1] client side pcap : https://cp.sync.com/dl/44f5d34b0#h8bb5gda-frp78vyt-yapws5gx-kidhq4mb [2] server side pcap : https://cp.sync.com/dl/32367

Re: Sporadic TCP/RST sent to client

[...] > Further, I would argue that round robin is not a valid 802.3ad/802.1AX > algorithm, per how it defines a frame distributor: > > "This standard does not mandate any particular distribution > algorithm(s); however, any distribution algorithm shall ensure that, > when frames are received by

Re: Sporadic TCP/RST sent to client

> On 27 Jun 2017, at 12:54, sth...@nethelp.no wrote: > >> Imagine this set up : >> >> freebsd host port0 <-> switch 1 <-> linux host port0 >> freebsd host port1 <-> switch 2 <-> linux host port1 >> >> On the linux box, port 0&1 are enslaved in a bond with a RR algorithm (Round >> Robin) >> On

Re: Sporadic TCP/RST sent to client

be split across the two lagg interfaces? > > Matt > > On Mon, Jun 26, 2017 at 1:35 PM, Navdeep Parhar wrote: >> On Thu, Jun 22, 2017 at 3:57 PM, Youssef GHORBAL >> wrote: >>> Hello, >>> >>>I'm having an issue with a FreeBSD 11 b

Re: Sporadic TCP/RST sent to client

int of the view of the lagg interface itself, packets arrive ordred and I expect the system to handle it correctly. The fact is that it is actually handled correctly in most cases but not when packets are really "close" (under 10 microseconds) Maybe the default sysctl settings are not meant

Sporadic TCP/RST sent to client

expected behaviour in this scenario on the netisr side ? How can I push the investigation further ? Youssef Ghorbal ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"