[Bug 283362] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283362

Ed Maste  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |DUPLICATE

--- Comment #3 from Ed Maste  ---


*** This bug has been marked as a duplicate of bug 283137 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 283362] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283362

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2831
   ||37

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 283363] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283363

Ed Maste  changed:

   What|Removed |Added

 Status|New |Closed
 CC||ema...@freebsd.org
 Resolution|--- |DUPLICATE

--- Comment #1 from Ed Maste  ---


*** This bug has been marked as a duplicate of bug 283362 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 283362] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283362

--- Comment #2 from Ed Maste  ---
*** Bug 283363 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 283363] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283363

Bug ID: 283363
   Summary: Frequent kernel crashes due to pf commit
   Product: Base System
   Version: 14.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: peter.b...@bsd4all.org
CC: k...@freebsd.org, n...@freebsd.org

For awhile my firewalls are crashing. Sometimes in pf code, sometimes in uma
code. Only two firewalls connected via carp seem to be having this problem. I
have narrowed it down to commit 93c80b79ad6564a17553fc1df41d57dc9da4cdec

Without this commit the problem does not occur. The passive firewall seems to
have this problem more often.

Running kernel and core files are available.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 283362] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283362

Franco Fichtner  changed:

   What|Removed |Added

 CC||fra...@opnsense.org

--- Comment #1 from Franco Fichtner  ---
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283137

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

--- Comment #31 from Vladislav Shabanov  ---
After switching to igb1 I see:
sudo sysctl -a | grep 'igb.*mgmt'
dev.igb.1.mac_stats.mgmt_pkts_txd: 0
dev.igb.1.mac_stats.mgmt_pkts_drop: 0
dev.igb.1.mac_stats.mgmt_pkts_recvd: 0
dev.igb.0.mac_stats.mgmt_pkts_txd: 0
dev.igb.0.mac_stats.mgmt_pkts_drop: 0
dev.igb.0.mac_stats.mgmt_pkts_recvd: 0

But the problem persists. Do you need fresh watchdog files?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 283362] Frequent kernel crashes due to pf commit

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283362

Bug ID: 283362
   Summary: Frequent kernel crashes due to pf commit
   Product: Base System
   Version: 14.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: peter.b...@bsd4all.org
CC: k...@freebsd.org, n...@freebsd.org

Created attachment 255895
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255895&action=edit
backtrace

For awhile my firewalls are crashing. Sometimes in pf code, sometimes in uma
code. Only two firewalls connected via carp seem to be having this problem. I
have narrowed it down to commit 93c80b79ad6564a17553fc1df41d57dc9da4cdec

Without this commit the problem does not occur. The passive firewall seems to
have this problem more often.

Running kernel and core files are available.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 272842] Missing WireGuard integration into the base system rc.d scripts

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272842

Patrick M. Hausen  changed:

   What|Removed |Added

 CC||p...@hausen.com

--- Comment #10 from Patrick M. Hausen  ---
Why not import net/wireguard-tools into base?

Been using it for years, first with the golang based implementation, then with
kernel based one.

All you need is:

wireguard_enable="YES"
wireguard_interfaces="wg0"

And then wg0.conf with interface and peer definitions. Routes are installed
automatically based on AllowedIPs settings.

What am I missing?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 272842] Missing WireGuard integration into the base system rc.d scripts

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272842

--- Comment #11 from Helge Oldach  ---
(In reply to Patrick M. Hausen from comment #10)
Little. :-)

IMHO importing net/wireguard-tools/files/wireguard_lite.in would cover most
functionality.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 272842] Missing WireGuard integration into the base system rc.d scripts

2024-12-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272842

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org,
   ||kev...@freebsd.org

--- Comment #12 from Warner Losh  ---
Add Kyle for his perspective.

-- 
You are receiving this mail because:
You are on the CC list for the bug.