Advice in regards to configuration

Brandon Mallory brandonm at medent.com
Mon Mar 4 14:49:11 UTC 2019


I am new to NGINX and looking for advice on how to configure NGINX. 

Here is what I am trying to accomplish for my cloud infrastructure. 

Have NGINX configured with a public IP (65.x.x.x.) . I need to use TCP for my application ( not http ). I would like to have a client hit the public IP with a location ( 65.x.x.x.x\12345) and have that connection forwarded to a LAN IP. 

Example: 

Client1 - application hits 65.x.x.x./12345 port 11001 and that connection forwarded to a VM at 10.45.2.1:11001 
Client2 - application hits 65.x.x.x./56789 port 11001 and that connection forwarded to a VM at 10.45.2.2:11001 
Client3 - application hits 65.x.x.x./24681 port 11001 and that connection forwarded to a VM at 10.45.2.3:11001 


can anyone point me in the right direction from a configuration aspect. I think I need to use the stream option just not sure what other options I need to send a specific "location" to a specific server. I could also use subdomains if that is required (12345.65.X.X.X to 10.45.2.1) 

Thanks 
Best Regards, 
Brandon Mallory 
Network & Systems Engineer 
MEDENT EMR/EHR 
15 Hulbert Street 
Auburn, NY 13021 
Phone: [ callto:(315)-255-0900 | (315)-255-0900 ] 
Fax: [ callto:(315)-255-3539 | (315)-255-3539 ] 
Web: [ http://www.medent.com/ | www.medent.com ] 



This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently delete this e-mail. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190304/97f1dabd/attachment.html>


More information about the nginx mailing list