YUM with proxy

watcher69b · 04-20-2008, 07:28 PM

I am running a few red hat servers and I cannot get yum to work via terminal with out 1st logging onto the server and putting my credentials into the Border Manger webpage.
Has any one been able to get this to work only using a command line?
I have no control over the Novell side of the house so i cannot allow my servers to bypass the proxy. Also the proxy has a home made ssl cert that is no longer valid. The Novell crew won’t regenerate it either.

I have tried
export http_proxy=usernameassword@https://192.168.x.x:9000
export http_proxy=https://usernameassword@192.168.x.x:9000
I am at a loss for what to do

Here is what i get...
[root@box1 ~]# yum update
Loading "rhnplugin" plugin
Loading "installonlyn" plugin
There was an error communicating with RHN.
RHN support will be disabled.
Error communicating with server. The message was:
Moved Temporarily
Setting up Update Process
Setting up repositories
No Repositories Available to Set Up
Reading repository metadata in from local files
No Packages marked for Update/Obsoletion

Simon Bridge · 04-21-2008, 07:03 AM

http://www.fedoraforum.org/forum/sho...=&threadid=742
I take it you need to authenticate to the proxy? You put the username and password in the wrong place.

Code:

http_proxy=http://user:passwd@proxy.foo.com:portnumber

Better:

create the following files in /etc/profile.d, and then this will work in *any* shell for *any* user of the system

Code:

#proxy.sh
export http_proxy=http://host.com:port/
export ftp_proxy=http://host.com:port/
export no_proxy=.domain.com
export HTTP_PROXY=http://host.com:port/
export FTP_PROXY=http://host.com:port/

#proxy.csh
setenv http_proxy http://host.com:port/
setenv ftp_proxy http://host.com:port/
setenv no_proxy .domain.com
setenv HTTP_PROXY http://host.com:port/
setenv FTP_PROXY http://host.com:port/

watcher69b · 04-21-2008, 01:31 PM

I created the 2 files and rebooted. Still no joy. Do i need to call the files before running yum?

i also had to replace http:// on all of them with https:// because http to the proxy is blocked...

Simon Bridge · 04-22-2008, 03:02 AM

Then you need to set https_proxy instead.

Code:

http_proxy=https://user:passwd@proxy.foo.com:portnumber
https_proxy=https://user:passwd@proxy.foo.com:portnumber
export http_proxy
export https_proxy

Always providing that the proxy requires an ssh encrypted http request. Usually, an https request is asking the proxy for connection to a secure web page. So check. Also check the authentication part.

There is a discussion about this here.

Quote:

Having a proxy configured to answer on a secure socket would add nothing to the security of the proxied connection.

watcher69b · 04-22-2008, 06:36 AM

I spoke to the Novell guys. the problem is that they need to add the servers IP addresses to the exception list on the proxy server.
Thank you for the help!

Simon Bridge · 04-22-2008, 07:08 AM

Ahah! So authentication was the issue

At least all this effort ruled out anything you were doing.