https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272124
Graham Perrin changed:
What|Removed |Added
Keywords|needs-patch |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272117
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272117
Graham Perrin changed:
What|Removed |Added
CC||bsd...@freebsd.org,
bob prohaska wrote:
> I can't detect any consistent pattern. For a while I thought load on the
> sshd-host end made a difference, but the latest disconnect was on an idle
> system with serial console output the only traffic on the dropped connection.
Could it be that the serial connection is
> On 21. Jun 2023, at 20:03, bob prohaska wrote:
>
> On Wed, Jun 21, 2023 at 10:45:25AM -0700, Mark Millard wrote:
>>> On Jun 21, 2023, at 10:24, bob prohaska wrote:
>>>
>>> I've got a Pi4 running -current that seems to selectively drop ssh
>>> connections.
>>
>> Only when the ssh has
On Wed, 21 Jun 2023, bob prohaska wrote:
I've got a Pi4 running -current that seems to selectively drop ssh connections.
There don't seem to be any error messages on the console at all, the client
I don't know what is the current way to do this, but maybe you could try to
sniff tty and see
>
> There don't seem to be any error messages on the console at all, the
> client
> session simply reports
> client_loop: send disconnect: Broken pipe
>
Have you tried SSH keepalive?
https://stackoverflow.com/questions/25084288/keep-ssh-session-alive
Best Regards,
Cheng Cui
On Wed, Jun 21,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272089
Kyle Evans changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271991
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272119
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272089
--- Comment #2 from Kyle Evans ---
the free_crypto label in there is actually wrong anyways, if cookie_init()
failed we don't set `ret` to a failure so MOD_LOAD will succeed even though
things are partially borked.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272089
Kyle Evans changed:
What|Removed |Added
CC||ema...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272117
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272090
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272089
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are
On Wed, Jun 21, 2023 at 10:45:25AM -0700, Mark Millard wrote:
> On Jun 21, 2023, at 10:24, bob prohaska wrote:
>
> > I've got a Pi4 running -current that seems to selectively drop ssh
> > connections.
>
> Only when the ssh has text streaming over it? Even when it
> is idle? Any other types of
On Jun 21, 2023, at 10:24, bob prohaska wrote:
> I've got a Pi4 running -current that seems to selectively drop ssh
> connections.
Only when the ssh has text streaming over it? Even when it
is idle? Any other types of context differences that lead
to observable differences of some type related
I've got a Pi4 running -current that seems to selectively drop ssh connections.
Connections running a shell seem to stay up, but a session running tip to a
usb-serial adapter (FTDI TTL232R-3V3) seems go away within a few hours.
There don't seem to be any error messages on the console at all, the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
NL changed:
What|Removed |Added
CC||noslin...@gmail.com
--- Comment #35 from NL
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272094
Franco Fichtner changed:
What|Removed |Added
CC||fra...@opnsense.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272094
--- Comment #5 from Gleb Smirnoff ---
(In reply to Alfa from comment #3)
> Sorry to bother but i am confused about PFILCTL tool, to make it clear What
> is this tool's main purpose?
To change how firewalls are hooked into the network
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272094
--- Comment #4 from Kristof Provost ---
(In reply to Alfa from comment #3)
> I am also using ip_divert with ipfw because PF divert-to not works as
> expected #260867 this bug references divert-to infinite loop problem this bug
> still
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272094
--- Comment #3 from Alfa ---
(In reply to Kristof Provost from comment #1)
"you can use dummynet with pf, and can also do basic layer 2 filtering with pf.
No doubt it's also possible to implement captive portal entirely with ipfw."
I am
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272124
--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=133b132bc1b612abe591c8f54680c3da8491e194
commit 133b132bc1b612abe591c8f54680c3da8491e194
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272124
--- Comment #1 from Michael Tuexen ---
The SCTP_DELAYED_ACK_TIME socket option was replaced by the SCTP_DELAYED_SACK
in the socket API specification in draft-ietf-tsvwg-sctpsocket-14. base r170056
changed the code, but missed updating the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272124
Michael Tuexen changed:
What|Removed |Added
Assignee|n...@freebsd.org |tue...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272124
Graham Perrin changed:
What|Removed |Added
CC||n...@freebsd.org
Graham Perrin has asked freebsd-net (Nobody)
for maintainer-feedback:
Bug 272124: The socket option "SCTP_DELAYED_ACK_TIME" is not available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272124
28 matches
Mail list logo
