Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Hi Folks,
I am unable to SSH to RHEL4 on eth0 which is having an IP, lets say 10.1.0.1. But at the same time eth1 (10.1.0.2) is working fine. And if I assign 10.1.0.2 on eth0 that's working fine. In other way if I assign 10.1.0.1 on eth1 it works.
No IPTABLES, TCP Wrapper or SELinux is enabled. Please help. Tried SSH restart and even reboot.
In the remote machine it's giving the error "ssh_exchange_identification: read: Connection reset by peer". And in TCPDUMP we found the same TCP RESET flag during Handshake. Machine is behind a vLAN with no ACLs or restrictions.
Hi Chris,
We were running with a single IP on eth0. Just for troubleshooting purpose we configured eth1 with a new IP. We did a ifdown eth1 after that. And one more thing, if we create eth0:0 it works like a charm.
Thanks for our reply. In hope of some tricks here....
well a trick would be to NOT use multiple interfaces on the same network. do as you did eht eth0:0 instead, or if you do want two physical interfaces, then a bond module making eth0 and eth1 into a bond0 interface, and then haave a bond0 and a bond0:0.
Take a look at route and you will probably see one nic is set as the gateway for both IPs. That would explain why it worked as eth0:0 but not as eth1.
If this doesn't explain it post the output of ifconfig and route and make certain there is no firewalling in place. Are the connected to the same switch? What is the IP of the other machine?
More information is needed to be certain of the problem.
Thanks a lot for your reply.
I really don't want 2 NICs as mentioned in the previous post. Just for ensuring there is no problem with SSH I tried enabling it. Now it has been removed.
And then, the problematic machine and the client machines are connected to the same switch. Even the eth1 was connected to the same Switch. There is no network firewall, IPTABLES, TCP Wrapper or SELinux. And the SSH was working previously. All of a sudden it got stuck. I don't remember any change in the server recently in these days of issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.