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.
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Rep:
Networking question - Connecting 2 Linux boxes.
I'm trying to connect two Linux boxes :
Machine 1 : Red Hat 9.0
Machine 2 : Red Hat 8.0
Both have network cards and they are connected by a crossover patch cable.
I've issued the following commands:
Code:
Machine 1 : ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
Machine 2 : ifconfig eth0 192.168.0.2 netmask 255.255.255.0 up
Fine no problems there as I can ping from either machine. I've tried using telnet/ssh from both machines and cannot connect to the other ( connection timed out). Do I have to modify certain conf files to use these services ?
There are no firewalls /iptables etc running on either machine. I've checked the xinetd file and the services have not been stopped.
I basically want to telnet / rlogin / ssh / sftp from either machine and work on the other - maybe setup ftp at some point.
The machines are not and will not be connected to the Internet.
Thanks
Uncle.
ps: I assumed this was a "newbie" question. Apologies if it should have been posted on the "Networking" forum.
You can ping, so your network is OK, a good start.
Next, make sure you have ssh installed and running on both machines: ps -A | grep ssh should show the sshd running, if not you'll have to start it.
Edit Oh, and don't try ssh-ing as root - this is usually disabled/forbidden.
that primary suggests that there is either a firewall running as you seem to have covered already, or there is no service running to connect to.
note xinetd is only going to affect rlogin and telnet, not worthwhile services like ssh. id' suggest solely worrying about ssh to start with. can you ssh to either box on the box itself? try using both the 192.168 ip and also 127.0.0.1 for the loopback interface.
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Original Poster
Rep:
SSH service was running on both machines. I think the ssh connection may not have worked as I was running as root. When switching to a regular user the connection and login was successful. I ran the ipconfig lo 127.0.0.1 on both machines for good measure. Not sure if that made any difference. There is one problem still bugging me and that is about "telnet." When on either machine I still cannot telnet to 127.0.0.1 or 192.168.ip - keeping getting the error message "cannot connect to server." I assume this is because the telnet daemon may not be running ? SSH has made telnet redundant in my case but it would be intruging to know why the latter is not working.
I still cannot telnet to 127.0.0.1 or 192.168.ip - keeping getting the error message "cannot connect to server."
If it's any consolation, I get the same, and I have xinetd running (not certain what it does though!). But I'm not worried as ssh really is the way to go!
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Original Poster
Rep:
Excellent !! I'll give partying a miss tonight and get into some hardcore ssh manuals !!! This was one of the reasons why I wanted to link two linux boxes together. Gives you the ideal opportunity to experiment without getting into trouble with the Sys Admins at work
This was one of the reasons why I wanted to link two linux boxes together.
I feel sorry for you, as this is how I started ("I wonder if I can get these 2 boxes to talk to one another somehow...?").
Key: "->" = "leads to"
Crossover cable -> Internet Router / Switch -> Firewalls -> More computers -> More distributions -> Remote desktops (so I can play with them all!) -> Networked printers -> Wireless (locked-down & encrypted of course) -> I probably need Psychotherapy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.