Re: FreeBSD 12.2 reply-to doesn't work

2021-02-01 Thread skeletor
29.01.2021 20:10, Kajetan Staszkiewicz пишет: On 27.01.21 14:24, skeletor wrote: Hello. After upgrading FreeBSD from 12.1 to 12.2 "reply-to" stopped working. I have the same on 2 different machines. Both of them had working "reply-to" on 12.1 and stopped working after upgrading to 12.2 Packets

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

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

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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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

2021-02-01 Thread bugzilla-noreply
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.