Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforce matching frontend TCP/UDP ports for backends using IPVS droute/tun forwarding #19

Open
SpComb opened this issue Aug 29, 2016 · 0 comments
Labels

Comments

@SpComb
Copy link
Member

SpComb commented Aug 29, 2016

The clusterf ServiceFrontend and ServiceBackends can be configured with different TCP/UDP ports, which are used for the IPVS Service/Destination ports. However, it appears that only the IPVS masq forwarding method supports the use of a different port for the IPVS destination. For other methods such as droute and tun, the IPVS dest port is ignored and the packets are forwarded using the service port.

clusterf should warn about mismatching ports for those ServiceBackends using a route.IPVSMethod != "masq". The service port may even be used for some entirely different purpose on the backend, which would lead to interesting issues... such misconfigured backends should probably be omitted.

@SpComb SpComb added the TODO label Aug 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant