https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272416
--- Comment #12 from Mithun ---
(In reply to Jonathan Vasquez from comment #11)
Hi Jonathan,
Thanks for your response!. Unfortunately, I don't have a spare slot to switch
NICs, so I'll continue looking for a solution with the if_re module
There seems to be an open bug describing similar issue:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272944
On Thu, 12 Sep 2024 13:25:32 -0400
Paul Procacci wrote:
> You need to define `poor'.
> You need to show `top -SH` while the `problem' occurs.
>
> My guess is packets are getting shuttled between a global taskqueue thread.
> This is the default, or at least I'm not aware of this default being
> c
On 12/09/2024 19:16, Sad Clouds wrote:
Hi, I'm using FreeBSD-14.1 and on this particular system I only have a
single physical network interface, so I followed instructions for
networking vnet jails via epair and bridge, e.g.
devel
{
vnet;
vnet.interface = "e0b_devel";
On Thu, Sep 12, 2024 at 1:16 PM Sad Clouds
wrote:
> Hi, I'm using FreeBSD-14.1 and on this particular system I only have a
> single physical network interface, so I followed instructions for
> networking vnet jails via epair and bridge, e.g.
>
> devel
> {
> vnet;
> vnet.interface
Hi, I'm using FreeBSD-14.1 and on this particular system I only have a
single physical network interface, so I followed instructions for
networking vnet jails via epair and bridge, e.g.
devel
{
vnet;
vnet.interface = "e0b_devel";
exec.prestart += "/jails/jib addm devel gene
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280036
Kristof Provost changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280036
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=8f251937850142748cdf67a46630342934ff9f91
commit 8f251937850142748cdf67a46630342934ff9f91
Author
On 12 Sep 2024, at 00:57, Vadim Goncharov wrote:
>
> This is just not true. See, for example, FreeBSD-SA-17:06.openssh for
> vulnerability disabled by default, and workaround proposed to return
> to default (disabled) state.
No, this was changing from one supported expected-secure setting to ano
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272416
Mithun changed:
What|Removed |Added
CC||kbmithunchakravarthy@gmail.
10 matches
Mail list logo
