On Dec 31, 2011, at 11:32 PM, Amos Jeffries wrote:
On 1/01/2012 11:23 a.m., jeffrey j donovan wrote:
turns out to be an OSX 10.6 issue
previous systems were set to 0 the default on 10.6 is 1. disable this and
squid then gets the hit transparently.
sysctl -w net.inet.ip.scopedroute=0
greetings, Im stuck and im not sure what part I should re-do.
I have an xserve running 10.6.8
I have clients routing through the system just fine with ipfw. they can access
the internet via a NAT on the otherside of the squid.
compiled squid 3.1.18
Squid Cache: Version 3.1.18
configure
On Dec 31, 2011, at 4:00 PM, jeffrey j donovan wrote:
greetings, Im stuck and im not sure what part I should re-do.
I have an xserve running 10.6.8
I have clients routing through the system just fine with ipfw. they can
access the internet via a NAT on the otherside of the squid.
turns out to be an OSX 10.6 issue
previous systems were set to 0 the default on 10.6 is 1. disable this and squid
then gets the hit transparently.
sysctl -w net.inet.ip.scopedroute=0
-j
On 1/01/2012 11:23 a.m., jeffrey j donovan wrote:
turns out to be an OSX 10.6 issue
previous systems were set to 0 the default on 10.6 is 1. disable this and squid
then gets the hit transparently.
sysctl -w net.inet.ip.scopedroute=0
-j
Thank you for that info. I've added it to the IPFW
