Hi,
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.
For example (w/ or w/o vlan(4) doesn't make a difference)
- pfsync0 in rdomain 5 (configured with syncdev vlan5 and syncpeer,
so no multicast traffic)
- vlan5 in rdomain 5
- lo5 in rdomain 5
- pf(4) is passing pfsync traffic
With tcpdump i only see packets on pfsync0
Sep 18 11:41:52.207074 PFSYNCv69 len 212
but nothing on vlan5.
Besides that, the kernel prints the following message every sec, so
it seems pfsync(4) is not rdomain aware anymore.
/bsd: vlan5: trying to send packet on wrong domain. if 5 vs. mbuf 0
I've tested with 7.3 and here it works.
Sep 18 11:56:19.142731 52:59:06:94:af:12 52:01:45:47:1c:34 0800 142:
192.168.5.1: PFSYNCv6 len 108 act UPD ST COMP count 1
...
(DF) [tos 0x10]
-Mark
--
Mark Patruck ( mark at wrapped.cx )
GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74 F644 0D3C F66F F286 5E51
https://www.wrapped.cx
