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
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=237973
Kristof Provost changed:
What|Removed |Added
Assignee|k...@freebsd.org |p...@freebsd.org
--- Comment
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
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=196087
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Overcome By Events
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=230619
--- Comment #10 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Fri Mar 29 14:34:52 UTC 2019
New revision: 345692
URL: https://svnweb.freebsd.org/changeset/base/345692
Log:
MFC r345177:
pf :Use
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230619
--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Fri Mar 29 14:34:51 UTC 2019
New revision: 345691
URL: https://svnweb.freebsd.org/changeset/base/345691
Log:
MFC r345177:
pf :Use
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236829
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
--
You are
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=196087
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
Benedict Reuschling changed:
What|Removed |Added
Status|In Progress |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bcr
Date: Fri Mar 22 06:02:07 UTC 2019
New revision: 345404
URL: https://svnweb.freebsd.org/changeset/base/345404
Log:
MFC r345080:
Extend
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=226411
--- Comment #10 from Kristof Provost ---
Sadly not. This bug is actually still on my todo list, so I haven't forgotten
about it yet, but it's some way down the list right now.
If you're friend is very motivated a test case we can plug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226411
Shawn Webb changed:
What|Removed |Added
CC||shawn.w...@hardenedbsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230619
--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Fri Mar 15 11:08:45 UTC 2019
New revision: 345177
URL: https://svnweb.freebsd.org/changeset/base/345177
Log:
pf :Use counter(9) in pf tables.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
--- Comment #10 from Benedict Reuschling ---
Patch committed to head, waiting until the MFC has happened before closing this
PR.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bcr
Date: Tue Mar 12 20:08:38 UTC 2019
New revision: 345080
URL: https://svnweb.freebsd.org/changeset/base/345080
Log:
Extend descriptions and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230619
Kristof Provost changed:
What|Removed |Added
Status|New |In Progress
--- Comment #7 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
Kubilay Kocak changed:
What|Removed |Added
Keywords|needs-qa|
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=231977
--- Comment #4 from Kristof Provost ---
(In reply to Benedict Reuschling from comment #2)
Good question, but I don't really have a strong opinion.
ipfw has a default configuration in /etc/rc.firewall, but ipf doesn't.
We could certainly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
--- Comment #7 from Benedict Reuschling ---
I've opened a review on Phabricator to discuss the outstanding file changes
here: https://reviews.freebsd.org/D19530
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
--- Comment #5 from Benedict Reuschling ---
OK, I also think that changing the handbook text is easier. I've changed the
sentence to mention that there is not default /etc/pf.conf ruleset and point
people to the /usr/share/examples/pf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bcr
Date: Sun Mar 10 15:22:55 UTC 2019
New revision: 52854
URL: https://svnweb.freebsd.org/changeset/doc/52854
Log:
Mention that FreeBSD does not ship
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
bc...@lafn.org changed:
What|Removed |Added
CC||bc...@lafn.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231977
Benedict Reuschling changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201695
--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat Mar 9 10:33:47 UTC 2019
New revision: 344965
URL: https://svnweb.freebsd.org/changeset/base/344965
Log:
MFC r339836, r340286, r341358:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183198
Kristof Provost changed:
What|Removed |Added
CC||a.kraso...@yahoo.com
---
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 #8 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat Mar 2 12:30:59 UTC 2019
New revision: 344720
URL: https://svnweb.freebsd.org/changeset/base/344720
Log:
pf tests: Test for nested inline
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=229092
--- Comment #21 from Kristof Provost ---
(In reply to Kajetan Staszkiewicz from comment #20)
You are of course correct here.
I'd like to try to write a test case for this. Do you have any suggestions on
how to best reproduce (as simple a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #20 from Kajetan Staszkiewicz ---
'rt' contains values from enum { PF_NOPFROUTE, PF_FASTROUTE, PF_ROUTETO,
PF_DUPTO, PF_REPLYTO }. I don't see how those could be squashed into a single
flag, as they dictate differenct actions
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=203715
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Overcome By Events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208140
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Overcome By Events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209259
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Overcome By Events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212873
Kristof Provost changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223093
Kristof Provost changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #19 from Kristof Provost ---
There's a typo in the KASSERT (r_dir = PF_IN).
I wonder if 'rt' can't be a flag. That'd give us more room for other extensions
later.
--
You are receiving this mail because:
You are the assignee
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=229092
--- Comment #18 from Kajetan Staszkiewicz ---
My 2nd patch stores missing state->rt information in currently unused part of
struct pfsync_state. That should make it compatible. A router running
non-patched kernel will simply not transmit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #17 from Kristof Provost ---
Right, for 3. we come back to the compatibility issue. pfsync has to remain
able to run with different versions, so while we could potentially extend the
protocol to include this information we
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #16 from Kajetan Staszkiewicz ---
(In reply to Kristof Provost from comment #15)
> (In reply to Kajetan Staszkiewicz from comment #13)
>
>> - Any rule using interface IP addresses in unnamed table {} will end up
>> being
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #15 from Kristof Provost ---
(In reply to Kajetan Staszkiewicz from comment #13)
> - Any rule using interface IP addresses in unnamed table {} will end up being
> different on 2 routers unless named {} is used.
Ah, because
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #14 from Kajetan Staszkiewicz ---
To sum it up: I don't think it is feasible to have any functionality depending
on ruleset being identical. It is really hard to achieve it and it might not
be worth the effort.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #13 from Kajetan Staszkiewicz ---
(In reply to Kristof Provost from comment #12)
pfcksum only checks if loaded rules are the same, it does not ensure rules are
the same on 2 routers. There are a few ways to have different
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
--- Comment #12 from Kristof Provost ---
(In reply to Kajetan Staszkiewicz from comment #11)
Wouldn't the pfcksum protect us from having different rules in the first place?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229092
Kajetan Staszkiewicz changed:
What|Removed |Added
Attachment #194342|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Tue Jan 22 01:07:20 UTC 2019
New revision: 343290
URL: https://svnweb.freebsd.org/changeset/base/343290
Log:
MFC r343041
pf: silence a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Tue Jan 22 01:07:19 UTC 2019
New revision: 343289
URL: https://svnweb.freebsd.org/changeset/base/343289
Log:
MFC r343041
pf: silence a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
Kristof Provost changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211796
--- Comment #7 from Oleksandr Tymoshenko ---
There is a commit referencing this PR, but it's still not closed and has been
inactive for some time. Closing the PR as fixed but feel free to re-open it if
the issue hasn't been completely
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211796
Oleksandr Tymoshenko changed:
What|Removed |Added
Status|New |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209475
Oleksandr Tymoshenko changed:
What|Removed |Added
Status|New |Closed
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=122773
--- Comment #9 from Kristof Provost ---
Note that while we do log the uid we don’t log the pid. Offhand I think that
that was a nontrivial bit of extra work.
I have no immediate plans to implement that, so I’m okay with keeping this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230619
--- Comment #6 from Kajetan Staszkiewicz ---
I totally forgot about this patch too :) I'll fix the memory allocation flag
and run it in testing environment and come back to you in a few days.
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230619
--- Comment #5 from Kristof Provost ---
Apologies for taking this long to get back to this. I've had other priorities
in the past few months.
I'm not sure about the M_WAITOK in pfr_create_kentry(), because the initial
allocation there
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Tue Jan 15 08:59:52 UTC 2019
New revision: 343041
URL: https://svnweb.freebsd.org/changeset/base/343041
Log:
pf: silence a runtime warning
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
--- Comment #3 from rozhuk...@gmail.com ---
(In reply to Kristof Provost from comment #1)
All info in private email, if you need more - I will send.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
--- Comment #2 from rozhuk...@gmail.com ---
if ((ke == NULL || ke->pfrke_not) != notrule) {
if (op_pass != PFR_OP_PASS)
printf("pfr_update_stats: assertion failed.\n");
op_pass
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=234874
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
--
You are
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=233581
--- Comment #12 from peos42 ---
Hi Kristof
This is small :)
However... To try to give you something smaller I started by removing the
pass in quick on lo0 inet proto tcp from 1.2.3.4 to 1.2.3.4 port 953 flags
S/SAFR keep state
from the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #11 from Kristof Provost ---
(In reply to peos42 from comment #10)
Yes, there have been changes around set skip handling (mostly for groups). See
comment #1.
Do you have a smaller test case?
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #10 from peos42 ---
Have not tested on head. Is something fixed regarding this?
Config posted below as requested. Note that IPv4 and IPv6 addresses are
substituted to fake.
###
### FROM MAIN HOST
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #9 from Kristof Provost ---
(In reply to peos42 from comment #8)
Please include full pf.conf, ifconfig output and command line.
Have you tested this on head as well?
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #8 from peos42 ---
I have now tested on my primary firewall that is OpenBSD 6.4.
There I have "set skip on lo0". And I can in the firewall ping with the source
IP of one of my interfaces and the target IP the set to the same.
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=233581
--- Comment #7 from peos42 ---
I added this --ONLY-- to get it working...
pass in quick on lo0 inet proto tcp from 1.2.3.4 to 1.2.3.4 port 953 flags
S/SAFR keep state
That is...
Pass *IN* on lo0 and *NOT* vtnet0
So please explain your
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #6 from Kristof Provost ---
Your packet goes out lo0 and in vtnet0. So without the pass rule it’s blocked.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #5 from peos42 ---
Seems I cannot edit previous post. So here is an addition..
You say..
--snip--
but your block all rule is stopping it from being accepted on *vtnet0*, where
your IP address is assigned. You do need the rule
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233581
--- Comment #4 from peos42 ---
Hmmm
>From man page regarding "set skip"
--snip--
List interfaces for which packets should not be filtered. Packets
passing in or out on such interfaces are passed as if pf was
101 - 200 of 887 matches
Mail list logo