Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I run several servers on a small private network. one of which runs linux and apache and I have traffic port forwarded to that server using my router.

I have added another server an OSX Server to the network that i would like to access externally.

I was planning to set up the OSX server as a .private and access it via VPN but I'm not sure how to proceed in terms of the router set-up to enable traffic to access that server.

currently ports 80,22 route to my linux web server.

Thanks for any ideas or help

share|improve this question
My Router is a Netgear WNR834Bv2. I can replace this with an Apple Time Machine that I have on the network. – MB. Apr 27 '13 at 2:04
up vote 0 down vote accepted

Your question is a bit vague to give a clear answer.

Option 1: Port forwarding with different ports. You have 80,22 going to your linux web server, you could have 8080 and 8022 going to your OS X server. Pro: trivially easy. Con: to access them, you would have to specify every time which could get annoying. Also not secured.

Option 2: VPN terminating on your router. There are many common kinds of VPNs (PPTP, L2TP, IPSEC, OpenVPN) and which router model and which computers need to access it, and how secure you need it to be will affect how you can set this up. That said, most home routers will not have this as an option at all. But typically you would configure the VPN, connect to it (Windows and Macs have built in PPTP clients, for example), and then you can access anything on your internal network.

Option 3: Use SSH as if it was a VPN, which is one of it's lesser known features. You connect to SSH on your Linux server, and relay all traffic through that out onto your home network. Pro: cheap, easy-ish, effective, works with any kind of traffic, traffic is encrypted. e.g. Con: not all that easy if you're not familiar with that kind of thing, requires more work to connect to (SSH with port forwarding, then changing how you connect things).

Option 4: VPN terminating on your Linux or OS-X computer. Can be very difficult to setup, but the most configurable option. E.g. Linux IPSEC, OpenVPN. Pro: configurable. Con: needs a client install, complex.

share|improve this answer
Thanks for the answer. What I did was use port fwding to the OS X server VPN. the limitation is that I will not be able to route http traffic to that server from outside as port 80 is being routed to the Linux server. I might try the fwd of SSH from the Linux server if I get a chance. – MB. May 4 '13 at 22:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.