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

unable to connect via rpcbind behind NAT / docker port forwarding #41

Open
lmm-git opened this issue Mar 29, 2020 · 0 comments
Open

unable to connect via rpcbind behind NAT / docker port forwarding #41

lmm-git opened this issue Mar 29, 2020 · 0 comments

Comments

@lmm-git
Copy link

lmm-git commented Mar 29, 2020

This is expected behavior but it remains the port forwarding usage of rpcbind useless.

Background: With newer versions of rpcbind clients will use a newer protocol version. These versions will use the GETADDR call which returns the IP from the server on application level. As with a typical docker port forwarding we are doing a source NAT, the IP in response of GETADDR will not be equal to the external one and even worse, it is typically an unreachable address. So basically listing the exports is not possible with newer clients (depending on the version of rpcbind).

I do not have any idea how to fix that properly. But a note in the docs would be nice.

This image is pretty useful in some use cases but e.g. with newer versions of Proxmox it just doesn't work for non obvious reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant