0

I currently have my Time Capsule to forward all inbound requests on port 80 to my Mac Mini which runs a web server with its local ip address of 192.168.1.8. I also have DNS set up so that if I go to example.com then it will send the request to my static public IP which will in turn cause the Time Capsule to forward the request on port 80 to my Mac Mini.

However I now have a Raspberry Pi on the local network also, with the ip address of 192.168.1.5. I want to be able to access the web server on the Raspberry Pi by going to pi.example.com, but I'm not sure how I can get the Time Capsule to port forward based on the domain. What I'd like to be able to have is something that works like this:

example.com:80       -->   public IP   -->    192.168.1.8:80
pi.example.com:80    -->   public IP   -->    192.168.1.5:80

Update

I've managed to do the above with Virtual Hosts and Forward Proxies in Apache. However that is just for HTTP on Port 80, how could I do this with other services such as SSH and FTP? Like:

example.com:21       -->   public IP   -->    192.168.1.8:21
pi.example.com:21    -->   public IP   -->    192.168.1.5:21
Improve this question
0

1 Answer 1

Reset to default
0

You'll need an HTTP server acting as a proxy in order to forward based on the domain name. The Time Capsule is probably just doing NAT, and so isn't able to do this.

Improve this answer
8
  • How exactly would I go about doing that?
    – Joshua
    Commented Mar 6, 2013 at 22:34
  • Well I've managed to do that with Virtual Hosts and Forward Proxies in Apache now. However that is just for HTTP on Port 80, how could I do this with other services such as SSH and FTP?
    – Joshua
    Commented Mar 7, 2013 at 19:10
  • @Joshua SSH and FTP don't have a concept of virtual hosts, so it can't be done at that level. You'll have to use different ports.
    – mgorven
    Commented Mar 7, 2013 at 19:11
  • So for any other port other than 80 and I assume 443 it can't be done?
    – Joshua
    Commented Mar 9, 2013 at 12:16
  • @Joshua It's the protocol which is relevant, not the port number. Most protocols don't have the concept of virtual hosts.
    – mgorven
    Commented Mar 10, 2013 at 20:09

Not the answer you're looking for? Browse other questions tagged .