[p4] client on secured network

[Albrecht, Matt]

You could always try running the Perforce server on a different port
number, like 22 (ssh).  I would discourage using port 80 (http), due to
potential proxy servers throwing out the transactions.

If you want to use the ssh alternative (which most people will highly
recommend to help block out unwanted listeners), you'll want the sshd
process running on your Perforce server, then run the ssh port
forwarding process on the client machine (connecting to your home sshd
server).  Set your P4PORT on the client machine to the local tunnel
port.

In other words, I'll use the Perforce document's port numbers to
illustrate what's going on in this configuration:
	home machine:
		hostname: compy.home
		p4d listening on port 3710
		sshd listening on port 22
	work machine:
		hostname: xyz.work
		ssh -n -L 4242:compy.home:3710 compy.home sleep 9999999
&
		P4PORT=4242 (implies connecting to localhost)

This should open a secure tunnel from the work machine to your home
machine.  Someone correct me if I've made a mistake here.


> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Sam 
> Ehrlichman
> Sent: Monday, June 26, 2006 11:22 AM
> To: perforce-user at perforce.com
> Subject: Re: [p4] client on secured network
> 
> Thanks for all the comments.  What I don't understand is 
> this.  A number 
> of folks have suggested using ssh tunnelling, and referred me to this 
> documentation: 
> http://www.perforce.com/perforce/technotes/note022.html.  
> But this seems to describe a situation where the client has complete 
> access to the "big bad network" and the server is behind a firewall.  
> This is not the situation I am in.  Rather, the *client* is behind a 
> firewall and the server is on the open network. 
> 
> Any suggestions?
> 
> Thanks again,
> Sam
> 
> 
> >
> >Hello all.  I am a graduate student who has been using the 
> 2-user  version
> >of Perforce to manage files between my home and office
> >computers.  I run p4d on a small Linux box in my home.  
> Everything has 
> >worked swimmingly up until last month, when the 
> administrators for the 
> >network at our department got paranoid and decided to block 
> most traffic 
> >to and from the network.  Currently, email, http, and ssh 
> work, but not 
> >much else does (e.g., no ftp, no ping or tracert, etc.).  
> Needless to 
> >say, p4 does not work anymore either.
> >
> >Does any of you p4 experts know a way I can continue to use 
> p4 from the 
> >office under the circumstances?  Can I get the client to use http 
> >tunneling or something like that?  (The documentation regarding ssh 
> >tunneling seems to focus on the situation where the *server* is on a 
> >secure network, which is not the issue here.)
> >
> >If I need to ask the administrators to make changes, what 
> would be the 
> >likely minimal change that would get things to work?
> >
> >Thanks so much.
> >
> >  
> >
> 
> 
> -- 
> Sam Ehrlichman
> School of Operations Research and Industrial Engineering
> Cornell University
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>