From 13728aec15d184f4a25f78e50481a4f33357a12a Mon Sep 17 00:00:00 2001 From: Larry Rosenman Date: Fri, 5 Apr 2019 06:57:30 -0500 Subject: [PATCH] clarify not needing ng_etf.ko on OPNSense, its already there --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 021eb5d..933efb3 100644 --- a/README.md +++ b/README.md @@ -311,13 +311,14 @@ However, I don't think this works for everyone. I had to explicitly tag my WAN t For OPNSense (tested and working on 19.1): follow the pfSense instructions, EXCEPT: 1) modify pfatt.sh to set OPNSENSE='yes' -2) put the pfatt.sh script into `/usr/local/etc/rc.syshook.d/early` as `99-pfatt.sh` -3) do *NOT* modify config.xml, nor do any of the duid stuff -4) note: You *CAN* use IPv6 Prefix id 0, as OPNSense does *NOT* assign a routeable IPv6 address to ngeth0 +2) do *NOT* install the ng_etf.ko, as OPNSense is based on HardenedBSD 11.2, which is in turn based on FreeBSD 11.2 +3) put the pfatt.sh script into `/usr/local/etc/rc.syshook.d/early` as `99-pfatt.sh` +4) do *NOT* modify config.xml, nor do any of the duid stuff +5) note: You *CAN* use IPv6 Prefix id 0, as OPNSense does *NOT* assign a routeable IPv6 address to ngeth0 -I haven't tried this with OPNSense or native FreeBSD, but I imagine the process is ultimately the same with netgraph. Feel free to submit a PR with notes on your experience. +I haven't tried this with native FreeBSD, but I imagine the process is ultimately the same with netgraph. Feel free to submit a PR with notes on your experience. # U-verse TV