Comment 5 for bug 1288135

Some minor issues on setting up /etc/pf.conf: our rules must be in precise order, otherwise they won't be accepted by `pfctl`.

In /etc/pf.conf there's already a minimal configuration, on brand-new installations:

scrub-anchor "com.apple/*"
nat-anchor "com.apple/*"
rdr-anchor "com.apple/*"
dummynet-anchor "com.apple/*"
anchor "com.apple/*"
load anchor "com.apple" from "/etc/pf.anchors/com.apple"

For instance, one should inject

nat on en0 inet from ! (en0) to any -> (en0)

Between ^dummynet and ^anchor

Keeping in mind that this file won't be likely modified by the desktop user and probably he won't try Fuel on production (with production defined /etc/pf.conf), would you suggest to simply backup /etc/pf.conf to /etc/pf.conf.bak, reload PF rules, run the Fuel demo and finally restore /etc/pf.conf.bak in place?

Other suggestions work like a charm.

Also, solving this bug means that ./launch*.sh must be run by root.