Re: relayd(8): transparent forward

2019-11-06 Thread mp1009
On 2019-11-06 08:25, Stuart Henderson wrote: On 2019/11/05 20:46, Mischa Peters wrote: When you are using transparent (Direct Server Return) you have to make sure you disable ARP on the servers you are load balancing. Transparent is not "direct server return", that is done with "route to".

Re: relayd(8): transparent forward

2019-11-05 Thread Mischa Peters
> On 6 Nov 2019, at 08:25, Stuart Henderson wrote: > > On 2019/11/05 20:46, Mischa Peters wrote: >> When you are using transparent (Direct Server Return) you have to make sure >> you disable ARP on the servers you are load balancing. > > Transparent is not "direct server return", that is do

Re: relayd(8): transparent forward

2019-11-05 Thread Stuart Henderson
On 2019/11/05 20:46, Mischa Peters wrote: > When you are using transparent (Direct Server Return) you have to make sure > you disable ARP on the servers you are load balancing. Transparent is not "direct server return", that is done with "route to". > What happens with transparant is that the se

Re: relayd(8): transparent forward

2019-11-05 Thread mp1009
Mischa, as you were guessing right, my sole intention was to have the actual client IP address available on the server side without changing anything in the current server configuration. With your explanation, I understand that in my case this is not possible. So, as you suggested, passing the cl

Re: relayd(8): transparent forward

2019-11-05 Thread Mischa Peters
What are you trying to do? When you are using transparent (Direct Server Return) you have to make sure you disable ARP on the servers you are load balancing. What happens with transparant is that the server gets the client IP as source, not the IP of relayd, and will respond directly to the cli