[Bug 279830] Using AMD EPYC 9374F 32-Core Processor, PF driver gives error when loading for more than 62 VFs

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279830 --- Comment #3 from vdu...@maxlinear.com --- Hi Santiago, Thanks for the response. I had added more verbose logging for my device. When num_vfs=62. Below is the log: dre_drv0: DRE_drvIovInit: Called with num_vfs 62. pcib15: allocated memor

[Bug 279899] pf_unlink_state mutex unlock page fault panic

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899 --- Comment #5 from Kristof Provost --- (In reply to Daniel Ponte from comment #4) In comment #2 you stated there's no pfsync, yet this panic is in pfsync. It's very hard to debug things if you're not supplying the requested information. I

[Bug 279899] pf_unlink_state mutex unlock page fault panic

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899 Franco Fichtner changed: What|Removed |Added CC||fra...@opnsense.org --- Comment

[Bug 279899] pf_unlink_state mutex unlock page fault panic

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899 --- Comment #7 from Daniel Ponte --- The diff against upstream is a patch to make rtadvd(8) deprecate addresses on shutdown. It has nothing to do with this crash. I am not trying to be difficult, but my ruleset is 327 lines long and I will

[Bug 279899] pf_unlink_state mutex unlock page fault panic

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899 --- Comment #8 from Daniel Ponte --- And yes, pfsync is present in the kernel, but is not being used at all. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 279899] pf_unlink_state mutex unlock page fault panic

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899 --- Comment #9 from Daniel Ponte --- Removing pfsync from the kernel config has resolved this crash. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 279899] pf_unlink_state mutex unlock page fault panic

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899 --- Comment #10 from Zhenlei Huang --- (In reply to Kristof Provost from comment #5) > (In reply to Daniel Ponte from comment #4) > In comment #2 you stated there's no pfsync, yet this panic is in pfsync. `vnet_pfsync_init()` vnet sysinit

[Bug 273198] [14.0 CURRENT] PF recognizes encrypted IPSec traffic as coming from WAN. | NAT with IPsec Phase 2 Networks

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273198 --- Comment #2 from Igor Ostapenko --- (In reply to cArleone from comment #1) I've applied the initial analysis of the case. I've managed to test it using jails and vnet. From my testing both if_enc and pf work as expected, i.e. I can catc

[Bug 273198] [14.0 CURRENT] PF recognizes encrypted IPSec traffic as coming from WAN. | NAT with IPsec Phase 2 Networks

2024-06-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273198 --- Comment #3 from Igor Ostapenko --- Created attachment 251676 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251676&action=edit /usr/tests/sys/netpfil/pf/ipsec -- You are receiving this mail because: You are the assignee for