Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Dear All
My Linux server is at @172.16.17.100 and my remote equipment is at @172.16.17.110 located at far site . Both of my server and network equipment can have Internet access and I need to virtually put that network element on my Linux server LAN so I can touch it as I touch the other near side network elements . In my application I cannot change my server & remote network element ip addresses and as you see they are invalid ones . Can you please let me know which solutions are suitable for this purpose ?
Thank you in advance
The IP addresses aren't invalid, they're in one of the subnets reserved for LANs. Since they have private IPs and Internet access I assume that they're behind some sort of NAT gateway (in the SOHO market often called a router). Most gateways support port forwarding, a method by which they forward traffic arriving at a port on their public IP to a host on the LAN they serve. If you want specific help setting this up, we'll need your gateway's model number.
The IP addresses aren't invalid, they're in one of the subnets reserved for LANs. Since they have private IPs and Internet access I assume that they're behind some sort of NAT gateway (in the SOHO market often called a router). Most gateways support port forwarding, a method by which they forward traffic arriving at a port on their public IP to a host on the LAN they serve. If you want specific help setting this up, we'll need your gateway's model number.
Thank you very much for your reply . I am not sure about my Gateway model number and need to check it . According to you , it seems that there is no settings on my Linux server that can directly accomplish this . Am I right ? Please confirm.
Thank you
Not as such, no. Your server can (and probably does) run the OpenSSH daemon, which will listen on TCP port 22 for incoming connections. If the server is on a LAN, only hosts on that LAN can send packets to its IP. Therefore, only hosts on its LAN can initiate communicate with it.
TCP has two kinds of sockets: listeners an initiators. A listening socket sits around and waits for someone to send it a packet. An initiator opens a connection by sending a SYN packet to a listening socket. In SSH, the server is a listener and the client is an initiator. If the initiator can't get a packet to the listener, it can't open a connection. Thus you need to forward a port on the gateway (which the client can talk to) to the server (which the client otherwise can't see).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.