0

I am trying to connect to the internet with a wired ethernet.

The issue is my eth0 interface doesn't seem to get an IP address. The DCHP server is enabled on my router.

Wireless works fine! Same problem on my Raspberry Pi!

Here may be some useful info:

ifconfig

root@dimitris:/# ifconfig

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether blablabla  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

route -n

root@dimitris:/# route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    600    0        0 wlan1
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 br-e9207e6b0fa1
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-e9207e6b0fa1
192.168.1.0     0.0.0.0         255.255.255.0   U     600    0        0 wlan1

pinging net addr while only ethernet is cocnnected (wifi off)

root@dimitris:/# ping 192.168.1.1
    connect: Network is unreachable

root@dimitris:~# ip link show eth0 
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether ma:cc:ad:dr:es:ss brd ff:ff:ff:ff:ff:ff

Any ideas?

  • 1
    Can you include the output of ip link show eth0 while connected to cable in your question? – vidarlo Apr 13 at 9:56
  • root@dimitris:~# ip link show eth0 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether ma:cc:ad:dr:es:ss brd ff:ff:ff:ff:ff:ff – Dimitris Prasakis Apr 13 at 10:10
  • @vidarlo tag for the notificatiion ^^ – Dimitris Prasakis Apr 13 at 10:21
  • Ok. It shows NO-CARRIER, which means it has not detected link. It does not show LOWER-UP either. Can you edit your post to include lshw -c network? And are you certain that the cable is working? – vidarlo Apr 13 at 10:35
  • Thanks for you recommendation. Apparently the issue was that I needed some rest. I was plugging... a DSL cable, not an Ethernet cable facepalm. Thank you for your time. – Dimitris Prasakis Apr 13 at 16:28
0

Apparently the issue was that I was plugging... a DSL cable, instead of an Ethernet cable. facepalm

Always get enough sleep, guys... Always get enough sleep.

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.