Skip to content
This repository has been archived by the owner on May 15, 2020. It is now read-only.

Get Pow working under OS X Lion Server #305

Closed
wants to merge 1 commit into from

Conversation

codyrobbins
Copy link

Changes suggested by @kupinus to resolve #172.

  • The ipfw firewall rule is now created before all other rules.
  • Set net.inet.ip.fw.enable in addition to net.inet.ip.forwarding.

* The `ipfw` firewall rule is now created before all other rules.
* Set `net.inet.ip.fw.enable` in addition to `net.inet.ip.forwarding`.
@jwechsler
Copy link

Sorry, added this note to an old thread. Duplicating here:

The above is almost correct, but also know that it's still erratic/crazy because under Mountain Lion, the ipfw rules are flushed by, er, something that I couldn't find. You can see evidence of the rule flush in the console log. Therefore, here's what I do (and perhaps what pow will need to do):

sysctl -w net.inet.ip.forwarding=1
touch /etc/ipfilter/ipfwstate-on
echo "add 100 fwd 127.0.0.1,20559 tcp from any to me dst-port 80 in" >> /etc/ipfilter/ipfw.conf

/etc/ipfilter/ipfw.conf is where the admin for the box is supposed to put custom rules. Adding them in a launchdaemon works, but only until this random rule flush/recreate process happens. You could probably just write the ip.fw.enable directly on install to get it going, but it will get reset on restart by rc.server unless you add the rule the ipfw.conf

I've successfully gotten this to work on three Mountain Lion machines that were struggling.

And, these steps only seem to apply if the machine is not a clean install of Mountain Lion. Sigh.

@tadman
Copy link

tadman commented Dec 17, 2012

An experimental install of OS X Server for 10.8 left my Pow installation non-functional. The firewall rule for ipfw is present but apparently ignored and it's not clear if Server somehow over-rides or disables this.

As a work-around, I was able to use the solution for co-existing with Apache and restore functionality.

As a note, /etc/apache2 does not seem to be affiliated with the Server version that's actually located elsewhere.

This seemed to work for me:

sudo curl https://raw.github.com/gist/1058580/zzz_pow.conf -o /Library/Server/Web/Config/apache2/other/pow.conf

Adjusting :88 to :20559 is also required.

I'm not sure if the new pfctl interface might be able to do the proper port mapping with Server, but that could be a better solution than this.

@macsplan
Copy link

any update on this?

@nsforge
Copy link

nsforge commented May 27, 2013

This allowed me to get pow working under OS X 10.8.3. Frustrating that the PR hasn't been accepted by @37signals, it could have saved me (and presumably many others) a whole lot of wasted time.

I actually ended up here trying to troubleshoot a non-working installation of Anvil. Making the changes described here to cx.pow.firewall.plist made Anvil (0.76) work correctly.

@travisjeffery
Copy link
Contributor

fixed in b32762b. didn't see this PR until after making that change.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Couldn't resolve configured domains
6 participants