No internet connection after ubuntu server 20.04 install, ifconfig not available
I recently installed Ubuntu Server 20.04 LTS on my desktop, and found out there was no internet connection even though I had the LAN cable connected. ifconfig and iwconfig failed saying the corresponding packages net-tools and wireless-tools were not installed. EDIT Here is the info requested. Please find the image here.
Also ip link . Look at service NetworkManager status , to. The whole ifconfig/ifup/ifdown system is depreciated in later Ubuntu releases.
Please edit your question to show the result of the terminal command: cat /etc/netplan/*.yaml Welcome to Ask Ubuntu.
Along with @chili555 request, also please show us sudo lshw -C network and cat /etc/network/interfaces .
2 Answers 2
Networking in Ubuntu server is managed by netplan. Your file lacks the details needed to connect the ethernet properly.
First, let’s rename the file:
sudo mv /etc/netplan/*.yaml /etc/netplan/01-netcfg.yaml Now, let’s change it to include the required details:
sudo nano /etc/netplan/01-netcfg.yaml network: version: 2 renderer: networkd ethernets: ens33: dhcp4: true Netplan is very particular about spacing, indentation, etc. Proofread carefully twice. Save (Ctrl+o followed by Enter) and exit (Ctrl+x) the text editor. Follow with:
sudo netplan generate sudo netplan apply Не работает интернет, но есть соединение по локальной сети
Всем доброго дня! Не пинайте сильно, в линуксе я полный новичек, но добросовестно весь вечер гуглил свою проблему и ничего не нагуглил 🙁 Суть проблемы такова: в линуксе настраиваю сетевое соединение (что вручную, что DHCP — все одна беда). Пробую пинговать компьютеры в локальной сети и внутрений интерфейс роутера — все отлично пингуется. Но интернета нет. Пробую «ping http://www.google.com», он находит IP гугла по имени (т.е. проблема не в DNS), но пинг не проходит. Сразу после попытки пингануть гугл смотрю лог на роутере — там появляется строчка вида „Dropped packet from 0.0.0.0 to X.X.X.X (IP protocol 1) as unable to create new session“, где X.X.X.X — IP гугла. С виндовыми клиентами (что по проводу, что по WiFi), и с андроидами подобных проблем с роутером не было. Роутер перегружать пробовал. Эта же проблема с различными сборками линукса, и как с виртуальными машинами, так и с живыми компьютерами.
http://www.google.com не существует, он давно на https. И команда ping пинется проще:
Это сути дела не меняет — на виндовой машине тот же гугль нормально пингуется, а на линуксах — нет.
ping в Linux не умеет редирект с http на https. Пробуй
Попробовал и ping google.com — не пашет. И тупо в браузере попробовал открыть google.com, не работает, та же ошибка в роутере при попытке открыть из браузера: «Dropped packet from 0.0.0.0 to 64.233.164.100 (IP protocol 6) as unable to create new session», где 64.233.164.100 — гугль. В то же время веб-интерфейс роутера без проблем открывается в браузере.
Dropped packet from 0.0.0.0 to 64.233.164.100
Стоп. А какого хрена у тебя IP 0.0.0.0?
Дак вот в том-то и проблема, что он никакой не 0.0.0.0 У линукса IP = 169.254.185.97, внутренний интерфейс роутера 169.254.185.200. Есть виндовая машина 169.254.185.1. Для интереса, чтобы убедиться, что линукс на самом деле не 0.0.0.0 я поробовал с винды его пингануть по 169.254.185.97 — пинг проходит, все ОК. Ума не приложу, чего роутер с ума сходит и про какой-то 0.0.0.0 пишет.
Покажи настройки DHCP своего роутера.
Вот: osboxes@osboxes:~$ sudo ifconfig [sudo] password for osboxes: enp0s3 Link encap:Ethernet HWaddr 08:00:27:6c:ff:1e inet addr:169.254.185.97 Bcast:169.254.185.255 Mask:255.255.255.0 inet6 addr: fe80::6314:62ee:128f:f2cf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1657 errors:0 dropped:0 overruns:0 frame:0 TX packets:2090 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:168892 (168.8 KB) TX bytes:201926 (201.9 KB) Interrupt:19 Base address:0xd020
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:58 errors:0 dropped:0 overruns:0 frame:0 TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:5550 (5.5 KB) TX bytes:5550 (5.5 KB)
blitz@inode ~/aur/infinality % sudo netstat -vWeeNpal --numeric-ports --numeric-users -t -u Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 localhost:53 0.0.0.0:* LISTEN 0 3925967 1/systemd tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 195 3929407 18265/systemd-resol tcp 0 0 inode:54268 104.31.88.227:80 ESTABLISHED 1000 8396952 1963/firefox tcp 1 0 inode:46506 bbc-vip024.cwwtf.bbc.co.uk:80 CLOSE_WAIT 1000 8363226 1679/cinnamon tcp 1 0 inode:46508 bbc-vip024.cwwtf.bbc.co.uk:80 CLOSE_WAIT 1000 8363227 1679/cinnamon tcp 0 0 inode:51400 192.0.73.2:443 ESTABLISHED 1000 8391573 1963/firefox tcp 0 0 inode:54270 104.31.88.227:80 ESTABLISHED 1000 8396953 1963/firefox tcp 0 0 inode:54266 104.31.88.227:80 ESTABLISHED 1000 8397918 1963/firefox tcp 0 0 inode:40132 pikabu.ru:443 TIME_WAIT 0 0 - tcp 0 0 inode:40114 pikabu.ru:443 TIME_WAIT 0 0 - tcp 0 0 inode:52828 178.248.233.6:9000 ESTABLISHED 1000 8391579 1963/firefox tcp 0 0 inode:53820 178.248.233.6:443 TIME_WAIT 0 0 - tcp6 0 0 [::]:6600 [::]:* LISTEN 0 15071 1/systemd tcp6 0 0 [::]:5355 [::]:* LISTEN 195 3929410 18265/systemd-resol tcp6 0 0 inode:36898 2400:cb00:2048:1::6819:4108:80 ESTABLISHED 1000 8396262 1963/firefox tcp6 0 0 inode:36896 2400:cb00:2048:1::6819:4108:80 ESTABLISHED 1000 8396261 1963/firefox tcp6 0 0 inode:60602 2400:cb00:2048:1::6814:e30d:80 ESTABLISHED 1000 8274797 1963/firefox tcp6 0 0 inode:39188 yandex.ru:443 ESTABLISHED 1000 8394158 1963/firefox tcp6 0 0 inode:58926 2400:cb00:2048:1::6819:4008:80 ESTABLISHED 1000 8398295 1963/firefox tcp6 0 0 inode:50870 nrt13s48-in-x0e.1e100.net:443 ESTABLISHED 1000 8390408 1963/firefox udp 0 0 localhost:53 0.0.0.0:* 195 3929412 18265/systemd-resol udp 0 0 localhost:53 0.0.0.0:* 0 3925968 1/systemd udp 0 0 inode:68 0.0.0.0:* 193 8364610 29216/systemd-netwo udp 0 0 0.0.0.0:5355 0.0.0.0:* 195 3929406 18265/systemd-resol udp6 0 0 [::]:57107 [::]:* 0 3925977 18173/dnscrypt-prox udp6 0 0 inode:546 [::]:* 193 8383803 29216/systemd-netwo udp6 0 0 [::]:5355 [::]:* 195 3929409 18265/systemd-resol blitz@inode ~/aur/infinality % ip a 1: lo: 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: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 44:37:e6:b7:93:1b brd ff:ff:ff:ff:ff:ff inet 192.168.1.7/24 brd 192.168.1.255 scope global dynamic eno1 valid_lft 2813sec preferred_lft 2813sec inet6 2a02:a03f:10be:2500:4637:e6ff:feb7:931b/64 scope global mngtmpaddr noprefixroute dynamic valid_lft 189555sec preferred_lft 189555sec inet6 fe80::4637:e6ff:feb7:931b/64 scope link valid_lft forever preferred_lft forever Connected to Wifi but no internet
Hi so I’m a complete Ubuntu beginner and I have just installed it. So the problem is that I am connected to the Wifi (wireless) but I can’t actually use the internet. I am using Ubuntu 16.04.
6 Answers 6
I found a simple fix. I didn’t have any problems pinging IP addresses; I ran into problems when I tried to issue a command like:
In other words, I could connect to the internet, as affirmed by the wifi indicator, but I was having problems turning domain names into IP addresses. This process is handled by the text file /etc/resolv.conf, so I decided perhaps it need to be updated. I issued the command:
but Ubuntu spit this back at me:
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf This was the source of my problem: somehow /etc/resolv.conf was pointing to /run/resolvconf/resolv.conf . Fortunately, once I removed the bad symbolic link and created a new symbolic link the wifi worked immediately. That is, I ran the following commands:
sudo rm /etc/resolv.conf sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf and the wifi was back up! I hope this simple solution works for you too!
After following the mentioned steps, as an additional step, I had to set DNS server IP from the network settings. Then that IP saved in the /etc/resolv.conf . Finally it worked.
knowing how to address a non working internet connection may help as follows.
See if you can ping or traceroute to google’s public dns.
If you get communication with Googl’s public DNS then skip down to the last step on DNS.
If you’re not getting a ping/traceroute to Goole’s DNS then start by making sure your wireless addapter is getting IP information with the command.
output should have ip information listed for your wireless adapter something like.
wlan0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xx inet addr:192.168.1.55 Bcast:192.168.1.255 Mask:255.255.255.0 next check to make sure you have a default route
output should have a route something like.
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 At this point you should be able to ping and/or traceroute to Google’s public DNS «8.8.8.8». If not then call your Internet provider for additional help with your internet connection.
Now that we can ping google’s public DNS we can be well assured that our internet is working. If you’re still having problems then your computer is most likely not reaching a working DNS service. You can check your DNS servers with.
You should also check the connection status in your network manager if you’re using a desktop version of ubuntu. Once you have identified/set your DNS servers make sure you can ping them as well. If you can ping the DNS servers that you have set then the problem resides above the network layer in a firewall or application issue.