iphash1? My basic understanding is that
iphashtries to route all requests from a specific client IP to the same backend. The docs say
"same as iphash but backend removal consistent (clients remain connecting to the same backend, even if some other backends down)". Why should
iphashworry about other backends going down, as long as the backend mapped to the client IP is up, it can keep connecting to the same backend, can't it?
Why should iphash worry about other backends going down, as long as the backend mapped to the client IP is up
There's no mapping, that's why ;)
Hi guys, first thanks for your fantastic work, I'm actually using your LB to forward system log to elasticsearch. I've seen there was a question about keeping the source IP.
Sure, right now we have a syslog stream which is forwarded by two nginx nodes to two logstash nodes. If we dont have the nginx option mentioned before, elastic will think that the syslog is commin from the nginx node. By issuing the option above it keeps the source IP when its forwarded and lets elastic find out the real source IP of the syslog
Hi all. I'm trying to set up a reverse proxy udp load balancer for syslog. I've found the following documentation.
transparent = false # (optional) [NOTE: does not work for Windows] if true - work in transparent mode, when forwarded udp packets have client source address (requires additional host configuration) (since 0.8.0)
Would anyone know where the "additional host configuration" documentation would be?
v0.8.0 released: https://github.com/yyyar/gobetween/releases/tag/0.8.0
Just want to remind for those who have questions, maintainers are more active in telegram channel: https://t.me/joinchat/GdlUlg_gRfchk1BORU82PA sorry for being unresponsive sometimes.