View Full Version : updating src via proxy ?
mgp
November 18th, 2008, 18:07
Hi,
I was wondering if there is any way to update src via proxy ?
with ports it's easy ,I'm just using portsnap which uses fetch to obtain ports via HTTP and it's easy to setup proxy for fetch
do you have any idea how to update src ? :)
thank you
regards,
mgp
sbe
November 18th, 2008, 18:26
1)cd /usr/ports/net/prtunnel
make install clean
2)prtunnel -t http -H myproxy.myfirm.com -P 3128 -D 5999 cvsup.FreeBSD.org 5999
3)vi supfile:
...
*default host=127.0.0.1
4)csup supfile
5)killall -9 prtunnel
none
November 18th, 2008, 19:09
prtunnel accepts user and pass ?
really great to know this software !!!
none
DutchDaemon
November 19th, 2008, 02:49
Not every proxy will allow connections to ports like 5999 (e.g. a restrictive Safe_Ports setting in Squid config).
bsddaemon
November 19th, 2008, 07:42
prtunnel accepts user and pass ?
really great to know this software !!!
none
Im not sure about prtunnel but I have been using httptunnel and it does support proxy authentication, so you may wanna check it out:
www/httptunnel
By the look of the command, the syntax is almost identical
mgp
November 19th, 2008, 09:25
thanks a lot guys!
prtunnel worked :)
vivek
November 19th, 2008, 11:12
What's wrong with http_proxy variable ? Something like as follows should work under bash:
export http_proxy=http://user:password@proxy.server.i.p:port/
Why install additional software?
mgp
November 19th, 2008, 16:24
because csup doesn't use fetch and this variable is used by fetch
none
November 20th, 2008, 00:17
because csup doesn't use fetch and this variable is used by fetch
I do confirm that. here at work it doesn't go and that's final. I used to csup at home and put it in a pendrive or in my home apache ...
even the svn repo from freebsd.org couldn't pass through the proxy :(
none
vivek
November 20th, 2008, 12:22
because csup doesn't use fetch and this variable is used by fetch
Actually portsnap man page recommends using http_proxy to save bandwidth on both ends. However, csup only works with proxy if either:
csup can be used through a SOCKS proxy server with the standard runsocks command. Your csup executable needs to be dynamically-linked with the system libraries for runsocks to work properly.
Or using ssh forward
ssh -f -x -L 5999:localhost:5999 serverhost sleep 60
Or any one of the above methods :)
none
January 28th, 2009, 01:41
TCP_DENIED/403 1409 CONNECT cvsup2.freebsd.org:5999 - NONE/- text/html
is what I get from my proxy :(
anyone has another way ?
will svn do the trick ?
thanks,
none
pablo
January 28th, 2009, 19:41
By default SQUID deni method CONNECT to ports other than 443. So, if you have acces to squid.conf, try to extend your list of SSL_ports:
acl SSL_ports port 5999
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.