Find the answer to your Linux question:
Results 1 to 3 of 3
problem: Trying to ping router 192.168.1.1, saying network unreachable (or not reachable, forgot exact word). doing Code: dmesg | grep eth | less Returning at the last a line like: ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie imranka's Avatar
    Join Date
    Dec 2007
    Location
    Kolkata
    Posts
    181

    [SOLVED] Network unreachable: cannot ping router


    problem:

    Trying to ping router 192.168.1.1, saying network unreachable (or not reachable, forgot exact word).

    doing
    Code:
    dmesg | grep eth | less
    Returning at the last a line like: no ipv6 router present.

    Doing
    Code:
    lspci -vv | grep -i eth
    Returning the Intel ethernet card that I have.

    Doing

    Code:
    /sbin/ifconfig -a
    doesn't return any inet , bcast, mask addresses.

    Now, first I thought the ethernet cable was not working, so I took my router and the cable and connected in other person's machine, but there the router page opened properly. Now, he told me, that the lancard may got fried. Another person told me to check the etherent port.

    Now, I am very confused, how to troubleshoot this? Biggest problem is that, I don't have internet by my side to check immediately this forums or anything.

    Any suggestion please....
    Imran
    Linux User #467555 | Debian Squeeze | Intel(R) Core(TM)2 Duo CPU 4500 @ 2.20GHz | Gigabyte GA-G41MT-ES2L
    | 2 GB RAM | 320 GB SATA | Kernel: 2.6.32-5-686

  2. #2
    Linux Engineer RobinVossen's Avatar
    Join Date
    Aug 2007
    Location
    The Netherlands
    Posts
    1,429
    Request DHCP?
    Or set IP by hand.
    Also try mii-tool if you think the Eth-card /cable is broken
    New Users, please read this..
    Google first, then ask..

  3. #3
    Linux Newbie imranka's Avatar
    Join Date
    Dec 2007
    Location
    Kolkata
    Posts
    181
    After many forum hopping I understood this can be because of configuration related issues also. So, I followed one solution, and checked my /etc/network/interfaces file and saw many garbage line was sitting there, cleaning the file and kept only

    Code:
    auto lo
    iface lo inet loopback
    solved the problem.

    This is a new learning, a problem which seems like hardware issue is just a config problem.
    Imran
    Linux User #467555 | Debian Squeeze | Intel(R) Core(TM)2 Duo CPU 4500 @ 2.20GHz | Gigabyte GA-G41MT-ES2L
    | 2 GB RAM | 320 GB SATA | Kernel: 2.6.32-5-686

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •