Behind a router. (HW firewall). So OSX: Off. (The less resources the better)
The problem with the Mac OS X firewall isn't lack of power - it's lack of GUI configuration tools for outbound connections that are built-in. The firewall built into Mac OS X can filter outbound connections just as easily as it can inbound - there's just no GUI for configuring it.You have to balance your needs versus the added bit of security a firewall provides. The firewall included in OS X is a pretty feeble affair - not worthless, but close to it.
The OS X firewall (at least up until OS X 10.4.9) only tries to control incoming traffic. It does nothing for outgoing traffic - which puts it behind the most recent stuff from the Windows worldThis is one reason why you may want to spring for Little Snitch, which essentially provides the other side: control of outgoing traffic. The other thing, is that the OS X firewall has very little in the way of controls and a subpar GUI. Overall, again, as firewalls go, it's one of the least impressive out there.
Having a firewall can't hurt, but frankly if you are behing a router, the additional protection offered by OS X firewall is not much at all. Meanwhile, it can cause problems if you run bittorrent and the like.
If you are out and about with a laptop, sure turn it on - won't hurt. If you're at home behind a router and running bittorrent and such applications, I wouldn't bother.
firewall is on every day, deny udp, stealth mode! I also have a hardware firewall router by linksys and 128 bit encryption. Wife is using a windoze box so I can never be too careful. (darned company laptop dell)
First, welcome to the Mac Platform.
Yes, turn your firewall on, block UDP, and enable Stealth mode. You may enable logging if you prefer. The firewall logs (who's hitting on you, for lack of a better way to put it. ) may be viewed by launching the console.app, found in the utilities folder. It's under var/log ipfw.log.
It's not too fancy, just a plain text style log.
As others have suggested, you can always invest in a firewall/router, for extra security if you feel it's necessary.
May be a dumb question but how do i block UDP and where to I enable "stealth mode". Firewall's already on.
Why are you all blocking UDP traffic?
Appreciate the info FrankBlack. Followed your well written instructions and guess what...UDP was already blocked and I was in stealth mode. also logging was on and i cleared the log. looked like there were lots of options on the left side of the log after clicking on the top left icon labled "logs". should i be clearing all of them or just the one that automatically comes up.
thanks again for the help.
wanda.
Mac OS X Panther and earilier did indeed have the problem you mentioned. However, in Tiger (and later), Apple added launchd, which has the clever ability to reschedule things that were supposed to run while the computer was off or asleep to run when it's next awakened or turned on. Macjanitor is still useful on these systems for running the scripts manually.You don't have to be too concerned about clearling the logs. As you've noticed, the system log is handy, and has quite a bit of information. The Crash reporter is frequently used by techs for troubleshooting purposes. In a lot of companies, these logs are retained for security purposes.
One thing you can do, and it's very simple: Use a freeware app called Macjanitor, to run three maintenance scripts once in awhile.
Problem: Unix was originally built to run on huge systems, running 24/7. These maintenance scrpits, called "cron jobs" by the Guru's, would normally run in the middle of the night. So, since most people either shut down their machines, or let them sleep when done for the day, the scripts never get run.
These scripts may be run through the terminal, but macjanitor puts a nice GUI on it. Again, it's freeware. You can read more about it at version tracker and find a link to download the latest version.
Here is a link to an Apple Tech info article on the maintenance scripts.
Running these only takes a few seconds for the "daily" and "monthly" portions. The "weekly" one may run for several minutes. Your mac may look like it's doing nothing, but the script is indeed running.
Meanwhile, it can cause problems if you run bittorrent and the like.