Ubuntu 16.04 ethernet issue: cannot ping IP address












0















I am new to Ubuntu and recently lost internet connection - cannot connect to 8.8.8.8 or google.com. I open the network manager and it says I'm connected with the correct hardware address and IP Address fe80::1037:4526:e2b:d5c3 . However, this is not the IP address of my ethernet router. Here are the output of some relevant commands:



$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 98:90:96:a5:d7:ae brd ff:ff:ff:ff:ff:ff
inet6 fe80::1037:4526:e2b:d5c3/64 scope link
valid_lft forever preferred_lft forever

$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

$dmesg |grep eth0
[ 1.603310] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 98:90:96:a5:d7:ae
[ 1.603311] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.603348] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 1.603863] e1000e 0000:00:19.0 enp0s25: renamed from eth0

$sudo lshw -c network
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: enp0s25
version: 05
serial: 98:90:96:a5:d7:ae
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:28 memory:fb100000-fb11ffff memory:fb139000-fb139fff ioport:f020(size=32)

$ ifconfig -a
enp0s25 Link encap:Ethernet HWaddr 98:90:96:a5:d7:ae
inet6 addr: fe80::1037:4526:e2b:d5c3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10151 errors:0 dropped:0 overruns:0 frame:0
TX packets:728 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1715192 (1.7 MB) TX bytes:154706 (154.7 KB)
Interrupt:20 Memory:fb100000-fb120000

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:23808 errors:0 dropped:0 overruns:0 frame:0
TX packets:23808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1798264 (1.7 MB) TX bytes:1798264 (1.7 MB)

$ more /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

$ vi etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


It seems odd that the route output is blank and also that the eth0 device is missing from interfaces. How can I get connected? Thanks!










share|improve this question







New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • You're not gettng an IPv4 address. Power down the computer, router, and dsl/cable modem. Power them back on in reverse order, with 15 seconds wait in between. Understand that this may take a little time to troubleshoot. Report back to @heynnema

    – heynnema
    3 hours ago











  • I'm working in a university so I cannot control beyond my own computer. I am able to connect on the same computer but on my Windows partition. Rebooting the Ubuntu OS does not change the problem. What should the appropriate network settings be for the IPv4 panel of network manager?

    – Scott Sterrett
    1 hour ago
















0















I am new to Ubuntu and recently lost internet connection - cannot connect to 8.8.8.8 or google.com. I open the network manager and it says I'm connected with the correct hardware address and IP Address fe80::1037:4526:e2b:d5c3 . However, this is not the IP address of my ethernet router. Here are the output of some relevant commands:



$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 98:90:96:a5:d7:ae brd ff:ff:ff:ff:ff:ff
inet6 fe80::1037:4526:e2b:d5c3/64 scope link
valid_lft forever preferred_lft forever

$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

$dmesg |grep eth0
[ 1.603310] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 98:90:96:a5:d7:ae
[ 1.603311] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.603348] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 1.603863] e1000e 0000:00:19.0 enp0s25: renamed from eth0

$sudo lshw -c network
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: enp0s25
version: 05
serial: 98:90:96:a5:d7:ae
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:28 memory:fb100000-fb11ffff memory:fb139000-fb139fff ioport:f020(size=32)

$ ifconfig -a
enp0s25 Link encap:Ethernet HWaddr 98:90:96:a5:d7:ae
inet6 addr: fe80::1037:4526:e2b:d5c3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10151 errors:0 dropped:0 overruns:0 frame:0
TX packets:728 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1715192 (1.7 MB) TX bytes:154706 (154.7 KB)
Interrupt:20 Memory:fb100000-fb120000

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:23808 errors:0 dropped:0 overruns:0 frame:0
TX packets:23808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1798264 (1.7 MB) TX bytes:1798264 (1.7 MB)

$ more /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

$ vi etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


It seems odd that the route output is blank and also that the eth0 device is missing from interfaces. How can I get connected? Thanks!










share|improve this question







New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • You're not gettng an IPv4 address. Power down the computer, router, and dsl/cable modem. Power them back on in reverse order, with 15 seconds wait in between. Understand that this may take a little time to troubleshoot. Report back to @heynnema

    – heynnema
    3 hours ago











  • I'm working in a university so I cannot control beyond my own computer. I am able to connect on the same computer but on my Windows partition. Rebooting the Ubuntu OS does not change the problem. What should the appropriate network settings be for the IPv4 panel of network manager?

    – Scott Sterrett
    1 hour ago














0












0








0








I am new to Ubuntu and recently lost internet connection - cannot connect to 8.8.8.8 or google.com. I open the network manager and it says I'm connected with the correct hardware address and IP Address fe80::1037:4526:e2b:d5c3 . However, this is not the IP address of my ethernet router. Here are the output of some relevant commands:



$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 98:90:96:a5:d7:ae brd ff:ff:ff:ff:ff:ff
inet6 fe80::1037:4526:e2b:d5c3/64 scope link
valid_lft forever preferred_lft forever

$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

$dmesg |grep eth0
[ 1.603310] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 98:90:96:a5:d7:ae
[ 1.603311] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.603348] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 1.603863] e1000e 0000:00:19.0 enp0s25: renamed from eth0

