Skip navigation

Configuring OSX 10.6.8 server for Airport.

1039 Views 4 Replies Latest reply: Jan 23, 2013 10:47 AM by DougalfromHants RSS
DougalfromHants Calculating status...
Currently Being Moderated
Jan 22, 2013 11:44 AM

How do I configure OSX 10.6.8 server for Airport when only configured for ethernet? I am moving to an un-cabled and non-ethernet environment. Is it straightforward and do-able by a moderately informed amateur?

Mac mini, Mac OS X (10.6.8), Running OSX Server 10.6.8
  • MrHoffman Level 6 Level 6 (11,695 points)
    Currently Being Moderated
    Jan 22, 2013 1:16 PM (in response to DougalfromHants)

    What network configuration are you trying to achieve?  Airport for non-wired local connections?  Or Airport as a network gateway and unwired connections?  If you're aiming at the former, then you can set the Airport to its "bridged" mode, and run the network services off the OS X Server box like you aways have.  This is the so-called "access point" or AP mode, and makes managing the network easier, and you can run multiple APs.

  • MrHoffman Level 6 Level 6 (11,695 points)
    Currently Being Moderated
    Jan 23, 2013 10:19 AM (in response to DougalfromHants)

    Bridged mode — what's more commonly called an "Access Point" or an "AP" configuration — means...

    • the WiFi devices are network "transparent", and function roughly analogous to a hunk of Ethernet wiring.
    • the WiFi devices are not operating as IP routers.
    • DHCP and the rest of your services are running directly from your OS X Server box.
    • that there is no need to deal with IP subnet routing.
    • little or no need to change the OS X Server configuration.
    • portable devices can move among multiple local WiFi (AP/bridged) devices, without reconnecting.


    If you choose to run your WiFi as routers, you'll be dealing with all the "fun" that is multiple routers. Which is entirely possible, but an approach that requires rather more knowledge of IP.   Also that if (when?) you start using have more than one WiFi device, that clients will have to drop off and reconnect.


    I also prefer a dedicated firewall-gateway box and preferably one with VPN server capabilities, and generally not prefering to use an Airport-class device in that role, nor do I prefer to use an OS X Server box as the firewall-gateway box.  This makes the network simpler, and avoids (unintentionally) exposing ports or such outside your network due to software reconfigurations or sometimes after software installs and updates.


    I'd encourage some general homework here, and do some reading on setting up an IP network, IP routing and related. This area is usually fairly simple — once you've done a few — but it's rather more that can easily fit into a small text input box.  Apple has some related documentation here and here and here and here, and probably a few other spots.  Or get some help.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.