Linux - Server This forum is for the discussion of Linux Software used in a server related context. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
05-04-2011, 06:05 AM
|
#1
|
LQ Newbie
Registered: Dec 2010
Posts: 12
Rep:
|
NAT Local Network
Hi all,
First let me explain the situation.
There is in the DMZ a NAT Server, behind the NAT Server is a vritual switch that is connected with a Network environment that called the live environment. Here are a lot of virtual servers.
If you want to communicate with the virual servers, outside the company, works with portforwarding.
The issue is, there is also a test environment in the trusted zone. From this place we must deploy ruby on rails applications to the live environment. Normally will this work with SSH, port 23. The question is now how can I be sure that I connect with SSH to the correct virtual server behind the NAT server.
I hope everything is a bit clear and you all understand it.
Greetings Mark
|
|
|
05-04-2011, 06:13 AM
|
#2
|
Member
Registered: Aug 2007
Location: INDIA
Distribution: CentOS, RHEL, Fedora, Debian, Ubuntu, LinuxMint, Kali Linux, Raspbian
Posts: 166
Rep:
|
1. you can differentiate them with Server Name
2. If you don't want to change the name of the server, Create text file on root (/) or home directory of all (test and live) server and write the environment like TEST or LIVE inside the file.
|
|
|
05-04-2011, 08:46 AM
|
#3
|
LQ Newbie
Registered: Dec 2010
Posts: 12
Original Poster
Rep:
|
Your second point is not clear for my, please explain it
Your first point Server Name? you mean domain name?
|
|
|
05-04-2011, 09:05 AM
|
#4
|
Senior Member
Registered: Jul 2007
Distribution: Gentoo
Posts: 2,125
|
Quote:
Your second point is not clear for my, please explain it
|
I believe that they meant that you can create a file and stick it in an obvious place and then look for that file. Put something in the file that will be meaningful to you as far as telling you what machine it is.
Quote:
Your first point Server Name? you mean domain name?
|
Not quite, rather the host name. The server should have a fully qualified name which is host@domain. Presumably all your machines will have the same domain name, but each one should have a unique host name.
|
|
|
All times are GMT -5. The time now is 11:45 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|