$sudo lshw -c network
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: enp0s25
version: 05
serial: 98:90:96:a5:d7:ae
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:28 memory:fb100000-fb11ffff memory:fb139000-fb139fff ioport:f020(size=32)

$ ifconfig -a
enp0s25 Link encap:Ethernet HWaddr 98:90:96:a5:d7:ae
inet6 addr: fe80::1037:4526:e2b:d5c3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10151 errors:0 dropped:0 overruns:0 frame:0
TX packets:728 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1715192 (1.7 MB) TX bytes:154706 (154.7 KB)
Interrupt:20 Memory:fb100000-fb120000

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:23808 errors:0 dropped:0 overruns:0 frame:0
TX packets:23808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1798264 (1.7 MB) TX bytes:1798264 (1.7 MB)

$ more /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

$ vi etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


It seems odd that the route output is blank and also that the eth0 device is missing from interfaces. How can I get connected? Thanks!










share|improve this question







New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I am new to Ubuntu and recently lost internet connection - cannot connect to 8.8.8.8 or google.com. I open the network manager and it says I'm connected with the correct hardware address and IP Address fe80::1037:4526:e2b:d5c3 . However, this is not the IP address of my ethernet router. Here are the output of some relevant commands:



$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 98:90:96:a5:d7:ae brd ff:ff:ff:ff:ff:ff
inet6 fe80::1037:4526:e2b:d5c3/64 scope link
valid_lft forever preferred_lft forever

$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

$dmesg |grep eth0
[ 1.603310] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 98:90:96:a5:d7:ae
[ 1.603311] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.603348] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 1.603863] e1000e 0000:00:19.0 enp0s25: renamed from eth0

$sudo lshw -c network
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: enp0s25
version: 05
serial: 98:90:96:a5:d7:ae
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:28 memory:fb100000-fb11ffff memory:fb139000-fb139fff ioport:f020(size=32)

$ ifconfig -a
enp0s25 Link encap:Ethernet HWaddr 98:90:96:a5:d7:ae
inet6 addr: fe80::1037:4526:e2b:d5c3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10151 errors:0 dropped:0 overruns:0 frame:0
TX packets:728 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1715192 (1.7 MB) TX bytes:154706 (154.7 KB)
Interrupt:20 Memory:fb100000-fb120000

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:23808 errors:0 dropped:0 overruns:0 frame:0
TX packets:23808 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1798264 (1.7 MB) TX bytes:1798264 (1.7 MB)

$ more /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

$ vi etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


It seems odd that the route output is blank and also that the eth0 device is missing from interfaces. How can I get connected? Thanks!







16.04 networking ethernet






share|improve this question







New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 3 hours ago









Scott SterrettScott Sterrett

1




1




New contributor




Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Scott Sterrett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • You're not gettng an IPv4 address. Power down the computer, router, and dsl/cable modem. Power them back on in reverse order, with 15 seconds wait in between. Understand that this may take a little time to troubleshoot. Report back to @heynnema

    – heynnema
    3 hours ago











  • I'm working in a university so I cannot control beyond my own computer. I am able to connect on the same computer but on my Windows partition. Rebooting the Ubuntu OS does not change the problem. What should the appropriate network settings be for the IPv4 panel of network manager?

    – Scott Sterrett
    1 hour ago



















  • You're not gettng an IPv4 address. Power down the computer, router, and dsl/cable modem. Power them back on in reverse order, with 15 seconds wait in between. Understand that this may take a little time to troubleshoot. Report back to @heynnema

    – heynnema
    3 hours ago











  • I'm working in a university so I cannot control beyond my own computer. I am able to connect on the same computer but on my Windows partition. Rebooting the Ubuntu OS does not change the problem. What should the appropriate network settings be for the IPv4 panel of network manager?

    – Scott Sterrett
    1 hour ago

















You're not gettng an IPv4 address. Power down the computer, router, and dsl/cable modem. Power them back on in reverse order, with 15 seconds wait in between. Understand that this may take a little time to troubleshoot. Report back to @heynnema

– heynnema
3 hours ago





You're not gettng an IPv4 address. Power down the computer, router, and dsl/cable modem. Power them back on in reverse order, with 15 seconds wait in between. Understand that this may take a little time to troubleshoot. Report back to @heynnema

– heynnema
3 hours ago













I'm working in a university so I cannot control beyond my own computer. I am able to connect on the same computer but on my Windows partition. Rebooting the Ubuntu OS does not change the problem. What should the appropriate network settings be for the IPv4 panel of network manager?

– Scott Sterrett
1 hour ago





I'm working in a university so I cannot control beyond my own computer. I am able to connect on the same computer but on my Windows partition. Rebooting the Ubuntu OS does not change the problem. What should the appropriate network settings be for the IPv4 panel of network manager?

– Scott Sterrett
1 hour ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Scott Sterrett is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123911%2fubuntu-16-04-ethernet-issue-cannot-ping-ip-address%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Scott Sterrett is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Scott Sterrett is a new contributor. Be nice, and check out our Code of Conduct.













Scott Sterrett is a new contributor. Be nice, and check out our Code of Conduct.












Scott Sterrett is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1123911%2fubuntu-16-04-ethernet-issue-cannot-ping-ip-address%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

GameSpot

日野市

Tu-95轟炸機