RE: A few patches

> -----Original Message-----
> From: Adrian Chadd [mailto:adrian@creative.net.au]
> Sent: Tuesday, 13 March 2007 4:59 PM
> To: Steven Wilton
> Cc: 'Adrian Chadd'; squid-dev@squid-cache.org
> Subject: Re: A few patches
>
> On Tue, Mar 13, 2007, Steven Wilton wrote:
>
> > Good point. The only problem is that (under Linux at
> least) we can't find
> > out the original destination port (ie if traffic destined
> for port 80 is
> > redirected to port 3128). Would you suggest this as a
> configuration option
> > on a per-port basis? (ie squid can listen to multiple
> ports, and the port
> > that the connection arrives on is used to determine the
> destination port).
>
> What, this isn't accessible via clientNatLookup() ? Hm! I'm
> sure I've seen
> it supported somehow/somewhere.

It looks like BSD may support this, but the Linux NAT lookup does not write
the destination port into the struct (I checked using gdb). I'm interested
to see if anyone knows another way, otherwise the only way I can see this
working is using a per-port configuration option.

Steven

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.11/721 - Release Date: 13/03/2007
4:51 PM