On 2023-09-18, Mark Patruck <m...@wrapped.cx> wrote:
> i've already wrote to dlg@, but also want to know if others see
> the same behavior or at least inform about it.
>
> pfsync(4) in combination with rdomain(4) doesn't work anymore on
> a fresh -current. I see packets on pfsync0, but nothing leaves
> the machine, so no states are synchronised.
pfsync had a big rewrite between 7.3 and -current. Setting rtableid
in the packet header was present in the 7.3 version but dropped in the
rewrite; can you try this?
Index: if_pfsync.c
===================================================================
RCS file: /cvs/src/sys/net/if_pfsync.c,v
retrieving revision 1.321
diff -u -p -r1.321 if_pfsync.c
--- if_pfsync.c 16 Sep 2023 09:33:27 -0000 1.321
+++ if_pfsync.c 18 Sep 2023 18:59:14 -0000
@@ -1537,6 +1537,7 @@ pfsync_sendout(struct pfsync_softc *sc,
imo.imo_ifidx = sc->sc_sync_ifidx;
imo.imo_ttl = PFSYNC_DFLTTL;
imo.imo_loop = 0;
+ m->m_pkthdr.ph_rtableid = sc->sc_if.if_rdomain;
if (ip_output(m, NULL, NULL, IP_RAWOUTPUT, &imo, NULL, 0) == 0) {
counters_pkt(sc->sc_if.if_counters, ifc_opackets,
