AW: Avoiding DNAT
Fri, 27 Jul 2001 09:01:27 +0200
You=B4re right, the ip is only submitted, if trhe request ran through a =
sorry for this .... :-( (its very hot in austria).
Intel Certified Integration Specialist Networking
Netzwerksysteme / Firewalls
Bricks Core Development
Von: Patrick Schaaf [mailto:firstname.lastname@example.org]
Gesendet: Freitag, 27. Juli 2001 08:57
An: Harald Scharf
Cc: 'Woody'; Netfilter Mailing List (E-Mail)
Betreff: Re: Avoiding DNAT
> There is nothig to do, because apache (you do use apache, don=B4t you =
> writes the logfile with the ip=B4s from the http header. (OSI Layer =
Sorry, but there is no client IP in the HTTP request headers.
If there were, I wouldn't trust it in any way (it would be
client-supplied, and easily fakeable). The exception to this
rule is clients which already ran through a web proxy - web proxies
tend to note the client IP in some header (e.g. X-Forwarded-For in =
But that's not part of the HTTP standard request, and not universal.
A solution to the original request, would be to run a reverse proxy
on the firewall machine, and have that reverse proxy do the logging.
A less intruding solution might be using the ULOG target to selectively
log the request packets as they fly by. It should be possible to write
an ULOG user level process which reassembles the TCP stream from client
to server. I don't know whether ULOG sees the original source, though,
so maybe this is not practical right now.