Date: Sun, 14 Feb 2021 13:34:37 +0000 From: bugzilla-noreply@freebsd.org To: ipfw@FreeBSD.org Subject: [Bug 253476] ipfw keepalive: tcp_do_segment: Timestamp missing, segment silently dropped Message-ID: <bug-253476-8303-NPfUih2oq7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253476-8303@https.bugs.freebsd.org/bugzilla/> References: <bug-253476-8303@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253476 --- Comment #5 from Michael Tuexen <tuexen@freebsd.org> --- (In reply to Helge Oldach from comment #4) This middlebox code lets an RFC compliant end-point look like an endpoint violating the specification. So if the peer wants to talk to a broken end-point, the peer can set the corresponding sysctl. So I don't see a valu= e in making the configuration more complex. I also haven't thought about the consequence of a firewall pretending that = an end point is still alive, although it might not be. Personally, I wouldn't expect a middlebox inserting packets in a communicat= ion, which break the specification, but instead would like them to filter out communications which break the specifications. But that is a personal opini= on. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253476-8303-NPfUih2oq7>