You are not logged in.
- Topics: Active | Unanswered
#1 2020-06-11 04:14:36
- noblesseoblige22
- Member
- Registered: 2020-06-11
- Posts: 1
Unable to connect to ethernet
It works on my windows 10 partition.
Right now I'm connected over wifi, I hope that doesnt affect the results of my commands.
ip link gives me:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 94:de:80:0b:a5:14 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether d0:ab:d5:a2:f8:be brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:ba:2d:58:0e brd ff:ff:ff:ff:ff:ff
5: br-3ad87e374711: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 02:42:e8:e0:27:e7 brd ff:ff:ff:ff:ff:ff
7: veth53b661b@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-3ad87e374711 state UP mode DEFAULT group default
link/ether b2:34:68:6e:a9:97 brd ff:ff:ff:ff:ff:ff link-netnsid 0
9: vetheb5646f@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-3ad87e374711 state UP mode DEFAULT group default
link/ether 4a:9c:9d:1e:d4:f6 brd ff:ff:ff:ff:ff:ff link-netnsid 3
11: veth09bed8c@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-3ad87e374711 state UP mode DEFAULT group default
link/ether a2:5c:1f:0e:fe:52 brd ff:ff:ff:ff:ff:ff link-netnsid 1
13: veth69974d9@if12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-3ad87e374711 state UP mode DEFAULT group default
link/ether 6a:ae:df:73:b8:c5 brd ff:ff:ff:ff:ff:ff link-netnsid 2
I have docker installed if that helps, wondering if maybe it's interfering?
I believe my device for ethernet is enp4s0 but I don't know.
Tell me o arch wizards what spell I ought cast.
Offline
#2 2020-06-11 05:58:32
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,945
Re: Unable to connect to ethernet
Please wrap the output in "code" tags.
enp4s0 is your wired ethernet NIC and "NO-CARRIER" generally suggests a lack of "wire".
Other than that, please read https://bbs.archlinux.org/viewtopic.php?id=57855 and elaborate on "Unable to connect" - how do you attempt it, what are the error messages/symptoms etcetc.
As for "works on my windows 10", please see the third link in my signature.
As generic advice: try to connect via ethernet and dump the output of "ip a; ip r" and if you already wonder whether docker is interfering, stop wondering and check by getting it out of the equation.
Offline