"Default" ethernet port not responding to SSH any more
I have 2 NIC's on my server. I just recompiled the stock kernel and since then eth0, i cannot connect to the server via SSH, WINSCP, Webmin, or VMWARE console server. I can however do it on eth1. eth0 ip addy is what i added to dns and thats why i was using eth0. Both are static, and did not swap IP's. DNS still has the ip for eth0 and the dns name is pingable from another machine.
Im really stumped as to why this is happenning... would have figured if SSH port is listening that it would be listening on all eth's my ifconfig Code:
eth0 Link encap:Ethernet HWaddr 00:1C:23:CC:5A:7D Code:
tcp 0 0 *:time *:* LISTEN Not sure what else i could post that would help. i haven't changed any config files and i wouldn't even know which ones to change to have this occur. |
What error do you get when you try to connect to say SSH on eth0? Is it connection refused, or timeout ?
I will also check IPTABLES or any firewall rules. Post output of iptables-save to have a look. |
When i use putty and try to connect via SSH i get
Code:
Server Unexpectedly closed network connection |
Another thing i've noticed is that eth1 has become my "default" ethernet port. everything by default is going in or out of that port now instead of eth0.
Any idea's why that might be happening? |
Quote:
what does "iptables -L" say? |
Quote:
here's iptables output just for fun. :) Code:
Chain INPUT (policy ACCEPT) |
Quote:
But considering the message from putty, I think that there may be a problem with sshd. Regarding the "same driver" issue - check lsmod, it will tell you, which driver is used. If you use some kind of hotplug manager, the modules should be loaded correctly and when you see the NICs in ifconfig, they must be loaded correctly. Check sshd version - try updating sshd. |
iptables is not the problem.
i don't realy remember how it went with those 2 NIC's, only remeber that there were some strange problems. there is probably a way to get around this, unfortunately i can't help you. |
Solved
I figured out the problem.
i was checking out my route table and the default gateway was set for eth1 not eth0! once i changed it, everything worked as normal again. PS anyone know how to edit my title so i can add "solved" ? tried editing my first post title and it didn't change the title displayed in the forums. |
*puts foot in mouth
I think i spoke to soon, but i think i am on the right track. Once i changed the default gw it did work and then it stopped working. default gateway is still there but i still have to use the other nic's ip to connect via ssh. |
some investigating i've found this, but not sure if it is relevant.
route table from slack 12 box i'm having issues with Code:
Destination Gateway Genmask Flags Metric Ref Use Iface Code:
Destination Gateway Genmask Flags Metric Ref Use Iface |
Alright, lets hope i don't have to stick my other foot in my mouth.
i had to have both in there, which makes sense. Code:
Kernel IP routing table |
*Sticks other foot in mouth.... dang it!
it worked for a while and then quit. not sure what the deal is. |
Localnet is 127.0.0.0 which isn't something that should be on any interface but lo.
Use `route -n` instead. No host is likely to do what you want it to on a IP network with two interfaces in the same netblock. This is a limitation of IPv4. |
I have noticed that with Slackware 12, if you have more than one NIC in a box, then the assignment of eth0 and eth1 (etc) can change from one reboot to the next. I suspect that this is due to different timings of the cards becoming available on the bus after initialising.
The solution is to assign eth0, eth1 etc to MAC addresses in /etc/udev/rules.d/network-devices.rules. |
All times are GMT -5. The time now is 11:46 PM. |