[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 Kristof Provost changed: What|Removed |Added Status|New |Open Assignee|p...@fre

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #13 from Rumen Palov --- Created attachment 225147 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225147&action=edit Truss output of pfctl -ss , pfctl -sn , pfctl -sr, tar.bz2, 13M -- You are receiving this mail be

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #12 from Rumen Palov --- Hello Kristof, I have truss files for each type of pfctl execution. I attach them here. For experiment, we disable pf state nagios sensor and since then the server is stable. No one freeze / hang.

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #11 from Rumen Palov --- (In reply to Kristof Provost from comment #10) Sorry, I missed one part of the sentence: We do not have this error each time: DIOCGETRULE. -- You are receiving this mail because: You are the assignee

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #10 from Kristof Provost --- (In reply to Rumen Palov from comment #8) I don't understand where comment #1 came from then. When did that happen? -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #9 from Rumen Palov --- Created attachment 225125 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225125&action=edit Truss otput LAST 200K rows , 12 MB, bziped -- You are receiving this mail because: You are the assi

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #8 from Rumen Palov --- When the server is in the hang state, we can enter login username in system console, press enter and never receive password prompt. The machine is still having ICMP working, but we can not login to it v

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #7 from Kristof Provost --- (In reply to Rumen Palov from comment #6) Ah, I misunderstood your test setup. In that case the last few thousand lines might be more interesting. Depending on how the system stops working, of course.

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #6 from Rumen Palov --- The truss is running one perl script which execute pfctl -sr pfctl -sn pfctl -ss in endless loop until the Server Hangs, so yes the file is full with repeating content. This endless loop execution is

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #5 from Rumen Palov --- Created attachment 225124 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225124&action=edit Truss otput first 200l rows , 12 MB, bziped -- You are receiving this mail because: You are the ass

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #4 from Kristof Provost --- (In reply to Rumen Palov from comment #3) That's also odd, but possibly useful. A 16GB truss log is very unexpected, so I'd speculate that it's somehow ending up in an infinite loop. Can you post the

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 --- Comment #3 from Rumen Palov --- Hello Kristof , Yes we have memory monitoring. The amount of free RAM before server freeze is aroud 350MB from 16G total RAM. The swap is around 10-15MB usage. How do you recommend to execute truss

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #2

[Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org Keywords

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org Assig

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 --- Comment #7 from Tobias Brunner --- OK, that interface name is passed via RTA_IFP attribute to the kernel when installing the route. Maybe it doesn't like that the gateway (presumably) is not reachable via that interface, so it changes i

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 --- Comment #6 from Marek Zarychta --- You can try to increase net.route.algo.debug_level by changing this sysctl, but it might be dependent on kernel "options FIB_ALGO" which is enabled by default only in CURRENT. -- You are receiving th

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 --- Comment #5 from martin.larss...@gmail.com --- Mon, 2021-05-17, 15:58:12 07[KNL] adding policy 10.11.12.0/24 === 192.168.5.0/24 in Mon, 2021-05-17, 15:58:12 07[KNL] adding policy 192.168.5.0/24 === 10.11.12.0/24 out Mon, 2021-05-17, 15:58

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 --- Comment #4 from Tobias Brunner --- Please increase the log level for KNL to 2. Then check the log message starting with "installing route:". Does it list the correct (internal) interface? -- You are receiving this mail because: You ar

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 --- Comment #3 from martin.larss...@gmail.com --- I installed 13.0-STABLE kernel and /boot only which seemed to work. result is that I can see the route being added now and no errors. but regardless of settings in kernel-pfkey.conf it alway

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 255852] pf: set skip on: serious security hole

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255852 Kristof Provost changed: What|Removed |Added Status|New |Open Assignee|p...@fre

[Bug 255852] pf: set skip on: serious security hole

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255852 Kristof Provost changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 255852] pf: set skip on: serious security hole

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255852 Mark Linimon changed: What|Removed |Added CC||sect...@freebsd.org Assig

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 Marek Zarychta changed: What|Removed |Added CC||zarych...@plan-b.pwste.edu.

[Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678 Mark Linimon changed: What|Removed |Added Keywords||regression Assignee|b...@

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=b0b9525172ba9f8704f810d974f56d4ee3aad51f commit b0b9525172ba9f8704f810d974f56d4ee3aad51f Author:

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 --- Comment #6 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=e49799dcf14e7026f377d26a70fe0a3a3d15390a commit e49799dcf14e7026f377d26a70fe0a3a3d15390a Author:

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 255432] pf fragment reassembly leads to invalid IP checksum since 13.0-RELEASE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255432 Kristof Provost changed: What|Removed |Added Assignee|p...@freebsd.org |k...@freebsd.org S

[Bug 255432] pf fragment reassembly leads to invalid IP checksum since 13.0-RELEASE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255432 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 --- Comment #4 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=2aa21096c7349390f22aa5d06b373a575baed1b4 commit 2aa21096c7349390f22aa5d06b373a575baed1b4 Author:

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #3

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 --- Comment #2 from takahiro.kuros...@gmail.com --- (In reply to Kristof Provost from comment #1) Thanks for taking a look at the patch! I forgot to note that it was made against 12-STABLE. I'll port it to -current. The patch is indeed not

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 --- Comment #1 from Kristof Provost --- I need to read up on MAP-E before I can say much sensible, but on first glance this looks like a pretty solid patch. It appears to date from before the split-up of pf_pool / pf_kpool, but that's a mi

[Bug 254577] [PATCH] pf: Implement the NAT source port selection of MAP-E Customer Edge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254577 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 254171] 13.0-RC1: pf: vnet: jail leaves a unnecessary swi1 thread in intr process

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254171 Kristof Provost changed: What|Removed |Added Status|New |In Progress Assignee|p

[Bug 254171] 13.0-RC1: pf: vnet: jail leaves a unnecessary swi1 thread in intr process

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254171 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 253587] netisr: possible concurrency issues with net.isr.maxthreads > 1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253587 Kristof Provost changed: What|Removed |Added Assignee|p...@freebsd.org |n...@freebsd.org -- You are r

[Bug 253587] netisr: possible concurrency issues with net.isr.maxthreads > 1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253587 Kamigishi Rei changed: What|Removed |Added Summary|pf: page fault in |netisr: possible

[Bug 253587] pf: page fault in pf_pull_hdr

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253587 --- Comment #3 from Kamigishi Rei --- It does not seem like pf specifically is at fault here. Got two more faults over the past 12 hours and both were with mbufs being 0x0 in different code paths: Important note: net.isr.maxthreads: -1 n

[Bug 253587] pf: page fault in pf_pull_hdr

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253587 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 skele...@lissyara.su changed: What|Removed |Added Status|New |Closed Resolution|--

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #9 from Kristof Provost --- (In reply to skeletor from comment #8) Have you confirmed, with pflog, that the route-to rule is still getting hit? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #8 from skele...@lissyara.su --- Yes, from outside (some host in internet). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-pf@freebsd.org mailin

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #7 from Kristof Provost --- (In reply to skeletor from comment #6) Send packets from where? From the machine? From the internet? -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #6 from skele...@lissyara.su --- I expect, that, if I send packets to secondary (ext_if_2) interface (not to point default GW) I receive it from ext_if_2. But really I see it on ext_if_1 and don't see on ext_if_2 (but should see)

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #5 from Kristof Provost --- (In reply to skeletor from comment #4) Again: explain what happens and what you expect to have happen instead. I've looked at the 12.1 and 12.2 code and there are no obvious differences in the reply-

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #4 from skele...@lissyara.su --- ext_if_2="igb0" ext_if_1="bge0" int_if="vlan12" vlan1920_net="192.168.0.0/24" lo="lo0" int_net="10.11.12.0/24" gw_2="BB.BB.BB.YY" gw_1="AA.AA.AA.YY" # services tcp_svc="ssh, 53, 110,143,993,995

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #3 from Kristof Provost --- (In reply to skeletor from comment #2) Yes. (a) **FULL** rule sets (b) a description of what happens and what's supposed to happen. "It's broken" is not an actionable bug report. -- You are receiv

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 --- Comment #2 from skele...@lissyara.su --- pass in on $ext_if_1 reply-to ($ext_if_1 $gw_1) inet proto tcp to ($ext_if_1) port { $tcp_svc } tag EXT_IF_A pass in on $ext_if_1 inet proto tcp from ($ext_if_1:network) to ($ext_if_1) port { $tcp

