Create this file under /etc/pf-.conf and add the following contents. Once your anchor file checks out, you need to add a pfctl config file. Rdr pass on lo0 inet proto tcp from any to any port = -> 127.0.0.1 port Creating a pfctl config file Present in the main ruleset added by the system at startup. fctl: Use of -f option, could result in flushing of rules If you see output that looks something like the below, with no errors, you’re good. The ports won’t actually be forwarded yet, this just checks the validity of your anchor file. To test the anchor file, run the following command. You can add one or many lines of the following format: rdr pass on lo0 inet proto tcp from any to any port -> 127.0.0.1 port Testing the anchor file This defines the ports we want to forward. The first file we need to add is an anchor file. Possible in the hopes that they won’t be wiped out with the next upgrade. Also, since all of myĬhanges had been wiped out with this upgrade, I wanted to try to keep my changes out of existing system files as much as
Protection (SIP) prevented me from editing some necessary files. When I tried to re-apply them, a new feature called System Integrity Previously I had followed some of the steps in this gist, but all of those changes hadīeen wiped out with the upgrade. Recently when I updated to OS X El Capitan (10.11) I noticed that
Without having to start vagrant with root privleges. I forward local ports on my OS X machines using pfctl so that I can use traditional ports for HTTP and HTTPS with Vagrant Update: I have tested this with MacOS Sierra and it works for me!
0 kommentar(er)
