Jim my transparent proxy setup is exactly as described. The only thing is, that method fails with EINVAL in the ipnat lookup call if you use it with 32-bit squid and 64-bit ipnat. The immediate reason is that the definition of SIOGCNATL depends on the sizeof(natlookup*) via the _IOWR macro. So the 32-bit compile gets the wrong value. So I tried both - compiling squid in 64 with gcc 3.1, and - using the 32-bit compatibility functions for use with ioctl that come with Solaris, ie ddi_copyin etc. Both of these methods work. Actually for a general user, the first is probably simpler, if you are willing to get gcc 3.1 on CD from the FSF in Boston. Otherwise you have to build it yourself.
Gary > ----- Original Message ----- > From: "Jim Sandoz" <[EMAIL PROTECTED]> > To: "Gary Price (ICT)" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Saturday, March 01, 2003 2:02 AM > Subject: Re: 32 bit compatibility on Solaris 8 > > > > > > hi gary, > > > > how does your 'custom' transparent proxy differ from the > > squid/ipf integration which had been done previously, e.g. > > > > http://www.squid-cache.org/Doc/FAQ/FAQ-17.html#ss17.1 > > > > also see > > http://home.earthlink.net/~jaymzh666/ipf/IPFsolaris.html#11 > > > > regards, > > jim > > > > > > > > > > Gary Price (ICT) wrote: > > > Recently I wanted to get Squid to be able to do transparent proxying > without > > > using the HOST header, so I made a custom version of IPFilter that > allows a > > > 32-bit program to call successfully into ipnat. Would anyone be > interested > > > in this code? I would be happy to integrate it myself. What is the best > way > > > to proceed? > > > > > > Thanks > > > Gary Price > > > Intelligent Compression Technologies > > > > > > > > > >
