https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256393
--- Comment #33 from Eugene Grosbein ---
(In reply to Alexander V. Chernikov from comment #11)
It seems the problem is same as in my old PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129
The problem was fixed back in 2017 with
Hello,
So I have a very basic ruleset, as described in the FreeBSD handbook, see
below. I have "blurred" my open ports as seen in the ruleset below.
Igc0 is my WAN port and in the table "trusted_if" are like my LAN if and
some bridges.
1 reass ip from any to any in
00010 allow ip from any to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282434
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282434
--- Comment #2 from Lexi Winter ---
Created attachment 254891
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254891&action=edit
'sysctl debug.witness' output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #18 from Vladislav Shabanov ---
(In reply to Kevin Bowling from comment #17)
The problem persistis. The server still works, now on FreeBSD 14.1. BIOS
upgrade does not solve the issue. The network hungs every day, from 1 to 10
ti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Jose Luis Duran changed:
What|Removed |Added
Assignee|n...@freebsd.org |jldu...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #17 from Kevin Bowling ---
Were you able to do any of the above? A dump from a recent version where I
have added the nvm prints would be helpful to me.
I would like to make some progress or close this out. I don't doubt you'v
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
