Correction to previous message; should be:
> After your ideA re "no actual packets on lo2" I ran tcpdump on that
> interface; indeed no traffic shows up. I moved the jails to a new
> vlan1 ON WAN0 (INSTEAD OF LO0) with /24 subnet, with x.x.0.1 empty and
> jails starting from x.x.0.2/32. This obviously facilitates NAT from
> pf in that NAT is now not needed for inter-jail communication.
> However, nothing changes for the greater problem of packet tagging as
> "tcpdump -i vlan1" shows no packet traversal as was the case on lo2.
So now, jails are on a vlan hosted on wan0 (egress) but tcpdump still shows no
packet traversal on that interface. hardware driver is re :
wan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (100baseTX <full-duplex>)
--
FreeBSD_amd64_11-Stable_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
_______________________________________________
freebsd-pf@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-pf
To unsubscribe, send any mail to "freebsd-pf-unsubscr...@freebsd.org"
