Quote:
Originally Posted by nimnull22
post the output for: route -n
Thanks
|
0.0.0.0 x.y.z.1 0.0.0.0 UG 0 0 0 eth1
x.y.z.0 0.0.0.0 255.255.255.240 U 0 0 eth1
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 eth0
so, that is ok.
I tried other solutions:
First, I checked cable type. It was straight-through cable, so this was not cause of the problem.
After that, I decided to do power-cycling. But when I've opened the rack, there was a huge mess in it, at least 10 network devices with mass of cables and wires. It was nothing labeled (I don't know why) so I concluded that it easier for me to change NICs between Debian and Win server and find out what will happen. If the MAC learning is a problem, this will solve it. But after I change NICs between servers, unexpected problem arised: kernel did not recognized a new NIC. This problem could probably be solved by adding some kernel modules, or in similar way, but with no working internet connection I couldn't find the proper way to do it. So I decided to reinstall Debian with new NIC in the box. After that, kernel have racognized the NIC, and it's LEDs start to show some activity. Finally, I coud ping x.y.z.1. So, link is ok.
But, when I've tried to ping a nameserver's IP in provider's network, I haven't got any response! I tried to traceroute a nameserver's IP, and I've got 4 hops, all inside provider's network, after i've got stars (* * * and last response * *). I tried to ping the second hop and the third hop, it was ok, but I didn't get any response when I tried to ping the fourth hop!
Is there any possible kernel parametres which I shoud set? Should I set some parametres inside sysctl.conf?
Anyway, thenks for the answers.