eth0 going down (connection reset by peer, then connection refused)
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
eth0 going down (connection reset by peer, then connection refused)
I have a fresh install of slack 12.0 on a box on my lan, however from time to time, just like a woman, it ignores everything except ping packets if ping packets are the ipv4 equivalent of poking.
If I am ssh'd into the box I will recieve a connection reset by peer error (or browsing a mounted directory via samba), and after that about 5-10 minutes of "connection refused".
At first I thought it was because ipv6 and ipv4 were conflicting in attempting to control listen ports bound to 0.0.0.0, so I made ssh and samba use specific ipv4 IP addresses - that didn't seem to help.
There is only one network card in this box.
I am not experiencing the same problem on a fresh install of slack 10.2 on a different box (192.168.0.10 for those that are curious)
Anyway, here's the ifconfig info of the box in question
and if I ssh from the slack 10.2 box and i'm disconnected, here's the error message pertaining to what I'm talking about
root@isfrael:/media1# Read from remote host 192.168.0.11: Connection reset by peer
Connection to 192.168.0.11 closed.
omega@azhure:~$ ssh 192.168.0.11
ssh: connect to host 192.168.0.11 port 22: Connection refused
omega@azhure:~$
If there's any kind of logs I should be looking at (dmesg, /var/log/syslog and /var/log/messages don't tell me anything useful as far as I can tell) then I am more than happy to provide them.
Also note that during this time the box cheerfully responds to pings, unlike a woman (they tend to poke you back or hit you in my experience, quite uncheerfully)
oh, and i tried the ServerKeepAlive option in ssh_config, doesn't do much except keep ghost connections alive. For instance:-
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.