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
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=92949
Josh Paetzel changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=82271
Josh Paetzel changed:
What|Removed |Added
CC|
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
Damjan Jovanovic changed:
What|Removed |Added
Attachment #183512|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
--- Comment #8 from Kristof Provost ---
Thanks. I'll start testing this patch.
Can you also take a look at the style(9) remarks in the review
(https://reviews.freebsd.org/D11137)?
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
Damjan Jovanovic changed:
What|Removed |Added
Attachment #183243|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
--- Comment #6 from Kristof Provost ---
With this patch my gateway box (pf and vimage jails) panics pretty quickly
during boot.
#0 doadump (textdump=0) at pcpu.h:232
#1 0x803a4c2b in db_dump (dummy=, dummy2=,
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
--- Comment #5 from Damjan Jovanovic ---
Thank you.
I've developed a patch for the same feature in LibAlias (tested with IPFW but
presumably applies to natd/pppd too) on bug 219918, which you might want to
look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
Damjan Jovanovic changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
--- Comment #4 from Kristof Provost ---
I've created a phabricator entry for this https://reviews.freebsd.org/D11137 ,
because that makes reviewing easier.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
--- Comment #3 from Kristof Provost ---
I see. I think that makes sense, but I'll need a bit of time to review this.
It probably wouldn't hurt if you could explain this on freebsd-pf@ so others
can take a look too.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219803
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
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
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
Robert Schulze changed:
What|Removed |Added
Resolution|--- |FIXED
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
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122773
Jan Beich changed:
What|Removed |Added
Attachment #86358|text/x-diff;|text/plain
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #17 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat Apr 8 09:49:21 UTC 2017
New revision: 316641
URL: https://svnweb.freebsd.org/changeset/base/316641
Log:
MFC r316355
pf: Fix leak of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #16 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat Apr 8 09:48:21 UTC 2017
New revision: 316640
URL: https://svnweb.freebsd.org/changeset/base/316640
Log:
MFC r316355
pf: Fix leak of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #15 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat Apr 1 12:22:34 UTC 2017
New revision: 316355
URL: https://svnweb.freebsd.org/changeset/base/316355
Log:
pf: Fix leak of pf_state_keys
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #14 from Max ---
--- sys/netpfil/pf/pf.c.orig2017-03-30 09:54:22.05649 +
+++ sys/netpfil/pf/pf.c 2017-03-30 09:55:10.735221000 +
@@ -3508,7 +3508,7 @@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #13 from Robert Schulze ---
By the way: could someone please attach a patch based on the assumptions you
made?
regards,
Robert Schulze
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #12 from Robert Schulze ---
Since the affected machine is critical and cannot be rebooted without care, I
cannot confirm the fix right now. My primary intention was to report the
misbehaviour.
If a planned
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #11 from Max ---
(In reply to Kristof Provost from comment #10)
I've done basic tests. It works. I can post some counters here. Perhaps we
should test it without rdr/nat rule.
By the way, "pfctl -Fi"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
Robert Schulze changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #9 from Max ---
It seems that I'm right. The problem has gone. Hope that someone more
experienced will review this fix.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #8 from Max ---
I think the problem is in pf_create_state():
/* check maximums */
if (r->max_states &&
(counter_u64_fetch(r->states_cur) >= r->max_states)) {
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #7 from Max ---
A bit more info...
Before reaching the limit:
Status: Enabled for 0 days 04:08:59 Debug: Urgent
State Table Total Rate
current entries
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #6 from Robert Schulze ---
(In reply to Max from comment #5)
Thank you for your efforts.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #5 from Max ---
Well, I can reproduce the problem.
I have 3 hosts with 10.3 release (generic kernel). "Server", "client" and
"firewall".
Complete pf.conf of "firewall" host:
set skip on {lo, em2}
table
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #3 from Max ---
(In reply to Robert Schulze from comment #2)
I'm unable to reproduce the described behaviour on 10.3 release with generic
kernel and your rules. It works just fine. Maybe the problem is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
--- Comment #2 from Robert Schulze ---
There are no pf-related kernel messages.
# pfctl -st | grep src.track
src.track 0s
So source tracking entries should expire, as soon there are no more
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
Max changed:
What|Removed |Added
CC||maxi...@als.nnov.ru
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217997
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203735
Kristof Provost changed:
What|Removed |Added
CC|
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185633
Kristof Provost changed:
What|Removed |Added
Resolution|--- |FIXED
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
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
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
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
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215041
Max changed:
What|Removed |Added
CC||maxi...@als.nnov.ru
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215041
--- Comment #5 from b...@ddh.de1.cc ---
(In reply to Kristof Provost from comment #4)
Sorry, nothing related to networking there
--
You are receiving this mail because:
You are the assignee for the bug.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215716
Kristof Provost changed:
What|Removed |Added
Assignee|freebsd-pf@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215716
--- Comment #3 from Kristof Provost ---
Created attachment 178681
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178681=edit
Remove bogus checks
I'm very confused by these checks. The RMCF_* flags they check
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215716
Kristof Provost changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215716
Kristof Provost changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215716
Hiren Panchasara changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215041
--- Comment #4 from Kristof Provost ---
That would suggest that the state tracking is involved in the problem.
Unfortunately I've had no luck reproducing this. Do you have any unusual
sysctl's set?
--
You are receiving
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213736
--- Comment #1 from Franco Fichtner ---
Review available at https://reviews.freebsd.org/D8877
--
You are receiving this mail because:
You are the assignee for the bug.
___
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215041
--- Comment #3 from b...@ddh.de1.cc ---
Update: The problem seems to center on the line "pass [log] all". When I
comment out the line and do "pfctl -F all -f configfile", the handshake to
185.60.115.40:443 works. Comment it in again,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211730
--- Comment #12 from ncrog...@gmail.com ---
I ran into this same problem myself today on a 10G ixgbe(4) interface running
10.1-RELEASE... Did anyone manage to get a working patch going? Looks like
activity towards a resolution has died off.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215041
--- Comment #2 from b...@ddh.de1.cc ---
(In reply to Kristof Provost from comment #1)
Correct, it's just working as a MAC-level bridge.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215041
Kristof Provost changed:
What|Removed |Added
CC|
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196314
--- Comment #6 from kri...@cflinux.hu ---
Created attachment 177689
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=177689=edit
more appropriate patch
This patch removes dead code also.
--
You are receiving this mail because:
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212384
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Not A Bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212384
--- Comment #2 from patf...@davenulle.org ---
Hello,
We have tracked down this problem to a misworking fiber on the pfsync physical
link.
So I think we can close this PR.
Sorry for the noise, best regards.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212115
shriyogeshchan...@gmail.com changed:
What|Removed |Added
CC|
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214613
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196314
--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Thu Nov 10 18:41:44 UTC 2016
New revision: 308486
URL: https://svnweb.freebsd.org/changeset/base/308486
Log:
pfctl: fix nested inline anchors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196314
--- Comment #4 from Martin Beran ---
(In reply to Kristof Provost from comment #3)
This pf.conf should block ping 127.0.0.1, but it does not:
anchor on ! vboxnet0 {
anchor on ! vboxnet1 {
block on lo0
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209475
fehmi noyan isi changed:
What|Removed |Added
Attachment #170810|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210860
--- Comment #5 from Kristof Provost ---
I've not had the time to look at this yet. It's on my list, but I can't promise
when I'll have the time.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210860
--- Comment #4 from Joao Vieira ---
Still present on 11.0-RELEASE-p1.
Were you able to reproduce it?
--
You are receiving this mail because:
You are the assignee for the bug.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212384
--- Comment #1 from patf...@davenulle.org ---
Hello,
My firewalls are now in production and it appears that with a lot of states
(~600 000 here). The pfsync bulk works fine just using /etc/rc.d/pfsync.
So there is something wrong when the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213736
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163208
kuPyxa changed:
What|Removed |Added
CC||ki...@varnakov.net
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185633
--- Comment #17 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sun Oct 2 21:11:25 UTC 2016
New revision: 306594
URL: https://svnweb.freebsd.org/changeset/base/306594
Log:
MFC r306289:
bridge: Fix
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185633
--- Comment #16 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sun Oct 2 21:06:55 UTC 2016
New revision: 306593
URL: https://svnweb.freebsd.org/changeset/base/306593
Log:
MFC r306289:
bridge: Fix
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185633
--- Comment #15 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat Sep 24 07:09:43 UTC 2016
New revision: 306289
URL: https://svnweb.freebsd.org/changeset/base/306289
Log:
bridge: Fix fragment handling
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212873
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
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
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
501 - 600 of 887 matches
Mail list logo