On Thu, Nov 22, 2018 at 11:50:52AM -0500, Josh Grosse wrote:
> The page refers to vmx0 rather than vxlan0 in its pf.conf
> guidance.
>
Are you sure? In this example, vmx0 is the parent interface that
receives VXLAN UDP packets - it could also be em0, ix0, or whatever
you like.
Reyk
> Index: vxlan.4
> ===================================================================
> RCS file: /systems/cvs/src/share/man/man4/vxlan.4,v
> retrieving revision 1.7
> diff -u -p -r1.7 vxlan.4
> --- vxlan.4 22 Feb 2018 01:35:04 -0000 1.7
> +++ vxlan.4 22 Nov 2018 16:43:37 -0000
> @@ -123,9 +123,9 @@ endpoint policies in
> .Xr pf.conf 5 :
> .Bd -literal -offset indent
> table <vxlantep> { 192.168.1.200, 192.168.1.201 }
> -block in on vmx0
> -pass out on vmx0
> -pass in on vmx0 proto udp from <vxlantep> to port vxlan
> +block in on vxlan0
> +pass out on vxlan0
> +pass in on vxlan0 proto udp from <vxlantep> to port vxlan
> .Ed
> .Pp
> The Time-to-Live (TTL) value of the tunnel can be set to 1 or a low
>
