So for years, I've set up servers to also be routers. It's really easy, just stick a second ethernet card in there. Then enable NAT and DHCP and you're golden. OS X Server's DHCP server is really nice. Very easy to set up, super reliable, and clients get an IP from it in about 2 seconds. The biggest benefit is you're not dealing with cheapo routers crapping out every 6 months.
But here's my problem. I've been having problems with Snow Leopard Server acting as a router since day one. I'm actually still running leopard server on my home mac mini server. Early on, the problems I'd have were that after a short time of working perfectly, everything would just stop working. Nothing would get an IP from DHCP, not even my server from my ISP. Everything would just stop. Like the firewall in 10.6 was going crazy. I had hoped that by 10.6.4, this was fixed. But I just set up a server for a customer, and it still seems to be happening. After a day of perfect function, suddenly all networking has shit the bed.
Is there anything special you have to do with the firewall to make nat/dhcp work, and continue to work, seamlessly? Or maybe some other obscure thing? Something that would make 10.6 Server stop acting up, and just be a super reliable, high performance router like all previous versions of OS X Server would do?
Top
