“What I wanted was very simple and very routine—so routine and simple that it’s enabled with a single checkbox in Mac OS X 10.2 and 10.3. But I wasn’t working with the client versions of Mac OS X. No, I was in server land. And I wanted Panther Server (Mac OS X Server 10.3) to hand out private Network Address Translation (NAT) managed addresses over DHCP (Dynamic Host Configuration Protocol).” Read the tutorial at OReillyNet.
Squeezing NAT Out of Panther Server
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
No doubt it could be streamlined, but the author comes off like its some sort of stange, secret, and previously unknown solution. All the necessary changes make sense to me…
We’ve been doing this off and on with MacOS X Server since 10.2 was released; although we do everything through the terminal, since it IS just ipfw & natd….
Can’t vouch for the dhcpd stuff, though. In any case, I find editing a few config files less cumbersome than the method described in this article….just my two cents.
Back in the hectic worm-ridden times of early Fall, we had a few cases of the ports of Mac owners being blocked because it appeared they had a worm. Of course that doesn’t make sense, as it turned out they had NAT enabled and people with virus’s were connecting through them. I’m not familar with Macs, but perhaps it should be made more clear that this is something you need to turn off while on a public LAN. Mac (and Windows more so with their universial PNP stuff) seem to enjoy assuming their users are on safe networks.