[Bug 253164] reply-to in PF brokens after upgrade from 12.1 to 12.2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253164 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org Keywords

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 242044] pf can't load rules with newline at end.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242044 Kristof Provost changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 242044] pf can't load rules with newline at end.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242044 --- Comment #2 from sasamotik...@gmail.com --- Created attachment 209352 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209352&action=edit pf failed config Example of not working rules. -- You are receiving this mail because: Y

[Bug 242035] pf/pflog failed to load after 12.1-RELEASE upgrade.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242035 Bjoern A. Zeeb changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 242044] pf can't load rules with newline at end.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242044 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1

[Bug 242045] pf can't be unloaded if pflog loaded.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242045 Kristof Provost changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 242045] pf can't be unloaded if pflog loaded.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242045 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

[Bug 242044] pf can't load rules with newline at end.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242044 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

[Bug 242035] pf/pflog failed to load after 12.1-RELEASE upgrade.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242035 --- Comment #6 from sasamotik...@gmail.com --- (In reply to Bjoern A. Zeeb from comment #5) Yes, you're right pf can't be loaded along with ip_mroute and vice versa but in my custom kernel (minimal kernel without options which can be loaded

[Bug 242035] pf/pflog failed to load after 12.1-RELEASE upgrade.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242035 Bjoern A. Zeeb changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 242035] pf/pflog failed to load after 12.1-RELEASE upgrade.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242035 Bjoern A. Zeeb changed: What|Removed |Added Status|New |Open CC|

[Bug 242035] pf/pflog failed to load after 12.1-RELEASE upgrade.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242035 Mark Linimon changed: What|Removed |Added Keywords||regression Assignee|b...@

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 241563] pf: altq Adaptive RED (Random Early Detection) queuing support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241563 Mark Linimon changed: What|Removed |Added Assignee|n...@freebsd.org |p...@freebsd.org Keyword

[Bug 241563] pf: altq Adaptive RED (Random Early Detection) queuing support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241563 Archit Pandey changed: What|Removed |Added Version|12.0-RELEASE|CURRENT -- You are receiving this

[Bug 241563] pf: altq Adaptive RED (Random Early Detection) queuing support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241563 --- Comment #3 from Archit Pandey --- Hello Kubilay Kocak, Thanks for editing the bug as required. > If required, a patch against CURRENT would be appreciated as it will need to > land in head first I created the patch against FreeBSD g

[Bug 241563] pf: altq Adaptive RED (Random Early Detection) queuing support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241563 Kubilay Kocak changed: What|Removed |Added Keywords||needs-patch --- Comment #2 from Ku

[Bug 241563] pf: altq Adaptive RED (Random Early Detection) queuing support

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241563 Archit Pandey changed: What|Removed |Added CC||p...@freebsd.org -- You are recei

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 240819] PF scrub drop UDP Fragment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240819 fabrice.br...@orange.com changed: What|Removed |Added Status|New |Closed Resolutio

[Bug 240819] PF scrub drop UDP Fragment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240819 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #2

[Bug 240819] PF scrub drop UDP Fragment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240819 --- Comment #1 from Kristof Provost --- I think I've reproduced this, but I don't think it's a pf bug. The packet gets dropped and counted as a short packet because the UDP destination port is 0. That check has been there since 2004. The I

[Bug 240819] PF scrub drop UDP Fragment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240819 Olivier Cochard changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are rec

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 240532] pf stops purging IPv6 FIN_WAIT_2 states?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240532 Kristof Provost changed: What|Removed |Added Resolution|--- |Not A Bug Status|New

[Bug 240532] pf stops purging IPv6 FIN_WAIT_2 states?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240532 --- Comment #3 from Peter Eriksson --- I ran those tests you mention and some other stuff, and it looks like the "accumulation" was due to Linux (Ubuntu 18.04 for what it's worth) NFS clients bombarding our servers with new TCP connections

Problem reports for p...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

  1   2   3   4   5   6   7   8   9   10   >