Hi, I am facing problem with my ethernet interface. Help Me!

Linuxlova · 10-12-2017, 04:38 AM

ifconfig
enp3s0 Link encap:Ethernet HWaddr b8:ae:ed:78:37:a3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:5968 errors:0 dropped:0 overruns:0 frame:0
TX packets:5968 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:654449 (654.4 KB) TX bytes:654449 (654.4 KB)

Shadow_7 · 10-12-2017, 04:41 AM

What problem?

$ sudo dhclient -4 -v enp3s0

Linuxlova · 10-12-2017, 04:48 AM

I cant connect using an ethernet connection.
Please tell me where to look
The output of command that you posted is:
sudo dhclient -4 -v enp3s0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp3s0/b8:ae:ed:78:37:a3
Sending on LPF/enp3s0/b8:ae:ed:78:37:a3
Sending on Socket/fallback
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 5 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 11 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 11 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 19 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 15 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 19 (xid=0x6175a66b)
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 15 (xid=0x6175a66b)

The output goes on like this

Linuxlova · 10-12-2017, 05:52 AM

Let me know if anything is required

Linuxlova · 10-12-2017, 05:57 AM

dmesg | grep -e eth -e r8169
[ 1.909946] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.909963] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.916985] r8169 0000:03:00.0 eth0: RTL8168h/8111h at 0xffffc900003e4000, b8:ae:ed:78:37:a3, XID 14100800 IRQ 310
[ 1.916990] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 2.018144] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 13.010611] r8169 0000:03:00.0 enp3s0: link down
[ 13.010628] r8169 0000:03:00.0 enp3s0: link down

michaelk · 10-12-2017, 06:00 AM

What linux distribution/version are you running?

How is the computer connected to your network?

jefro · 10-12-2017, 03:11 PM

Is it plugged in? Any lights on nic?

JeremyBoden · 10-12-2017, 04:56 PM

Quote:

Originally Posted by Linuxlova

dmesg | grep -e eth -e r8169
[ 1.909946] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.909963] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.916985] r8169 0000:03:00.0 eth0: RTL8168h/8111h at 0xffffc900003e4000, b8:ae:ed:78:37:a3, XID 14100800 IRQ 310
[ 1.916990] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 2.018144] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 13.010611] r8169 0000:03:00.0 enp3s0: link down
[ 13.010628] r8169 0000:03:00.0 enp3s0: link down

I have something similar - but different (no name changing going on)

Code:

dmesg | grep -e eth -e r8169
[    1.363834] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.363845] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[    1.364095] r8169 0000:02:00.0: irq 72 for MSI/MSI-X
[    1.364272] r8169 0000:02:00.0 eth0: RTL8168f/8111f at 0xffffc90000c70000, 2c:4d:54:4f:a1:06, XID 08000800 IRQ 72
[    1.364275] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   18.445915] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168f-1.fw
[   18.539604] r8169 0000:02:00.0 eth0: link down
[   18.539620] r8169 0000:02:00.0 eth0: link down
[   18.539701] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.033989] r8169 0000:02:00.0 eth0: link up
[   21.034002] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Depending on your version of Linux, you may just need some firmware for the ethernet connection.

frankbell · 10-12-2017, 07:59 PM

Please provide some additional detail. For example:

Are you trying to connect via ethernet cable or wireless? DHCP or static ip?

If ethernet, have you checked that the cable is properly seated at both ends? If so, try substituting a known-good cable.

If wireless, it would appear that the wireless chipset is not detected (there is no WLAN0). Running the command lspci in a terminal should show which wireless chipset is installed.

The more information you provide, the easier it is for others to help you.

Shadow_7 · 10-13-2017, 03:36 AM

# mii-tool enp3s0

You might be missing firmware as previously suggested.

$ dmesg | grep -i firmware

Otherwise you have bad hardware. Missing or bad ethernet cable? The machine on the other end of the cable doesn't have it's interface configured, or any number of potentials.

# arp -vn -i enp3s0

Might help you see what's on the other side of the cable in case you need to static IP your configuration.

X-LFS-2010 · 10-13-2017, 02:25 PM

+1 didn't say what linux

the ifconfig line proves linux "likes" the nebulous network attachment

> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

proves no traffic on the interface

run dhclient, yes

$ routed # may help you out

plug in your cable, check if lights light up on both sides and blink (damn i hate chinese cards without the traffic light!)

are you CAT5 cable attaching, usb, wifi?

lan cables are mass produced and often fail. you might have, say, two bad cables not just one bad cable

i assumed you tried pinging your in-home router to the internet (do so when checking your lights, and RX/TX will increment if any packets are sent/received successfully)

scasey · 10-14-2017, 05:08 PM

Quote:

Originally Posted by Linuxlova

ifconfig
enp3s0 Link encap:Ethernet HWaddr b8:ae:ed:78:37:a3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

An observation: enp3s0 appears to have no IP address [inet addr:] configured...

AwesomeMachine · 10-15-2017, 12:31 AM

Yes, that is the problem. The interface has no IP. Is it attached to a DHCP server, like a router or ISP? Are you using network-manager?