14.2 Multilib Can't Even Ping Router but Current Works Fine. Why?
Greetings and thank you in advance for any suggestions
Recently my Main motherboard failed and I'm trying to deploy an older PC as a substitute until I can replace/repair my Main. Slackware Current (upon which this is being typed now) and other OpSys work fine but my Main is 14.2 MultiLib and though DHCPD gets the correct IP from my router, and "ifconfig" and "route" shows nearly identical parameters, in 14.2 I can ping myself, so Loopback is working, but I can't even ping my Gateway. I've spent more than a day trying to determine what is wrong or missing but without being at least able to get to my router, I'm stuck. What tests or changes can I make that might help me gather the information I need to fix this? FWIW here's some data from Current vs/ 14.2. CURRENT Code:
bash-4.4# ifconfig eth0 Code:
bash-4.3# ifconfig eth1 |
Code:
--- 10.0.0.1 ping statistics --- |
What does
Code:
# ip neigh |
Quote:
One factor to also consider is that I literally dropped the drives from my Main into this substitute and while the brand and model of the onboard nics is different, they both obviously work in some settings (different opsys/version) 14.2 worked before with the previous nic but doesn't with the "new",different nic even though it does with with current and other OpSys. I have no idea why it didn't just work in 14.2 without any alterations as it does in Current? How do I address the issue that it didn't send to it's own Gateway?.. and as an aside why would it require any changes given the network setup worked before? |
Quote:
Sorry to take so long but I had to install iproute2 since I don't upgrade my full installs unless I'm forced to, excepting security patches. I also had to familiarize myself with the "ip" command as it's new to me. I've known about it but always relied on ifconfig. In any case I had to familiarize myself with "ip" discovering I had to initiate some sort of contact first before it would register which, of course, it did on this Current <reachable>, but did not give any output for "neighbor" on 14.2. It did answer to "ip route" and "ip address" so at least I know it functions. On top of that I'm glad to discover the tool, thanks to your inquiry, as it has some of the power I'm seeking to even see let alone troubleshoot network data. I had tried to get "ipscan" from Slackbuilds.org but apparently a brief look-see says it needs jdk-8 and Oracle's oldest listed is now v12 so I stopped until I have more to go on. Anyway, TLDR, no output at all from "ip neighbor" (not sure it even accepted the abbreviation in the older version available for 14.2) So now what? |
Quote:
|
Thank you GazL. That actually worked. Why did this even ever occur?
|
Because of the old entry in that file, eth0 was still looking for your old hardware, which wasn't there. Your new interface was likely assigned to eth1 instead. Deleting the file lets the system regenerate it and assign 'eth0' to the new hardware.
|
Quote:
|
Quote:
|
All times are GMT -5. The time now is 02:53 AM. |