Comments on: Living with Leopard’s Firewall http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/ you probably have a better idea Wed, 19 Nov 2008 03:51:16 +0000 http://wordpress.org/?v=2.6.3 By: Jaiwant Mulik http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2667 Jaiwant Mulik Fri, 10 Oct 2008 03:01:23 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2667 I found a workaround by enabling the right applications. I was trying to enable port 8080 to allow Plone to work. After not being able to get ipfw to work as expected I added python.app (Resources) and the python executable (bin) to the "allow these applications to accept .." option under firewall. Everything works as expected. Sometimes you have to scroll down in the allowed application textbox to see which applications are being actively blocked for accepting connections. I found a workaround by enabling the right applications. I was trying to enable port 8080 to allow Plone to work. After not being able to get ipfw to work as expected I added python.app (Resources) and the python executable (bin) to the “allow these applications to accept ..” option under firewall. Everything works as expected. Sometimes you have to scroll down in the allowed application textbox to see which applications are being actively blocked for accepting connections.

]]> By: rob zand » Blog Archive » links for 2008-06-17 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2377 rob zand » Blog Archive » links for 2008-06-17 Tue, 17 Jun 2008 23:56:08 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2377 [...] Atomic Lemur » Living with Leopard’s Firewall (tags: leopard mac firewall) [...] [...] Atomic Lemur » Living with Leopard’s Firewall (tags: leopard mac firewall) [...]

]]> By: Miss.Detd http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2339 Miss.Detd Sun, 08 Jun 2008 20:09:38 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2339 Well...i can enter this codes...but nothing seems to work with warcraft 3. The ports 6112 to 6119 should be open. it's not my router because I can hoste fine on Vista... Mac on the other hand gives problems, and can't figure out why. pleasy help. grtz Well…i can enter this codes…but nothing seems to work with warcraft 3.

The ports 6112 to 6119 should be open. it’s not my router because I can hoste fine on Vista…
Mac on the other hand gives problems, and can’t figure out why.

pleasy help.

grtz

]]> By: hagbard_23 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2268 hagbard_23 Wed, 23 Apr 2008 14:12:06 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2268 Thanks E Fox, I've been looking for this so long, but your commands finally worked! Thanks E Fox,
I’ve been looking for this so long, but your commands finally worked!

]]> By: E Fox http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2249 E Fox Wed, 09 Apr 2008 20:47:23 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2249 At least for me, the fix from Kotov did not work entirely, the syntax no longer makes the port into the ip (thanks Kotov), but it just did not get traction for me . . . so I found some other syntax that did. Hope this helps prevent the day I have had. DID NOT WORK: ipfw add allow tcp from any 80 to any 80 DID WORK: ipfw add allow tcp from any to any 80 To test: run your portscan or nmap ipfw show ipfw delete (the entry number) run your portscan or nmap again repeat to convince yourself. . . e At least for me, the fix from Kotov did not work entirely, the syntax no longer makes the port into the ip (thanks Kotov), but it just did not get traction for me . . . so I found some other syntax that did. Hope this helps prevent the day I have had.

DID NOT WORK:
ipfw add allow tcp from any 80 to any 80

DID WORK:
ipfw add allow tcp from any to any 80

To test:
run your portscan or nmap
ipfw show
ipfw delete (the entry number)
run your portscan or nmap again

repeat to convince yourself. . .

e

]]> By: Kotov http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2204 Kotov Fri, 23 Nov 2007 14:42:43 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2204 dude only thing >> sudo ipfw add allow tcp from 80 to 80 is not opening port, but rather treats it as IP, so this: >> 33400 allow udp from 0.0.0.80 to 0.0.0.80 is exactly what it looks like should be add allow tcp from any 80 to any 80 or even ad allow tcp from any 80,8080... you get the point :) cheers dude only thing
>> sudo ipfw add allow tcp from 80 to 80
is not opening port, but rather treats it as IP, so this:
>> 33400 allow udp from 0.0.0.80 to 0.0.0.80
is exactly what it looks like

should be
add allow tcp from any 80 to any 80
or even ad allow tcp from any 80,8080… you get the point :)

cheers

]]> By: Juan http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2187 Juan Thu, 08 Nov 2007 23:49:53 +0000 http://taisteal.atomiclemur.com/2007/10/living-with-leopards-firewall/#comment-2187 We both did exactly the same thing: I bought my Leopard copy at 6pm in a compUSA and got the rebate. Works pretty good. I agree with you about the firewall issue. I thought little snitch was not going to be as useful as it was before, but i'm afraid it will be more needed than it was before :/ We both did exactly the same thing: I bought my Leopard copy at 6pm in a compUSA and got the rebate. Works pretty good.

I agree with you about the firewall issue. I thought little snitch was not going to be as useful as it was before, but i’m afraid it will be more needed than it was before :/

]]>