On Friday, June 10, 2011 07:33:07 AM Amos Jeffries wrote: <snip> > > ... behaved as intended: when clients went through > > the http_port listener 192.168.2.2:80, the tcp_outgoing_address > > worked as expected, wherein http://www.whatismyip.com > > displayed 192.168.2.2 rather than 192.168.1.1. > > * whatismyip.com is a global website outside on The Internet > * 192.168.* is a rfc1918 IP space > * rfc1918 IP are not used on The Internet > > Ergo the Squid outgoing IP address is not what is being displayed by > that website. >
Sorry for making things difficult with my example - I completely failed to make it understood that the IPs in the config examples were dummy values. All the actual IPs in question under the real config are indeed within the publicly routable, non-reserved address space. So, to simplify, I found that using: acl <aclname> myportname <someStringA> http_port <ipaddr:port> name=<someStringA> tcp_outgoing_address <ipaddr> <someStringA> ... failed to cause the tcp_outgoing_address to work as expected/intended, while: acl <aclname> myip <ipaddr> http_port <ipaddr:port> name=<someStringA> tcp_outgoing_address <ipaddr> <someStringA> ... worked as intended. .. the only change being that I used the 'myip' acl rather than the 'myportname' acl.
