How to fully reset network settings on 18.04?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I upgraded to Ubuntu 18.04 and suddenly I don't have internet on command line, wired nor wireless, some domains seem not to resolve, though ping 8.8.8.8
does work, but service networking status
is outputting error. I saw many tweaks here on askubuntu regarding the issue, with ifconfig
or /etc/network/interface
but none fully works. sudo service network-manager restart
does not work either.
My network is basically a mess. Is there a way to fully reset network settings to a functional one? How is it possible that Ubuntu is releasing a main distro with such a bug, since this is a hot topic around?
Edit:
output of ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:8c:fa:8a:7c:ba txqueuelen 1000 (Ethernet)
RX packets 12829 bytes 5924414 (5.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8755 bytes 1396496 (1.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 40521 bytes 4309970 (4.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40521 bytes 4309970 (4.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5e82:7f12:37f8:854f prefixlen 64 scopeid 0x20<link>
ether 34:de:1a:7f:93:1a txqueuelen 1000 (Ethernet)
RX packets 27441 bytes 22237443 (22.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18332 bytes 5607005 (5.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
output of ip addr && cat /etc/resolv.conf && sudo lshw -C Network
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:8c:fa:8a:7c:ba brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 34:de:1a:7f:93:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 84519sec preferred_lft 84519sec
inet6 fe80::5e82:7f12:37f8:854f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
# 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 8.8.8.8
nameserver 127.0.0.53
options edns0
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: eth0
version: 0c
serial: 00:8c:fa:8a:7c:ba
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
resources: irq:16 ioport:3000(size=256) memory:c1700000-c1700fff memory:c1400000-c1403fff
*-network
description: Wireless interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: wlan0
version: cb
serial: 34:de:1a:7f:93:1a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-45-generic firmware=17.948900127.0 ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:33 memory:c1600000-c1601fff
cat /etc/apt/sources.list
:
# deb cdrom:[Ubuntu 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
## Major bug fix updates produced after the final release of the
## distribution.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
deb http://archive.ubuntu.com/ubuntu bionic main universe restricted multiverse
## respective vendors as a service to Ubuntu users.
deb http://security.ubuntu.com/ubuntu/ bionic-security universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-updates universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-backports universe multiverse restricted main
deb http://archive.canonical.com/ubuntu bionic partner
# deb-src http://archive.canonical.com/ubuntu bionic partner
deb [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
# deb-src [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
networking 18.04 network-manager 18.10
|
show 11 more comments
I upgraded to Ubuntu 18.04 and suddenly I don't have internet on command line, wired nor wireless, some domains seem not to resolve, though ping 8.8.8.8
does work, but service networking status
is outputting error. I saw many tweaks here on askubuntu regarding the issue, with ifconfig
or /etc/network/interface
but none fully works. sudo service network-manager restart
does not work either.
My network is basically a mess. Is there a way to fully reset network settings to a functional one? How is it possible that Ubuntu is releasing a main distro with such a bug, since this is a hot topic around?
Edit:
output of ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:8c:fa:8a:7c:ba txqueuelen 1000 (Ethernet)
RX packets 12829 bytes 5924414 (5.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8755 bytes 1396496 (1.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 40521 bytes 4309970 (4.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40521 bytes 4309970 (4.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5e82:7f12:37f8:854f prefixlen 64 scopeid 0x20<link>
ether 34:de:1a:7f:93:1a txqueuelen 1000 (Ethernet)
RX packets 27441 bytes 22237443 (22.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18332 bytes 5607005 (5.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
output of ip addr && cat /etc/resolv.conf && sudo lshw -C Network
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:8c:fa:8a:7c:ba brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 34:de:1a:7f:93:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 84519sec preferred_lft 84519sec
inet6 fe80::5e82:7f12:37f8:854f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
# 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 8.8.8.8
nameserver 127.0.0.53
options edns0
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: eth0
version: 0c
serial: 00:8c:fa:8a:7c:ba
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
resources: irq:16 ioport:3000(size=256) memory:c1700000-c1700fff memory:c1400000-c1403fff
*-network
description: Wireless interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: wlan0
version: cb
serial: 34:de:1a:7f:93:1a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-45-generic firmware=17.948900127.0 ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:33 memory:c1600000-c1601fff
cat /etc/apt/sources.list
:
# deb cdrom:[Ubuntu 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
## Major bug fix updates produced after the final release of the
## distribution.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
deb http://archive.ubuntu.com/ubuntu bionic main universe restricted multiverse
## respective vendors as a service to Ubuntu users.
deb http://security.ubuntu.com/ubuntu/ bionic-security universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-updates universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-backports universe multiverse restricted main
deb http://archive.canonical.com/ubuntu bionic partner
# deb-src http://archive.canonical.com/ubuntu bionic partner
deb [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
# deb-src [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
networking 18.04 network-manager 18.10
1
what's the output ofip addr && cat /etc/resolv.conf && sudo lshw -C Network
?
– AlexOnLinux
Feb 16 at 19:52
1
colbycdev mentiones a good point netplan. i do not have ubuntu 18 installed, so i can only refer to the manual either. Perhaps you have some old configurations in/etc/network/interfaces
that now are in conflict with the new system, i dont know. What suprises me is the fact that you recieve an ip from your AP. Yourresolv.conf
looks a littel strange to me, i would have expected your gateway / router ip in there - a line with the following content:nameserver 192.168.1.1
and another line withnameserver 127.0.1.1
. you say: "no internet via command line" - via browser it's working?
– AlexOnLinux
Feb 17 at 10:27
1
as nameserver you are actl using 8.8.8.8. thats google dns. in general that should work either. i dont understand why browsing works while terminal shouldn't. to me that makes no sense. are you sure your apt is pointing to the correct links for your upgraded ubuntu version? check your/etc/apt/sources.list
but i have to admit i am out of ideas. askubuntu.com/a/1036749/669014
– AlexOnLinux
Feb 17 at 12:36
1
Joao, i am really out of ideas. perhaps this is an IPv4 IPv6 problem. This would explain why sometimes connection works and sometimes it does not. Can you connect to this site ipv6-test.com does it show any errors regarding ipv4 or ipv6? You could test forcing ipv4 askubuntu.com/a/759540/669014 or disabling ipv6 askubuntu.com/a/484487/669014
– AlexOnLinux
Feb 17 at 15:51
1
Let us continue this discussion in chat.
– AlexOnLinux
Feb 17 at 17:34
|
show 11 more comments
I upgraded to Ubuntu 18.04 and suddenly I don't have internet on command line, wired nor wireless, some domains seem not to resolve, though ping 8.8.8.8
does work, but service networking status
is outputting error. I saw many tweaks here on askubuntu regarding the issue, with ifconfig
or /etc/network/interface
but none fully works. sudo service network-manager restart
does not work either.
My network is basically a mess. Is there a way to fully reset network settings to a functional one? How is it possible that Ubuntu is releasing a main distro with such a bug, since this is a hot topic around?
Edit:
output of ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:8c:fa:8a:7c:ba txqueuelen 1000 (Ethernet)
RX packets 12829 bytes 5924414 (5.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8755 bytes 1396496 (1.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 40521 bytes 4309970 (4.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40521 bytes 4309970 (4.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5e82:7f12:37f8:854f prefixlen 64 scopeid 0x20<link>
ether 34:de:1a:7f:93:1a txqueuelen 1000 (Ethernet)
RX packets 27441 bytes 22237443 (22.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18332 bytes 5607005 (5.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
output of ip addr && cat /etc/resolv.conf && sudo lshw -C Network
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:8c:fa:8a:7c:ba brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 34:de:1a:7f:93:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 84519sec preferred_lft 84519sec
inet6 fe80::5e82:7f12:37f8:854f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
# 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 8.8.8.8
nameserver 127.0.0.53
options edns0
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: eth0
version: 0c
serial: 00:8c:fa:8a:7c:ba
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
resources: irq:16 ioport:3000(size=256) memory:c1700000-c1700fff memory:c1400000-c1403fff
*-network
description: Wireless interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: wlan0
version: cb
serial: 34:de:1a:7f:93:1a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-45-generic firmware=17.948900127.0 ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:33 memory:c1600000-c1601fff
cat /etc/apt/sources.list
:
# deb cdrom:[Ubuntu 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
## Major bug fix updates produced after the final release of the
## distribution.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
deb http://archive.ubuntu.com/ubuntu bionic main universe restricted multiverse
## respective vendors as a service to Ubuntu users.
deb http://security.ubuntu.com/ubuntu/ bionic-security universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-updates universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-backports universe multiverse restricted main
deb http://archive.canonical.com/ubuntu bionic partner
# deb-src http://archive.canonical.com/ubuntu bionic partner
deb [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
# deb-src [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
networking 18.04 network-manager 18.10
I upgraded to Ubuntu 18.04 and suddenly I don't have internet on command line, wired nor wireless, some domains seem not to resolve, though ping 8.8.8.8
does work, but service networking status
is outputting error. I saw many tweaks here on askubuntu regarding the issue, with ifconfig
or /etc/network/interface
but none fully works. sudo service network-manager restart
does not work either.
My network is basically a mess. Is there a way to fully reset network settings to a functional one? How is it possible that Ubuntu is releasing a main distro with such a bug, since this is a hot topic around?
Edit:
output of ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:8c:fa:8a:7c:ba txqueuelen 1000 (Ethernet)
RX packets 12829 bytes 5924414 (5.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8755 bytes 1396496 (1.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 40521 bytes 4309970 (4.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40521 bytes 4309970 (4.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::5e82:7f12:37f8:854f prefixlen 64 scopeid 0x20<link>
ether 34:de:1a:7f:93:1a txqueuelen 1000 (Ethernet)
RX packets 27441 bytes 22237443 (22.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18332 bytes 5607005 (5.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
output of ip addr && cat /etc/resolv.conf && sudo lshw -C Network
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:8c:fa:8a:7c:ba brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 34:de:1a:7f:93:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 84519sec preferred_lft 84519sec
inet6 fe80::5e82:7f12:37f8:854f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
# 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 8.8.8.8
nameserver 127.0.0.53
options edns0
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: eth0
version: 0c
serial: 00:8c:fa:8a:7c:ba
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
resources: irq:16 ioport:3000(size=256) memory:c1700000-c1700fff memory:c1400000-c1403fff
*-network
description: Wireless interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:08:00.0
logical name: wlan0
version: cb
serial: 34:de:1a:7f:93:1a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-45-generic firmware=17.948900127.0 ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:33 memory:c1600000-c1601fff
cat /etc/apt/sources.list
:
# deb cdrom:[Ubuntu 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
## Major bug fix updates produced after the final release of the
## distribution.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
deb http://archive.ubuntu.com/ubuntu bionic main universe restricted multiverse
## respective vendors as a service to Ubuntu users.
deb http://security.ubuntu.com/ubuntu/ bionic-security universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-updates universe multiverse restricted main
deb http://archive.ubuntu.com/ubuntu bionic-backports universe multiverse restricted main
deb http://archive.canonical.com/ubuntu bionic partner
# deb-src http://archive.canonical.com/ubuntu bionic partner
deb [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
# deb-src [arch=amd64,i386] https://deb.opera.com/opera-stable/ stable non-free
networking 18.04 network-manager 18.10
networking 18.04 network-manager 18.10
edited Feb 17 at 12:54
João Pimentel Ferreira
asked Feb 16 at 18:05
João Pimentel FerreiraJoão Pimentel Ferreira
18711
18711
1
what's the output ofip addr && cat /etc/resolv.conf && sudo lshw -C Network
?
– AlexOnLinux
Feb 16 at 19:52
1
colbycdev mentiones a good point netplan. i do not have ubuntu 18 installed, so i can only refer to the manual either. Perhaps you have some old configurations in/etc/network/interfaces
that now are in conflict with the new system, i dont know. What suprises me is the fact that you recieve an ip from your AP. Yourresolv.conf
looks a littel strange to me, i would have expected your gateway / router ip in there - a line with the following content:nameserver 192.168.1.1
and another line withnameserver 127.0.1.1
. you say: "no internet via command line" - via browser it's working?
– AlexOnLinux
Feb 17 at 10:27
1
as nameserver you are actl using 8.8.8.8. thats google dns. in general that should work either. i dont understand why browsing works while terminal shouldn't. to me that makes no sense. are you sure your apt is pointing to the correct links for your upgraded ubuntu version? check your/etc/apt/sources.list
but i have to admit i am out of ideas. askubuntu.com/a/1036749/669014
– AlexOnLinux
Feb 17 at 12:36
1
Joao, i am really out of ideas. perhaps this is an IPv4 IPv6 problem. This would explain why sometimes connection works and sometimes it does not. Can you connect to this site ipv6-test.com does it show any errors regarding ipv4 or ipv6? You could test forcing ipv4 askubuntu.com/a/759540/669014 or disabling ipv6 askubuntu.com/a/484487/669014
– AlexOnLinux
Feb 17 at 15:51
1
Let us continue this discussion in chat.
– AlexOnLinux
Feb 17 at 17:34
|
show 11 more comments
1
what's the output ofip addr && cat /etc/resolv.conf && sudo lshw -C Network
?
– AlexOnLinux
Feb 16 at 19:52
1
colbycdev mentiones a good point netplan. i do not have ubuntu 18 installed, so i can only refer to the manual either. Perhaps you have some old configurations in/etc/network/interfaces
that now are in conflict with the new system, i dont know. What suprises me is the fact that you recieve an ip from your AP. Yourresolv.conf
looks a littel strange to me, i would have expected your gateway / router ip in there - a line with the following content:nameserver 192.168.1.1
and another line withnameserver 127.0.1.1
. you say: "no internet via command line" - via browser it's working?
– AlexOnLinux
Feb 17 at 10:27
1
as nameserver you are actl using 8.8.8.8. thats google dns. in general that should work either. i dont understand why browsing works while terminal shouldn't. to me that makes no sense. are you sure your apt is pointing to the correct links for your upgraded ubuntu version? check your/etc/apt/sources.list
but i have to admit i am out of ideas. askubuntu.com/a/1036749/669014
– AlexOnLinux
Feb 17 at 12:36
1
Joao, i am really out of ideas. perhaps this is an IPv4 IPv6 problem. This would explain why sometimes connection works and sometimes it does not. Can you connect to this site ipv6-test.com does it show any errors regarding ipv4 or ipv6? You could test forcing ipv4 askubuntu.com/a/759540/669014 or disabling ipv6 askubuntu.com/a/484487/669014
– AlexOnLinux
Feb 17 at 15:51
1
Let us continue this discussion in chat.
– AlexOnLinux
Feb 17 at 17:34
1
1
what's the output of
ip addr && cat /etc/resolv.conf && sudo lshw -C Network
?– AlexOnLinux
Feb 16 at 19:52
what's the output of
ip addr && cat /etc/resolv.conf && sudo lshw -C Network
?– AlexOnLinux
Feb 16 at 19:52
1
1
colbycdev mentiones a good point netplan. i do not have ubuntu 18 installed, so i can only refer to the manual either. Perhaps you have some old configurations in
/etc/network/interfaces
that now are in conflict with the new system, i dont know. What suprises me is the fact that you recieve an ip from your AP. Your resolv.conf
looks a littel strange to me, i would have expected your gateway / router ip in there - a line with the following content: nameserver 192.168.1.1
and another line with nameserver 127.0.1.1
. you say: "no internet via command line" - via browser it's working?– AlexOnLinux
Feb 17 at 10:27
colbycdev mentiones a good point netplan. i do not have ubuntu 18 installed, so i can only refer to the manual either. Perhaps you have some old configurations in
/etc/network/interfaces
that now are in conflict with the new system, i dont know. What suprises me is the fact that you recieve an ip from your AP. Your resolv.conf
looks a littel strange to me, i would have expected your gateway / router ip in there - a line with the following content: nameserver 192.168.1.1
and another line with nameserver 127.0.1.1
. you say: "no internet via command line" - via browser it's working?– AlexOnLinux
Feb 17 at 10:27
1
1
as nameserver you are actl using 8.8.8.8. thats google dns. in general that should work either. i dont understand why browsing works while terminal shouldn't. to me that makes no sense. are you sure your apt is pointing to the correct links for your upgraded ubuntu version? check your
/etc/apt/sources.list
but i have to admit i am out of ideas. askubuntu.com/a/1036749/669014– AlexOnLinux
Feb 17 at 12:36
as nameserver you are actl using 8.8.8.8. thats google dns. in general that should work either. i dont understand why browsing works while terminal shouldn't. to me that makes no sense. are you sure your apt is pointing to the correct links for your upgraded ubuntu version? check your
/etc/apt/sources.list
but i have to admit i am out of ideas. askubuntu.com/a/1036749/669014– AlexOnLinux
Feb 17 at 12:36
1
1
Joao, i am really out of ideas. perhaps this is an IPv4 IPv6 problem. This would explain why sometimes connection works and sometimes it does not. Can you connect to this site ipv6-test.com does it show any errors regarding ipv4 or ipv6? You could test forcing ipv4 askubuntu.com/a/759540/669014 or disabling ipv6 askubuntu.com/a/484487/669014
– AlexOnLinux
Feb 17 at 15:51
Joao, i am really out of ideas. perhaps this is an IPv4 IPv6 problem. This would explain why sometimes connection works and sometimes it does not. Can you connect to this site ipv6-test.com does it show any errors regarding ipv4 or ipv6? You could test forcing ipv4 askubuntu.com/a/759540/669014 or disabling ipv6 askubuntu.com/a/484487/669014
– AlexOnLinux
Feb 17 at 15:51
1
1
Let us continue this discussion in chat.
– AlexOnLinux
Feb 17 at 17:34
Let us continue this discussion in chat.
– AlexOnLinux
Feb 17 at 17:34
|
show 11 more comments
2 Answers
2
active
oldest
votes
Ubuntu 18.04 no longer uses ifupdown(/etc/network/interfaces). That is where you are going wrong
They switched to netplan, huge pain. See more info here
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
add a comment |
I happen to solve this issue by factory resetting the definitions of the router.
add a comment |
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118798%2fhow-to-fully-reset-network-settings-on-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ubuntu 18.04 no longer uses ifupdown(/etc/network/interfaces). That is where you are going wrong
They switched to netplan, huge pain. See more info here
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
add a comment |
Ubuntu 18.04 no longer uses ifupdown(/etc/network/interfaces). That is where you are going wrong
They switched to netplan, huge pain. See more info here
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
add a comment |
Ubuntu 18.04 no longer uses ifupdown(/etc/network/interfaces). That is where you are going wrong
They switched to netplan, huge pain. See more info here
Ubuntu 18.04 no longer uses ifupdown(/etc/network/interfaces). That is where you are going wrong
They switched to netplan, huge pain. See more info here
answered Feb 16 at 22:19
colbycdevcolbycdev
14310
14310
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
add a comment |
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
I read the article, but how can I go from there?
– João Pimentel Ferreira
Feb 17 at 10:09
add a comment |
I happen to solve this issue by factory resetting the definitions of the router.
add a comment |
I happen to solve this issue by factory resetting the definitions of the router.
add a comment |
I happen to solve this issue by factory resetting the definitions of the router.
I happen to solve this issue by factory resetting the definitions of the router.
answered Feb 17 at 20:10
João Pimentel FerreiraJoão Pimentel Ferreira
18711
18711
add a comment |
add a comment |
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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118798%2fhow-to-fully-reset-network-settings-on-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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 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
1
what's the output of
ip addr && cat /etc/resolv.conf && sudo lshw -C Network
?– AlexOnLinux
Feb 16 at 19:52
1
colbycdev mentiones a good point netplan. i do not have ubuntu 18 installed, so i can only refer to the manual either. Perhaps you have some old configurations in
/etc/network/interfaces
that now are in conflict with the new system, i dont know. What suprises me is the fact that you recieve an ip from your AP. Yourresolv.conf
looks a littel strange to me, i would have expected your gateway / router ip in there - a line with the following content:nameserver 192.168.1.1
and another line withnameserver 127.0.1.1
. you say: "no internet via command line" - via browser it's working?– AlexOnLinux
Feb 17 at 10:27
1
as nameserver you are actl using 8.8.8.8. thats google dns. in general that should work either. i dont understand why browsing works while terminal shouldn't. to me that makes no sense. are you sure your apt is pointing to the correct links for your upgraded ubuntu version? check your
/etc/apt/sources.list
but i have to admit i am out of ideas. askubuntu.com/a/1036749/669014– AlexOnLinux
Feb 17 at 12:36
1
Joao, i am really out of ideas. perhaps this is an IPv4 IPv6 problem. This would explain why sometimes connection works and sometimes it does not. Can you connect to this site ipv6-test.com does it show any errors regarding ipv4 or ipv6? You could test forcing ipv4 askubuntu.com/a/759540/669014 or disabling ipv6 askubuntu.com/a/484487/669014
– AlexOnLinux
Feb 17 at 15:51
1
Let us continue this discussion in chat.
– AlexOnLinux
Feb 17 at 17:34