I have an issue on Ubuntu 18.04 that Ethernet is not managed. However Internet works fine, but it makes it impossible for me to set up vino screen sharing.

Here are some outputs:

superuser@SuperTower:~$ nmcli d
DEVICE  TYPE      STATE      CONNECTION 
eno1    ethernet  unmanaged  --         
vmnet1  ethernet  unmanaged  --         
vmnet8  ethernet  unmanaged  --         
lo      loopback  unmanaged  --  



superuser@SuperTower:~$ ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.228  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::ba85:84ff:fea3:c235  prefixlen 64  scopeid 0x20<link>
        ether b8:85:84:a3:c2:35  txqueuelen 1000  (Ethernet)
        RX packets 1365  bytes 842871 (842.8 KB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 792  bytes 98547 (98.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0x93200000-93220000  

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 66  bytes 5663 (5.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 66  bytes 5663 (5.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.69.1  netmask 255.255.255.0  broadcast 192.168.69.255
        inet6 fe80::250:56ff:fec0:1  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:c0:00:01  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.116.1  netmask 255.255.255.0  broadcast 172.16.116.255
        inet6 fe80::250:56ff:fec0:8  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:c0:00:08  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 59  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


superuser@SuperTower:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback


superuser@SuperTower:~$ cat /etc/NetworkManager/NetworkManager.conf 
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

[device]
wifi.scan-rand-mac-address=no


superuser@SuperTower:~$ ls -al /etc/NetworkManager/conf.d/10-globally-managed-devices.conf 
-rw-r--r-- 1 root root 0 feb  2 23:28 /etc/NetworkManager/conf.d/10-globally-managed-devices.conf


superuser@SuperTower:~$ cat /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf
[keyfile]
unmanaged-devices=none



superuser@SuperTower:~$ cat /etc/netplan/01-network-manager-all.yaml 
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

I have tried solutions from various questions here and also

superuser@SuperTower:~$ sudo nmcli dev set eno1 managed yes

but nothing helps. Still unmanaged. Any ideas?

Symptoms

1. I click on Network Manager icon
2. select the home network and click 'connect'
3. The standard sequence starts (connecting, getting ip address, and freezes for some minutes with 'Waiting for Authorizartion...' message, then fails.
4. Connection to public (non-password-protected) networks works fine.
5. Other devices access that network normally.
6. Workaround with wpa_supplicant works (This is how I connect now)
7. dpkg-reconfigure for either network-manager or kwallet does not help
8. Other applications (skype) use kwallet notmally

How can this be fixed? I read that reinstall or complete system upgrade might help, but I would prefer a quick fix

Is it possible to obtain informations about history of connections to Wi-Fi networks? I am interested in past connections, which had been made before machine last power-off. In my case, router's role was fulfilled by hotspots made from smartphones (let's assume that it is not possible to obtain such informations from router). Wi-Fi network card: TP-LINK TL-WN722N (external). Below I am inserting an example of what I would like to reach (data size is not necessary for me, that is just my image of this kind of functionality).

History of connections:
Foo wireless network, 19-03-2020 11:44, 19-03-2020 13:22, Send: 2123345768, Received: 1627335162
Bar wireless network, 19-03-2020 14:02, 19-03-2020 16:14, Send: 1224385229, Received: 525324143
... 

I'd like to network an old laptop (Linux Mint 17) by connecting its ethernet port to a desktop computer (Xubuntu 19.10) via ethernet to usb adapter. The desktop is connected to the router via its primary ethernet adapter.

The USB/ethernet adapter has an amber and green led, and both are lit. The laptop cannot yet see the network, however.

Here is the output of 'ip addr' on the Xubuntu desktop.

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 fq_codel state UP group default qlen 1000
    link/ether f8:0f:41:61:45:ef brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.105/24 brd 192.168.0.255 scope global dynamic noprefixroute enp0s25
       valid_lft 5092sec preferred_lft 5092sec
    inet6 fe80::28da:59c2:e084:f2d1/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enxe46f13f45969: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether e4:6f:13:f4:59:69 brd ff:ff:ff:ff:ff:ff
4: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 20:68:9d:97:da:4b brd ff:ff:ff:ff:ff:ff

When I installed Xubuntu on the desktop I believe the network configured automatically. When I came later to network the laptop via USB I thought maybe Xubuntu would configure it too automatically. Should Xubuntu 19.10 be able to automatically serve network service to the laptop? Do I need to explicitly configure a second network? Does the Xubuntu machine need to be a bridge? Can this be done using the network GUI tool? I can find the USB/ethernet adapter in the network GUI tool.

Can anyone advise?

Thank you

be warned: I'm a complete newbie to everything Linux, so please ELIF and I'll try to keep up :)

I'm trying to set up Lubuntu on a cheapo laptop that currently has Windows 10. I have my live USB and successfully booted Lubuntu, but while checking to ensure that everything works, I see that I can't connect to wifi. My wifi adapter (Realtek RTL8723DE 802.11b/g/n PCIe Adapter) doesn't appear on Lubuntu's Additional Drivers page, and when I run lshw -C network, this adapter is listed as "network UNCLAIMED" and doesn't list a driver. This is similar to the problem described by this user: https://ubuntuforums.org/showthread.php?t=1314693.

So apparently this problem arises from a device with no drivers attached. The solution given in that thread seems to apply specifically to Ubuntu JauntyJackalope; so my questions are as follows:

1. How do I determine which driver/backport/etc to install based on my distro and my network adapter, and can I just install them with sudo apt-get install? (Ideally I'd like a general way to figure it out in case I want to, say, install Linux Mint instead.)
2. Although I can access the Internet to install things with apt, it's a pain; is there a way to load the driver onto a flash drive and install it from there?

EDIT: As requested, some more terminal output:

$ lspci -nnk | grep 0280 -A3
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
    DeviceName: WLAN
    Subsystem: Hewlett-Packard Company RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]

$ uname -r
5.3.0-18-generic

I've encountered a recent problem with my Samba server (18.04). I have gigabit networking on both ends, but I seem to only get write speeds of about 2MB/s. However, using SSH or FTP, I can transfer files at around 30MB/s which is about what I can expect from my hard drives, so I'm pretty sure the problem is isolated to Samba. Read speeds are about what should be expected. I've only noticed this issue recently with 18.04, after I switched from 16.04. I've tried tweaking MTU's, buffers, cache and other things to no avail. I've put a fresh install of 18.04 server on another machine and used samba just to see if a fresh install would help, but the issue seems universal to all my machines running 18.04. Any help would be greatly appreciated. My samba conf right now is just the default.

I am not so into Linux and I am experiencing a very strange problem with a Linux 19.10 system on which I am working into VmWare workstation (but I suppose that it is not a VMware related problem).

The problem is that I had to restart the system due to a crash that freeze the system. After the restart I have no more Internet connection.

Performing the ifconfig command into the shell I obtain:

developer@developer-virtual-machine:/etc/network$ ifconfig
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  (Loopback locale)
        RX packets 2508  bytes 186240 (186.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2508  bytes 186240 (186.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So it seems that for some reason it loose the ethernet interface used by VmWare to connect in NAT mode.

I tried to restart the system (also the host Windows machine on which VMWare is installed) but I still have this problem. How can I try to fix it?

EDIT-1: Performing sudo lshw -C network I obtain this output:

developer@developer-virtual-machine:~$ sudo lshw -C network
[sudo] password di developer: 
  *-network DISABLED        
       description: Ethernet interface
       product: 82545EM Gigabit Ethernet Controller (Copper)
       vendor: Intel Corporation
       physical id: 1
       bus info: pci@0000:02:01.0
       logical name: ens33
       version: 01
       serial: 00:50:56:3a:4b:1e
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 66MHz
       capabilities: pm pcix bus_master cap_list rom ethernet physical logical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k8-NAPI duplex=full latency=0 link=no mingnt=255 multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:19 memory:fd5c0000-fd5dffff memory:fdff0000-fdffffff ioport:2000(size=64) memory:fd500000-fd50ffff

It seems that the networking is disabled

I'll do my best to provide as much information as possible, I'm still fairly new to linux, but I have Ubuntu Server 18.04.4 currently running my media server, and I'm trying to set a static IP.

I found plenty of tutorials online, I can get it to work fine by editing a file called 50-cloud-init.yaml, and here are the settings that I had:

network:
    renderer: networkd
    ethernets:
        eno1:
            dhcp4: no
            addresses: [192.168.2.46/18]
            gateway4: 192.168.2.1
            nameservers:
                addresses: [192.168.2.1,1.1.1.1]
            dhcp4-overrides:
                hostname: starlight01
                send-hostname: yes
                use-hostname: yes
    version: 2

Now that works perfectly fine, and I do the whole sudo netplan apply thing, and I can browse my samba shares from by doing \\192.168.2.46\ however, I have a few applications that rely on the machine name, not IP, and for some reason, when it's a dynamic IP I can type \\starlight01\, but it suddenly stops working when I use the machine/host name.

I would also like to add that every machine stops being able to access via the machine name.

When it has a static IP, I can ping by IP, and get a response, but pinging by machine name results in a timeout, but pinging with a Dynamic IP works fine for both.

I have also tried the following:

• rebooting my router, and associated switches
• rebooting the server
• dns flush on my windows machine
• rebooting my windows machine
• removing the dhcp4-overrides section of the said file

My resolv.conf file has 'nameserver 127.0.0.53'.
I need to replace it with different value or add another nameserver.

I erased symlink, replaced it with file. Now it is managed by Network Manager,
but 127.0.0.53 is restored upon reboot.

I need to keep changes, I made.

If I configure network interface in 'interfaces' file,
it becomes 'UNMANAGED' in Network Manager. It's configuration has no effect, though.

This question is related HERE.

Guys, If it is not so much trouble, will you, please, read.

Before I perform any 'ping' or 'host', I have to get through that LOGIN procedure.

My main problem is there. What I am trying to do here is to create a kind of work around.

Adding ANY nameserver except 127.0.0.53 or 0.0.0.0 into resolv.conf makes that thing working.
Network DNS is 192.168.11.1. I inserted 192.168.0.1 and it worked. You name it - it goes. But changing settings in Network Manager has no effect at all.

@heynnema, I did those settings in IPV4 tab before I rose the question, but unfortunately, they did not work.
/etc/network/interfaces file is intact,
UBUNTU 18.10 is clean installed.
I edited the file for the sake of creating a router in DEBIAN, and I saw how it worked. I do not want it to be the same way here.

@Marmayogi my DNS is 192.168.11.1, the same one is in /run/systemd/resolve/resolv.conf. I was surprised to see it there.

Yes, @Marmayogi, my goal is to get that screen.
On UNITY 18.04 this file does not exist, but it does not change much.

/etc/netplan/01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager  

ip link show
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: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether bc:ae:c5:35:85:e6 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 48:5d:60:c5:91:0b brd ff:ff:ff:ff:ff:ff

systemd-resolve --status wlp3s0
Link 3 (wlp3s0)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
    DNSSEC setting: no
    DNSSEC supported: no
Current DNS Server: 192.168.11.1
     DNS Servers: 192.168.11.1
      DNS Domain: ~.
                  crew.local  

Yes @Marmayogi, this is the only thing I want working for now. This solution seems aukward to me, though. There was a symlink, as you can see in other post. I removed it, hoping that I would get things working for me.

@Marmayogi, you did a Great job, creating that step by step instruction.

Your solution is GENIUS, not decent!

I tested. Login successful, internet works.

@heynnema,
/run/resolvconf/resolv.conf does not exist on UBUNTU 18.10.
What would you advise in this situation?

System is installed clean from ISO, downloaded from UBUNTU.COM.

My Ubuntu Server (18.04) will suddenly lose all internet connection, after running fine for a few minutes to a few hours, can't ping 8.8.8.8 or hostnames. Local network works fine.

It happens with both DHCP and static IP in /etc/netplan/50-cloud-init.yaml

Rebooting the server doesn't fix anything. Only rebooting the router restores internet.

Weirdly, DHCP works, and I will successfully get IP from my router, upon reboot or restarting network on the server.

running ifconfig -a gives following on my wired connection. (I have a ton of other interfaces, that I left out, from having docker running on the server)

enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.99  netmask 255.255.0.0  broadcast 192.168.255.255
        inet6 fe80::3e97:eff:fe3b:f588  prefixlen 64  scopeid 0x20<link>
        ether 3c:97:0e:3b:f5:88  txqueuelen 1000  (Ethernet)
        RX packets 286557  bytes 39798935 (39.7 MB)
        RX errors 0  dropped 63  overruns 0  frame 0
        TX packets 407440  bytes 427684619 (427.6 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf2500000-f2520000

And ethtool enp0s25 gives:

Settings for enp0s25:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

I'm unfortunately not very strong in the internals of linux/ubuntu to know how to troubleshoot this issue better. There are no indications in the logs in my cockpit interface.

I've had the exact same networking setup running fine on a ubuntu desktop for months - same router, routersetup and switches/cables.

Can anyone point me in the right direction?

I suspect a program is listening on port 8000 on my machine.

When I run the following command, I get this error:

> python -m SimpleHTTPServer
# Lots of python error
socket.error: [Errno 98] Address already in use

If I use another port (8000 is the default), the web server runs fine.

If I run wget localhost:8000 from the command line, it returns 404 Not Found.

What can I do (or what tools are available) to find what program is listening on port 8000, and from there where that program is configured?

In ubuntu 18.04 the network enables after the login.

But I need network after that, for remote network connections for example.

How do I archieve that?

Preferable by command line, so I could configure multiple machines.

I have looked at several posts on this issue but none seem to address what I am seeing.

First, I had issues with what this post details https://raspberrypi.stackexchange.com/questions/43560/raspberry-pi-3-eth0-wrongfully-named-enx

Apparently, there is some new way of naming eth0 consistent with "consistent network device naming". Great except it would not allow me to connect to the ethernet at all.

Therefore, I followed the post above and added a rule to: /etc/udev/rules.d/70-persistent-net.rules

which by my estimations forces the pi to name my ethernet card eth0 again.

This worked! I actually have two PIs which were having the same issue.

Ok, so why the post. Well, one pi is having no difficulties and connects on startup without any issues now. However, the other will not automatically connect to the ethernet. The IP listed when I run:

ifconfig -a

Is not on my subnet? Not sure if I have my lingo right here but... It has an IP of 192.168.0.1 for example when it should be 192.168.127.X

My knowledge of networking is growing because of these issues but I am no expert. I am curious about what is going on with the above problem and wondering if anyone has had similar issues.

The pi I am having issues with will connect eventually to the ethernet but I have to disconnect and then reconnect to obtain a valid IP. I would like to avoid this nonsense if possible.

I have seen solutions recommending editing the

/etc/network/interfaces

Network not starting up on boot

The issue here is when I edit in my eth0 it will not connect at all. I found this odd and the fact that when I edit the interfaces file, there is no mention of eth0 at all, yet on one machine, it connects fine. The other machine and the one I made this post about appears to have an intermittent problem with connecting where sometimes it picks up an IP no problem but other times it does not. this is what my interfaces file looks like now and today, upon startup, they both hooked up to the ethernet fine and got their IPs with no problem.

# The loopback network interface
auto lo
iface lo inet loopback

The pi that has been working fine and now the other pi seem to connect and get an IP but are missing eth0 in this file. I do not know tons about this but I assumed the interfaces file was similar to a startup file that setup these devices.

Any advice or thoughts would be appreciated as I would like to know more about why it is in fact working and what is going on when it doesn't connect right off the bat. It seems I have patched together a working environment but perhaps it is a little unstable.

UPDATE: In addition to adding the 70-persistent-net.rules file as described above, I ended up following another poster's advice from the first link above and did the following because it has continued to be intermittent with connecting.

1. I copied /lib/udev/rules.d/73-usb-net-by-mac.rules over to /etc/udev/rules.d/73-usb-net-by-mac.rules
2. I changed the name to >> NAME="eth0" as poster Luis Godinez suggested.

On reboot it connected right up but I will not be able to tell how stable it is for a bit I guess... Hopefully these two changes get me going in the right direction. I will update again on how this is working out if it doesn't work.

Final Update I still encountered ethernet problems so I just gave up at this point. All those rule fixes did not work on this machine which is weird because the first pi is still connecting fine and I used the same instructions. This is so odd. I am praying the pi that is working now continues to purr along because I can not deal with anymore ethernet issues at this point.

I've installed Ubuntu 16.04 Gnome on my laptop and the Wifi module was not working as soon as I booted into the system, so I followed these steps

But after doing the setup my wifi was still loading and "No networks" were showing.

It just spins up forever and no wifi networks are found, how can I resetup the wifi and make it working.

sahil@sahil-HP-Laptop-15-bs1xx:~$ lspci -knn | grep Net -A3; rfkill list
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:d723]
    DeviceName: WLAN
    Subsystem: Hewlett-Packard Company Device [103c:8319]
    Kernel driver in use: rtl8723de
3: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
4: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

In Ubuntu's system configuration menu, section "Network," there's a section called "Wired" with an On/Off slider button.

What is the command-line equivalent of pushing that slider to the Off position and the back into the On position?

I don't mind a solution that just power-cycles all networking, not just wired.

Ubuntu 18.04.4 LTS

(The problem I have is my connection is mediated by a crappy repeater/bridge; the hardware itself is junk. I just want the command-line tools to write my own work-around of disconnecting and reconnecting the wired connection automatically, which is an instantaneous process and solves my problem.)

Edit: Thank you for all the answers, they all work.

I'm running ubuntu 18.04.

I had network/router issues and ultimately I replaced my router. Both intranet and internet communications are now working, but I have a problem with one node, a laptop.

The older router IP was 192.168.0.1 and the new router IP is 192.168.86.1, so I had to update the IP addressing, which I did.

On this node, I have modified my /etc/netplan/01-network-manager-all.yaml file so that it reads as follows:

network:
  version: 2
  renderer: NetworkManager
  ethernets:
    enp6s0:
      dhcp4: no
      dhcp6: no
      addresses: 
        - 192.168.86.240/24
      gateway4: 192.168.86.1
      nameservers:
        addresses: [8.8.8.8,8.8.4.4]

I have run:

netplan apply

I have also rebooted the system.

When I run 'ip addr', I am expecting to see an ip address of 192.168.86.240/24, but my results are:

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: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 1c:75:08:c3:0a:fd brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.240/24 brd 192.168.0.255 scope global noprefixroute enp6s0
       valid_lft forever preferred_lft forever
    inet6 fe80::ca8e:48b6:9a1f:d7f2/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever 3: wlp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 90:00:4e:05:70:ee brd ff:ff:ff:ff:ff:ff

I did this on other nodes running ubuntu 18.04 and did not have a problem. Am I doing something wrong?

Jim A.

I have a Hp Elitebook G2 840 Core i5, 500GB HDD, 8GB RAM laptop. The laptop has a wlan card, antenna and sim slot installed.

I have tried installing iwlwifi and enabled the network interface. I want to connect to the internet using my sim card on the wlan card. Intel Wireless Dual Band 7265-AC.

root@elviskemboi:/# lspci | grep -i wireless
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 48)

root@elviskemboi:/# ifconfig wlo1
wlo1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 94:65:9c:f8:a5:5c  txqueuelen 1000  (Ethernet)
        RX packets 35149  bytes 3985866 (3.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 69436  bytes 83453640 (83.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@elviskemboi:/# iwconfig wlo1
wlo1      no wireless extensions.

root@elviskemboi:/# iw wlo1 info
Interface wlo1
    ifindex 3
    wdev 0x1
    addr 94:65:9c:f8:a5:5c
    type managed
    wiphy 0
    txpower 20.00 dBm

root@elviskemboi:/# rfkill list all
1: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

root@elviskemboi:/# iwlist wlo1 scan
wlo1      Interface doesn't support scanning.

root@elviskemboi:/# ethtool -i wlo1
driver: iwlwifi
version: 5.3.0-42-generic
firmware-version: 17.388f111f.0 7265-17.ucode
expansion-rom-version: 
bus-info: 0000:03:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

root@elviskemboi:/# nmcli -f GENERAL,WIFI-PROPERTIES dev show wlo1
GENERAL.DEVICE:                         wlo1
GENERAL.TYPE:                           wifi
GENERAL.NM-TYPE:                        NMDeviceWifi
GENERAL.VENDOR:                         Intel Corporation
GENERAL.PRODUCT:                        Wireless 7265 (Dual Band Wireless-AC 7265)
GENERAL.DRIVER:                         iwlwifi
GENERAL.DRIVER-VERSION:                 5.3.0-42-generic
GENERAL.FIRMWARE-VERSION:               17.388f111f.0 7265-17.ucode
GENERAL.HWADDR:                         94:65:9C:F8:A5:5C
GENERAL.MTU:                            1500
GENERAL.STATE:                          20 (unavailable)
GENERAL.REASON:                         2 (Device is now managed)
GENERAL.UDI:                            /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/net/wlo1
GENERAL.IP-IFACE:                       --
GENERAL.IS-SOFTWARE:                    no
GENERAL.NM-MANAGED:                     yes
GENERAL.AUTOCONNECT:                    yes
GENERAL.FIRMWARE-MISSING:               no
GENERAL.NM-PLUGIN-MISSING:              no
GENERAL.PHYS-PORT-ID:                   --
GENERAL.CONNECTION:                     --
GENERAL.CON-UUID:                       --
GENERAL.CON-PATH:                       --
GENERAL.METERED:                        unknown
WIFI-PROPERTIES.WEP:                    yes
WIFI-PROPERTIES.WPA:                    yes
WIFI-PROPERTIES.WPA2:                   yes
WIFI-PROPERTIES.TKIP:                   yes
WIFI-PROPERTIES.CCMP:                   yes

root@elviskemboi:/# wavemon
wavemon: no supported wireless interfaces found! Check manpage for help.

root@elviskemboi:/# netstat -i
Kernel Interface table
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
enp0s25   1500        0      0      0 0             0      0      0      0 BMU
lo       65536     4883      0      0 0          4883      0      0      0 LRU
wwp0s20u  1500   197263      0      0 0        112329      0      0      0 BMRU

root@elviskemboi:/# lspci | egrep -i --color 'network'
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 48)

Upon returning from a recent trip, my Ubuntu 19.04 autofs no longer mounts the cifs Windows 10 shares. When I click the Windows 10 machine in Nautilus under Other Locations, I get the error, Unable to access location, Failed to retrieve share list from server, Network dropped connection on reset. Does this have to do with SMB v1 and some Windows update? On my android phone, the file manager could also no longer connect to the Windows 10 machine, but after I installed an SMB v2 add-on, the phone can now connect to it. In my Ubuntu smb.conf file, I added min protocol = SMB2, but that did not fix it. Is there a way to get my autofs to mount the cifs shares again? I prefer to not go the fstab route, rather I want to keep using autofs if possible.

I'm trying to configure my Raspberry Pi 4B running Ubuntu 18.04 with a static IP address (to then configure a DHCP server) and use the WiFi for internet traffic (routing any clients connecting to the DHCP through to the WiFi connection) but I cannot define a static IP address for the LAN, using netplan I have the config: `network: #LAN connection for ipv4 DHCP server version: 2 renderer: networkd ethernets: eth0 addresses: - 10.0.0.1/24 gateway4: 10.0.0.1 nameservers: addresses: [8.8.8.8, 4.4.4.4.4]

    # LAN connection ipv6 - using for DHCP Server
    version: 2
    renderer: networkd
    ethernets:
            eth0:
    addresses:
            - 2001:1::1/64
    gateway6: 2001:1::2
    nameservers:
            addresses: [8.8.8.8, 4.4.4.4]

    # wifi connection
    wifis:
            wlan0
    dhcp4: true
    dhcp6: true
    access-points:
            "SSID-name"
    password: "WiFi Password"

I keep getting indentation errors when I try to apply the plan. The indentation is that which is created when I manually type in the details.

sudo netplan -debug generate
/etc/netplan/50-cloud-init.yaml:11:17: Error in network definition: expected mapping (check indentation)
                eth0
                ^

I have 4 NIC cards on my VM. While setting up OS, I have activated one NIC and after installing, I have activated other NIC manually by assigning static IP. But after every reboot, I have to enter ifcfg up for every NIC. Why is this happening and how can I resolve it?