Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Feb 2002 14:38:09 -0600 (CST)
From:      "Lane Holcombe" <lane@joeandlane.com>
To:        Jaime Kikpole <jkikpole@cairodurham.org>, questions@freebsd.org
Subject:   Re: Getting FreeBSD to talk to a proxy?
Message-ID:  <200202142038.g1EKc9M04592@joeandlane.com>

next in thread | raw e-mail | index | archive | help
I have been all through this for the last week.  UGH!  I thought it 
would drive me mad.

Here's what you do:

For clarity I put the proxy at IP address 172.16.7.1 and port 80.  The 
port defaults to 3128 if you don't include it. 

Edit your .cshrc and add the following 2 lines:

setenv HTTP_PROXY 172.16.7.1:80
setenv HTTP_PROXY_AUTH "basic:<REALM>:<USERID>:<PASSWORD>"

Where <REALM> is the name of your proxy realm, <USERID> is your proxy 
Userid (if required by your proxy), and <PASSWORD> is your proxy 
password (if required by your proxy).

According to fetch(3) (or (5)?) "basic" can be replaced with an "*" 
(asterisk) if you will negotiate multiple types of authentication.  It 
never worked for me though.

Also, you are supposed to be able to replace <REALM> with an "*" 
(asterisk) if you will negotiate multiple realms, but that never worked 
for me either.  I think the reason that this never worked for me is 
because our proxy is not properly configured.  I say this because our 
proxy server identifies itself as "proxy server" but I had to put the 
name of our NT Domain in place of <REALM> in order to make the whole 
thing work.

My understanding is that if you do not use <USERID> and <PASSWORD> 
(i.e. if your don't have to authenticate when you request an http page) 
then you should NOT include the ":" (colon(s)) in HTTP_PROXY_AUTH.
On Thu, 14 Feb 2002, Jaime Kikpole wrote:

Also, if you have an FTP proxy then you should still try it this way 
and if that doesn't work then remove the HTTP_PROXY variable and 
replace it with FTP_PROXY (But I don't think you should change the 
HTTP_PROXY_AUTH variable).

Finally you must log out, go home and get some sleep, and then log back 
in before the thing will work.  I thought that just the logout/login 
part was required, but when I left yesterday this was not working and 
when I got back to work today it was.

One more thing:  ping probably will not work through your proxy.  This 
has to do with UDP/TCP packets or something like that.  I don't 
remember where I got that information but it seems to be true in my 
arrangement.

good luck!

> On Thu, 14 Feb 2002 questions@geektank.org wrote:
> > I have a freebsd 4.5 server sitting behind a proxy currently, but I 
have
> > no idea how to get the server to talk to the proxy to allow me to 
have
> > external internet access.  Is there a particular doc I can read?
>
> 	What kind of proxy?  Most proxies that people are exposed to are
> actually HTTP or SOCKS proxies.  In these cases, you don't need to
> configure FreeBSD to communicate with them so much as you need to
> configure the application in question (e.g. Netscape Communicator, 
ftp,
> ssh) to communicate with them.  In that case, see the documentation 
for
> the given application.

Well i guess my problem is that I want to do thing like update the ports
tree, ping, tracert, etc, but how do you configure these types of things
to use the proxy? I know I can configure the applications like a
webbrowser to use a proxy, but I'm unsure about these other scenarios.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message


-- 
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202142038.g1EKc9M04592>