If you are doing web traffic, then relayd can insert a HTTP header
into the inbound request, which is then visible to the backend
webserver.
For vanilla tcp connections, verbose logging on relay box and backend
together with ntp time syncing and some scripting foo should permit
reconstruction of the end-to-end connection. No pretty but should work.
/pete
On 24 Feb 2009, at 18:57, Falk Brockerhoff - smartTERRA GmbH wrote:
Hi,
I'm using relayd for loadbalancing incoming tcp traffic, works fine
like a charme :-)
But as relayd works like a proxy, in the log files of my
applications, there is always the ip address of the load balancing
node and not of the real client. Is there a way to have relayd have
all packets redirect like pf's rdr function instead of working like
a classical proxy?
Another way to reach the final goal is touse pf with rdr statements,
but in this case I haven't any check if the target node is available
or not.
Both solutions only make half of the way I want to go - any idea,
hints, suggestions?
Regards,
Falk
