Hi,
You might want to have a look at IPVS for instance in combination with
Keepalived. You can then even use udp mounts if you want.
Just my 2 cents.
Regards,
Sander
> On 2 Aug 2018, at 18:40, Lucas Rolff wrote:
>
> I indeed removed the send-proxy - then I had to put the IP of haproxy
I indeed removed the send-proxy - then I had to put the IP of haproxy in the
NFS exports file instead to be able to mount the share (which makes sense seen
from a NFS perspective).
Making the NFS server support proxy protocol, isn't something I think will
happen - I rely on the upstream
On Thu, Aug 02, 2018 at 04:05:24AM +, Lucas Rolff wrote:
> Hi michael,
>
> Without the send-proxy, the client IP in the export would have to be the
> haproxy server in that case right?
That's it. But Michael is absolutely right, your NFS server doesn't support
the proxy protocol, and the
ct: Re: Using haproxy together with NFS
On Wed, Aug 1, 2018, 16:00 Lucas Rolff
mailto:lu...@lucasrolff.com>> wrote:
I use the “send-proxy” to let the NFS Server see the actual source IP, instead
of the haproxy machine IP.
You'll probably need remove that. Unless the destination servic
On Wed, Aug 1, 2018, 16:00 Lucas Rolff wrote:
>
> I use the “send-proxy” to let the NFS Server see the actual source IP,
> instead of the haproxy machine IP.
>
You'll probably need remove that. Unless the destination service
explicitly supports the Proxy Protocol (in which case, it must not, by
Hi guys,
I’ve been playing around today with two NFS servers (each on their own storage
array), synced by Unison to provide a bit higher uptime.
To allow NFS clients to use a single IP, I’ve configured an haproxy install (1
now, two when in prod), where I want to talk over tcp mode to the NFS
6 matches
Mail list logo
