eth: error fetching interface information: Device not found
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I have an ubuntu 18.04 linux server.
Why does the command(ifconfig eth
) says Device not found whereas this command(ifconfig eth0
) works?
$ ifconfig eth
eth: error fetching interface information: Device not found
$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 96.114.208.69 netmask 255.255.255.128 broadcast
96.114.208.127
inet6 fe80::8a9:12ff:fe5b:c324 prefixlen 64 scopeid 0x20<link>
ether 0a:a9:12:5b:c3:24 txqueuelen 1000 (Ethernet)
RX packets 5126229 bytes 7622036755 (7.6 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1823543 bytes 124228703 (124.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note: I tried the same thing on my other 14.04 linux server. Both commands are working
ubuntu ifconfig interface
add a comment |Â
up vote
-1
down vote
favorite
I have an ubuntu 18.04 linux server.
Why does the command(ifconfig eth
) says Device not found whereas this command(ifconfig eth0
) works?
$ ifconfig eth
eth: error fetching interface information: Device not found
$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 96.114.208.69 netmask 255.255.255.128 broadcast
96.114.208.127
inet6 fe80::8a9:12ff:fe5b:c324 prefixlen 64 scopeid 0x20<link>
ether 0a:a9:12:5b:c3:24 txqueuelen 1000 (Ethernet)
RX packets 5126229 bytes 7622036755 (7.6 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1823543 bytes 124228703 (124.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note: I tried the same thing on my other 14.04 linux server. Both commands are working
ubuntu ifconfig interface
Post the output from the working system
â Raman Sailopal
Aug 17 at 12:11
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have an ubuntu 18.04 linux server.
Why does the command(ifconfig eth
) says Device not found whereas this command(ifconfig eth0
) works?
$ ifconfig eth
eth: error fetching interface information: Device not found
$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 96.114.208.69 netmask 255.255.255.128 broadcast
96.114.208.127
inet6 fe80::8a9:12ff:fe5b:c324 prefixlen 64 scopeid 0x20<link>
ether 0a:a9:12:5b:c3:24 txqueuelen 1000 (Ethernet)
RX packets 5126229 bytes 7622036755 (7.6 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1823543 bytes 124228703 (124.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note: I tried the same thing on my other 14.04 linux server. Both commands are working
ubuntu ifconfig interface
I have an ubuntu 18.04 linux server.
Why does the command(ifconfig eth
) says Device not found whereas this command(ifconfig eth0
) works?
$ ifconfig eth
eth: error fetching interface information: Device not found
$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 96.114.208.69 netmask 255.255.255.128 broadcast
96.114.208.127
inet6 fe80::8a9:12ff:fe5b:c324 prefixlen 64 scopeid 0x20<link>
ether 0a:a9:12:5b:c3:24 txqueuelen 1000 (Ethernet)
RX packets 5126229 bytes 7622036755 (7.6 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1823543 bytes 124228703 (124.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note: I tried the same thing on my other 14.04 linux server. Both commands are working
ubuntu ifconfig interface
ubuntu ifconfig interface
edited Aug 17 at 12:48
GAD3R
22.8k154895
22.8k154895
asked Aug 17 at 11:42
Nani
173
173
Post the output from the working system
â Raman Sailopal
Aug 17 at 12:11
add a comment |Â
Post the output from the working system
â Raman Sailopal
Aug 17 at 12:11
Post the output from the working system
â Raman Sailopal
Aug 17 at 12:11
Post the output from the working system
â Raman Sailopal
Aug 17 at 12:11
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
Because you don' t have any eth
device, but you have the eth0
.
If you use ifconfig -a
or ip addr
you can see all the devices available.
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output ofifconfig -a
?
â Scorpion
Aug 17 at 19:00
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Because you don' t have any eth
device, but you have the eth0
.
If you use ifconfig -a
or ip addr
you can see all the devices available.
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output ofifconfig -a
?
â Scorpion
Aug 17 at 19:00
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
add a comment |Â
up vote
2
down vote
Because you don' t have any eth
device, but you have the eth0
.
If you use ifconfig -a
or ip addr
you can see all the devices available.
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output ofifconfig -a
?
â Scorpion
Aug 17 at 19:00
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Because you don' t have any eth
device, but you have the eth0
.
If you use ifconfig -a
or ip addr
you can see all the devices available.
Because you don' t have any eth
device, but you have the eth0
.
If you use ifconfig -a
or ip addr
you can see all the devices available.
edited Aug 17 at 16:09
RobotJohnny
675216
675216
answered Aug 17 at 12:19
Scorpion
543
543
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output ofifconfig -a
?
â Scorpion
Aug 17 at 19:00
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
add a comment |Â
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output ofifconfig -a
?
â Scorpion
Aug 17 at 19:00
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
on ubuntu 14.04 server, both commands returns same output
â Nani
Aug 17 at 14:03
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073083 errors:0 dropped:0 overruns:0 frame:0 TX packets:17790249 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628310363 (628.3 MB) TX bytes:25682765383 (25.6 GB)
â Nani
Aug 17 at 14:05
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
ubuntu@ip-96-114-208-17:~$ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 0a:c6:8c:f3:88:84 inet addr:96.114.208.17 Bcast:96.114.208.127 Mask:255.255.255.128 inet6 addr: fe80::8c6:8cff:fef3:8884/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 RX packets:3073247 errors:0 dropped:0 overruns:0 frame:0 TX packets:17792171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628338790 (628.3 MB) TX bytes:25685051888 (25.6 GB)
â Nani
Aug 17 at 14:06
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output of
ifconfig -a
?â Scorpion
Aug 17 at 19:00
In the question you said that the output is different and that you are using ubuntu 18.04 server and not the 14.04. What is the output of
ifconfig -a
?â Scorpion
Aug 17 at 19:00
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
@Nani it's probably a good idea to omit your public IP address from your PS1 (since it contains your IP) and the output of ifconfig. Also formatting in a comment can be difficult to read, so you would likely get a better response if you're to amend your question with those outputs rather than in the comments :)
â RobotJohnny
Aug 20 at 8:13
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f463170%2feth-error-fetching-interface-information-device-not-found%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post the output from the working system
â Raman Sailopal
Aug 17 at 12:11