On Friday 26 Jun 2015 at 09:51, Henry S. Thompson wrote:
logs will show the IP address that reached squid, ie. the source
address of the connection. If that was NATted, squid will never know
(and thus is not able to log) the original address before the NAT.
That's what I assumed, but
Leonardo Rodrigues writes:
Em 24/06/15 15:28, Henry S. Thompson escreveu:
I've searched the documentation and mailing list archives w/o success,
and am not competent to read the source, so asking here: what is
logged as the 'remotehost' in Squid logs when a request that has been
Antony Stone writes:
On Friday 26 Jun 2015 at 09:51, Henry S. Thompson wrote:
logs will show the IP address that reached squid, ie. the source
address of the connection. If that was NATted, squid will never know
(and thus is not able to log) the original address before the NAT.
On Friday 26 Jun 2015 at 10:42, Henry S. Thompson wrote:
Antony Stone writes:
It's entirely plausible (I'd even say common) for VPN clients to get
192.168 addresses; also if there's a NATting router in the path
and Squid is logging its address, that could easily be 192.168
I've searched the documentation and mailing list archives w/o success,
and am not competent to read the source, so asking here: what is
logged as the 'remotehost' in Squid logs when a request that has been
encapsulated, as in from a machine on a local network behind a router
implementing NAT, or
Em 24/06/15 15:28, Henry S. Thompson escreveu:
I've searched the documentation and mailing list archives w/o success,
and am not competent to read the source, so asking here: what is
logged as the 'remotehost' in Squid logs when a request that has been
encapsulated, as in from a machine on a
