Port forwarding/triggers for accessing Trac from outside your firewall.

[anonymous]

I would like to request documentation be posted outlining how a router or firewall should be setup to allow Trac access from the outside world (in general terms).

The scenario is a developer working from home on a single workstation who needs to visit client sites and have access to SVN and Trac externally from time to time (and allow clients access to Trac to post tickets).

This question is probably not relevant to Apache users, just TracD users.

I have attempted to make a second trac instance available to the outside world on another port using TracD, but it is not enough to merely forward the port as it appears that another port must be opened from the inside when TracD responds and that this port number cannot be predicted ahead of time.

Simple documentation to the effect of 'trigger port/protocol' and 'open port range/protocol' may be all that is required to make this implementation simple to set up.

[nkantrowitz]

As you are accessing from outside, "port triggers" won't help. HTTP uses TCP port 80, so open and forward that port. Firewalls should not block outbound connections greater than port 1024 in general. This information can be found in any of a variety of sources.