-
Notifications
You must be signed in to change notification settings - Fork 44
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
Reliable access to services in network namespace #211
Comments
Hey, Could you explain the issue a little more? It should already be available on all interfaces IIRC since it binds to the unspecified address - https://github.com/jamesmcm/basic_tcp_proxy/blob/master/src/lib.rs#L22-L25 But it'd be good to have a small example to replicate the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have several services running in network namespaces with vopono that need to be reached from outside the network namespace and on the LAN and other network interfaces. Since the IP addresses of the network namespaces constantly change (seems to be dependent on startup order which can be different between restarts or when services are manually restarted) simply forwarding connections from 192.168.X.X to 10.200.1.X is not a proper solution.
Could vopono add a feature to open ports so that they are accessible on all network interfaces or a couple command line arguments to specify what other interfaces beside 10.200.1.X to bind to?
The text was updated successfully, but these errors were encountered: