[p4] client on secured network

David Faison dfaison at photon.com
Mon Jun 26 09:36:39 PDT 2006


The most you need ask your admins to do is allow a specific port to be
tunneled.


If you can SSH out of the office back to your home computer, and if you
can forward ANY of the ports of your PC at work out through that secure
channel, then problem solved. Just issue the following command...

> ssh -l <username> -L {any_forwardable_port}:{ip_of_homepc}:1666
{ip_of_homepc}

e.g. ssh -l sehrlichman -L 1919:myhomepc.verizon.net:1666
myhomepc.verizon.net


And then you can configure any p4 client running at work to just point
at the port (e.g. "localhost:1919") that you are forwarding to your home
and you're in business.

As long as you have an active session on your work machine using this
SSH command, all traffic will be forwarded from work ("localhost:1919")
to your machine at home ("myhomepc.verizon.net:1666").

If you are running Windows at work and don't have SSH available, you can
download the PUTTY utility, which can create SSH tunnels and do port
forwarding.

	http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html


__________________________


David Faison, Software Configuration Manager

Photon Research Associates, Inc.

 

dfaison at photon.com

Phone: 703.243.6613
Fax:   703.243.6619


 


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Samuel M T
Ehrlichman
Sent: Monday, June 26, 2006 9:38 AM
To: perforce-user at perforce.com
Subject: [p4] client on secured network

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



More information about the perforce-user mailing list