Compatibility with Yosemite about local-tld HOT 12 CLOSED

Wo, thanks for the heads up!

On 12.06.2014, at 04:41, Mathieu Allaire [email protected] wrote:

Might be interesting to follow what come up here: basecamp/pow#452

ipfw is removed from yosemite, so we might have to backport some of the suff in pow again!

—
Reply to this email directly or view it on GitHub.

from local-tld.

Maybe just use pow's port proxy feature and call it a day for local-tld?

http://pow.cx/manual.html#section_2.1.4

# http://myapp.dev
$ echo 8000 > ~/.pow/myapp

from local-tld.

@brandonblack I love pow, but the reason for me to have local-tld is a pure Node solution, as that makes the installation story for our users a lot simpler. Not saying pow or Ruby are particularly difficult, it’s just another thing that has different conventions and all that, hence my “clone” :)

from local-tld.

Here are quick steps to get local-tld working in Yosemite. I don't have time right now to make fix but needed this working asap, so had to tinker around. Hope this saves some time from someone else.

/etc/pf.anchors/local.dev

rdr pass on lo0 inet proto tcp from any to 127.0.0.1 port = 80 -> 127.0.0.1 port 5999

/etc/pf.conf

After rdr-anchor "com.apple" add

rdr-anchor "local.dev"

Bottom of the file add

load anchor "local.dev" from "/etc/pf.anchors/local.dev"

Restart PF

sudo pfctl -f /etc/pf.conf
sudo pfctl -e

from local-tld.

This worked to get local-tld working for me, however is it normal to get these warnings?

$ sudo pfctl -f /etc/pf.conf
pfctl: Use of -f option, could result in flushing of rules
present in the main ruleset added by the system at startup.
See /etc/pf.conf for further details.

No ALTQ support in kernel
ALTQ related functions disabled
$ sudo pfctl -e
No ALTQ support in kernel
ALTQ related functions disabled
pf enabled

from local-tld.

As far as I know, these are completely normal. It just informs that some pf functions are unavailable under OS X kernel. However, we don't even need those functions, so you can safely ignore the warnings.

from local-tld.

Perfect. Thanks.

from local-tld.

Thanks for the workaround @tv, but every time I restart my system I need to enter both sudo pfctl -f /etc/pf.conf and sudo pfctl -e again. Is there some way to avoid that?

from local-tld.

You will need to create LaunchDaemon to handle pf startup at launch time. I rarely restart my system, so didn't bother to create this. Check local-tld-firewall.plist for reference.

from local-tld.

@tv Thanks!

from local-tld.

Thx for this!

from local-tld.

This doesn't seem to fix it on Yosemite for me, I still had to do the manual workaround.

from local-tld.