[p4] p4win / p4web via SSH...
drj at ravenbrook.com
Fri Jan 23 04:49:12 PST 2004
On Jan 23, 2004, at 08:17, Gutschner, Marc wrote:
> Currently, our Perforce server is on the company's internal net. This
> internal net is shielded from the Internet by two firewalls (one
> external, one internal) with most of our other servers (Exchange,
> File-Server, etc.pp.) between them in an DMZ. At this point of time,
> it is not an option to put the Perforce server in the DMZ, so all
> access has to be somehow "tunneled" from the external firewall through
> the DMZ and the internal firewall to our Perforce server...
> Now, I've skimmed over the documentation on www.perforce.com and came
> across a section in the Administrators Guide that deals with running
> Perforce through a firewall. This Document seems to imply that running
> the "standard" Perforce client through a SSH tunnel is rather
> "trivial". Now, does this setup work for a Web client, too? Has anyone
> out there implemented such setup and are there any caveats or pitfalls
> to watch out for?
As long as you can get SSH working there is nothing really special you
have to do with perforce. Just setup a local forward on a port you
like that forwards to the real perforce server and port. I use SSH on
my MacOS X laptop. Here's an extract from my .ssh/config:
Host ssh.ravenbrook.com raven ravenbrook
LocalForward 11666 perforce.ravenbrook.com:1666
Once I've connected (to ravenbrook) with SSH I can point my perforce
clients at localhost:11666, which I do by putting P4PORT=11666 in my p4
I run this over a DSL line, about 512Kbps, and the performance is fine;
obviously large syncs take a while, but they pretty much max out the
bandwidth so I have no complaints.
More information about the perforce-user