2

I have a fedora core machine, and it is picking up an IPV6 address, but not an IPV4 address. I have done dhclient -r eth0 but the ipv4 address has not come. I have reset the port using ifconfig, but the address keeps coming up as an IPV6 address.

  • 1
    What version of Fedora are you using? Are you sure your network has IPv4? – mattdm Feb 29 '16 at 17:42
  • yes, I am sure the network uses IPV4, and this is Fedora Core 4. it was working properly until there was a power outage on Friday (lightning etc). – j0h Feb 29 '16 at 17:43
  • 4
    That's important information to not leave out, as you are talking about an OS released over a decade ago, and out of support for 9½ years! – mattdm Feb 29 '16 at 17:50
  • please add to the post the output of sudo ifconfig -a – Rui F Ribeiro Feb 29 '16 at 18:24
  • 3
    +1 for bravery. I would not put a hand on Fedora 4 when we have 24 on the way. – Jakuje Feb 29 '16 at 18:28
4

It's possible that the lightning strike destroyed the network port on your machine, and that the IPv6 address is a self-assigned address. Have you tried using the 'ping6' command to try pinging an outside IP address via IPv6 to really ensure that you've got IPv6 connectivity to the outside world?

Also, I concur with mattdm here -- FC4 is very old -- it's definitely worth looking to upgrade to a more modern version of Fedora.

0

It might be that you are looking at the wrong end of the cable, i.e., the router's DHCP server went AWOL for some reason (board/network card fried, configuration scrambled, cable is shot, ...).

As comments indicate, Fedora Core 4 is from the Jurassic, by now your average sieve has less known holes. You might want to look into some very-low-resource distribution, or upgrade both the machine and the distribution.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.