Re: tinyproxy

2007-03-08 Thread Paolo 
On Thu, Mar 08, 2007 at 10:43:53PM +0100, Carolyn Debian wrote:
> 
> I changed to 192.168.1.1 and no difference.

but at least it's correct now :)

dunno much about tinyproxy, though your proxy's log look weird:

> In tinyproxy.log, I could see:
>
> CONNECT ... Connect (file descriptor 7): [192.168.1.1]
> CONNECT ... Request (file descriptor 7): GET http://google.com/HTTP/1.1
> INFO ... No proxy for google.come
> ERROR ... opensock: connect() error "Connection refused".
> INFO ... Not sending client headers to remote machine
>
> This is what's in tinyproxy.log when I tried to browse the website hosted
> on 192.168.1.1:
>
> CONNECT ... Connect (file descriptor 7): [192.168.1.1]
> CONNECT ... Request (file descriptor 7): GET http://my.dyndns.org/HTTP/1.1
> INFO ... No proxy for my.dyndns.org
> CONNECT ... Established connection to host "my.dyndns.org" using file
> descriptor 8.
> INFO ... Closed connection between local client and remote client
>

seems misconfigured. pls post the config.

--
paolo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: tinyproxy

2007-03-08 Thread Stephan Balmer 
> The connect() function doesn't work. The connection is refused. So how can 
> I check if port  (tinyproxy listens on it) can send out http request?

Test first whether you can reach any Internet hosts at all with commands
such as:
  ping google.com
  wget google.com
on the proxy host. Simply put: if they work, the problem lies with
tinyproxy, if they do not work, your firewall setup is too strict.

In case you have a 'Bind' directive in the tinyproxy.conf, try removing it
or replacing it with
  Bind $EXTIP
where $EXTIP is the IP adress of eth0 (your external interface, I presume) 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]