Installing Ivacy VPN on Ubuntu 20.04 is easy and like previous versions of Ubuntu. This is another story when it comes to Kubuntu 20.04. The only setting in Kubuntu 20.04 is "Turn on VPN Automatically". There are no settings for adding a VPN in either the Kubuntu Settings or Kubuntu Networks. I would like to be able to use the PTPP version as done in previous Ubuntu/Kubuntu versions.

An Ubuntu 19.10 machine has been experiencing sudden loss of network connectivity. It is on the same network as several Windows and Mac systems which never experience these network problems.

When the Ubuntu system experience this problem, running ping google.com will give the error message:

Temporary failure in name resolution

Tried running sudo dhclient to regain network connectivity. This sometimes solves the problem, and other times it just hangs there for a really long time.

Rebooting the system tends to work at restoring the network access, but the problem will eventually occur again.

What is really happening, and how can we avoid this problem?

ip route

172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-e679420ceeeb proto kernel scope link src 172.18.0.1 172.19.0.0/16 dev br-d24de0d39a51 proto kernel scope link src 172.19.0.1 

ip link

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:002: enp35s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000    link/ether 70:85:c2:fd:cb:f9 brd ff:ff:ff:ff:ff:ff3: enp36s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000    link/ether 70:85:c2:fd:e4:2b brd ff:ff:ff:ff:ff:ff6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default     link/ether 02:42:63:e9:39:70 brd ff:ff:ff:ff:ff:ff19: br-e679420ceeeb: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default     link/ether 02:42:b0:9b:ad:ed brd ff:ff:ff:ff:ff:ff20: br-d24de0d39a51: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default     link/ether 02:42:db:94:c2:16 brd ff:ff:ff:ff:ff:ff22: veth88fb62f@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d24de0d39a51 state UP mode DEFAULT group default     link/ether 3a:f6:09:94:16:38 brd ff:ff:ff:ff:ff:ff link-netnsid 224: vethd4b4b3e@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-e679420ceeeb state UP mode DEFAULT group default     link/ether 82:9c:8a:ea:fb:5c brd ff:ff:ff:ff:ff:ff link-netnsid 026: vethe937672@if25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d24de0d39a51 state UP mode DEFAULT group default     link/ether 92:f9:2d:6c:50:f1 brd ff:ff:ff:ff:ff:ff link-netnsid 130: vetha7a98be@if29: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-e679420ceeeb state UP mode DEFAULT group default     link/ether ea:5b:cf:3a:71:82 brd ff:ff:ff:ff:ff:ff link-netnsid 332: veth35b48e4@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d24de0d39a51 state UP mode DEFAULT group default     link/ether 86:96:63:9a:a5:e0 brd ff:ff:ff:ff:ff:ff link-netnsid 533: enp3s0f0u14u2c2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000    link/ether 66:cb:3b:51:7d:87 brd ff:ff:ff:ff:ff:ff

cat /etc/resolv.conf

# This file is managed by man:systemd-resolved(8). Do not edit.## This is a dynamic resolv.conf file for connecting local clients to the# internal DNS stub resolver of systemd-resolved. This file lists all# configured search domains.## Run "resolvectl status" to see details about the uplink DNS servers# currently in use.## Third party programs must not access this file directly, but only through the# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,# replace this symlink by a static file or a different symlink.## See man:systemd-resolved.service(8) for details about the supported modes of# operation for /etc/resolv.conf.nameserver 127.0.0.53options edns0

cat /etc/nsswitch.conf

# /etc/nsswitch.conf## Example configuration of GNU Name Service Switch functionality.# If you have the `glibc-doc-reference' and `info' packages installed, try:# `info libc "Name Service Switch"' for information about this file.passwd:         files systemdgroup:          files systemdshadow:         filesgshadow:        fileshosts:          files mdns4_minimal [NOTFOUND=return] dnsnetworks:       filesprotocols:      db filesservices:       db filesethers:         db filesrpc:            db filesnetgroup:       nis

nslookup ubuntu.com

Server:     127.0.0.53Address:    127.0.0.53#53** server can't find ubuntu.com: SERVFAIL

dig bing.com

; <<>> DiG 9.11.5-P4-5.1ubuntu2.1-Ubuntu <<>> bing.com;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50385;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 65494;; QUESTION SECTION:;bing.com.          IN  A;; Query time: 0 msec;; SERVER: 127.0.0.53#53(127.0.0.53);; WHEN: Mon Apr 06 18:21:13 EDT 2020;; MSG SIZE  rcvd: 37

systemd-resolve --status

Global       LLMNR setting: noMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: no          DNSSEC NTA: 10.in-addr.arpa                      16.172.in-addr.arpa                      168.192.in-addr.arpa                      17.172.in-addr.arpa                      18.172.in-addr.arpa                      19.172.in-addr.arpa                      20.172.in-addr.arpa                      21.172.in-addr.arpa                      22.172.in-addr.arpa                      23.172.in-addr.arpa                      24.172.in-addr.arpa                      25.172.in-addr.arpa                      26.172.in-addr.arpa                      27.172.in-addr.arpa                      28.172.in-addr.arpa                      29.172.in-addr.arpa                      30.172.in-addr.arpa                      31.172.in-addr.arpa                      corp                      d.f.ip6.arpa                      home                      internal                      intranet                      lan                      local                      private                      testLink 33 (enp3s0f0u14u2c2)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 32 (veth35b48e4)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 30 (vetha7a98be)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 26 (vethe937672)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 24 (vethd4b4b3e)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 22 (veth88fb62f)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 20 (br-d24de0d39a51)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 19 (br-e679420ceeeb)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 6 (docker0)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 3 (enp36s0)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: noLink 2 (enp35s0)      Current Scopes: noneDefaultRoute setting: no       LLMNR setting: yesMulticastDNS setting: no  DNSOverTLS setting: no      DNSSEC setting: no    DNSSEC supported: no

cat /var/log/syslog | grep resolved

Apr  6 00:00:01 foo-bar systemd-resolved[2390]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Apr  6 00:00:01 foo-bar systemd-resolved[2390]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Apr  6 00:00:01 foo-bar systemd-resolved[2390]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Apr  6 00:00:01 foo-bar systemd-resolved[2390]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.]Apr  6 12:40:31 foo-bar systemd-resolved[2358]: Positive Trust Anchors:Apr  6 12:40:31 foo-bar systemd-resolved[2358]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5Apr  6 12:40:31 foo-bar systemd-resolved[2358]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8dApr  6 12:40:31 foo-bar systemd-resolved[2358]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private testApr  6 12:40:31 foo-bar systemd-resolved[2358]: Using system hostname 'foo-bar'.Apr  6 12:40:31 foo-bar NetworkManager[2489]: <info>  [1586191231.7026] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices.conf, no-mac-addr-change.conf) (run: netplan.conf) (etc: default-wifi-powersave-on.conf)Apr  6 12:40:31 foo-bar systemd-resolved[2358]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Apr  6 12:40:31 foo-bar systemd-resolved[2358]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Apr  6 12:40:31 foo-bar systemd-resolved[2358]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Apr  6 12:40:31 foo-bar NetworkManager[2489]: <info>  [1586191231.9621] dns-mgr[0x56555788b290]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolvedApr  6 12:40:32 foo-bar dockerd[2624]: time="2020-04-06T12:40:32.149982460-04:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf"Apr  6 18:11:51 foo-bar systemd[1]: systemd-resolved.service: Succeeded.Apr  6 18:11:51 foo-bar systemd-resolved[8952]: Positive Trust Anchors:Apr  6 18:11:51 foo-bar systemd-resolved[8952]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5Apr  6 18:11:51 foo-bar systemd-resolved[8952]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8dApr  6 18:11:51 foo-bar systemd-resolved[8952]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private testApr  6 18:11:51 foo-bar systemd-resolved[8952]: Using system hostname 'foo-bar'.

today I was just doing regular maintenance on my computer and while checking that iptables was working properly I decided to run the list command,I was expecting to find my regular configuration dropping input and forward by default and accepting all outgoing traffic with some rules for input in order to allow browsing etc, however this is what the command listed iptables -L output, I am no expert so I am not sure of what all of these rules are doing, I recently updated to a newer version of ubuntu, is my computer compromised or this some change that was made by canonical.

Any help is appreciated thank you in advance!.

Edit: Currently I am using Ubuntu 18.04 64-bit, the desktop version, and I am not using virtualization, iptables v1.6.1, and the Kernel version is 5.5.7 hope this helps

Edit 2: Ok so I feel pretty dumb right now, after the upgrade it seems that the installer flushed my iptables configuration and activated UFW aka the regular firewall, since the firewall has multiple set ups it creates a bunch of rules that are listed under iptables regardless of which one is being used, I just needed to turn of the firewall and set my normal rules, Thanks to the guy who commented.

I've just installed Ubuntu 18.04.4 LTS (Bionic Beaver) on my desktop this evening - I use Linux VMs (purely CLI based) at work all the time so I'm familiar with Linux but new to Ubuntu, and configuring WiFi adapters in Linux for that matter.

I have a Gigabyte GC-WB1733D-I PCI-E WiFi adapter and my WiFi settings currently say 'No WiFi adapter found'. I have had a look around and followed a few tutorials and YouTube videos where you are instructed to run clone a Git repo and then run some scripts that are downloaded - none of these have worked for me.

My adapter is based on Intel Wireless-AC 9260. I found a firmware download for this here, but even after downloading and reading the README, I'm not entirely sure what to do as the instructions are generic i.e. not distribution specific so it doesn't give direct instructions. It did say to copy the iwlwifi-9260-th-b0-jf-b0-34.ucode file to /lib/firmware which I have done, but I'm not sure how to proceed from here.

Any advice is greatly appreciated!

EDIT: As requested, the output of running lspci -knn | grep Net -A3; rfkill list; uname -a is:

03:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)    Subsystem: ASUSTeK Computer Inc. I211 Gigabit Network Connection [1043:85f0]    Kernel driver in use: igb    Kernel modules: igb07:00.0 Network controller [0280]: Intel Corporation Wireless-AC 9260 [8086:2526] (rev 29)    Subsystem: Intel Corporation Device [8086:0014]    Kernel modules: iwlwifi08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1)0: hci0: Bluetooth    Soft blocked: no    Hard blocked: noLinux aidan-desktop 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Also, output of dmesg | grep iwl is:

[ 16.849713] iwlwifi 0000:07:00.0: enabling device (0000 -> 0002)[ 16.911415] iwlwifi: probe of 0000:07:00.0 failed with error -110

Total newbie here, got fed up with Windows world and gone over to the dark side

Yesterday I installed Ubuntu 18.4 LTS on VirtualBox with bridge connections.

It seems I can ping IP addresses internally, ping with IP addresses externally but when I try to resolve hostnames or websites, I can't.

rahim@websrv01ubuntu:~$ ping -c3 192.168.0.1PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.20 ms64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=9.16 ms64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=7.38 ms--- 192.168.0.1 ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 2003msrtt min/avg/max/mdev = 3.206/6.584/9.164/2.497 ms

rahim@websrv01ubuntu:~$ ping -c3 8.8.8.8PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.64 bytes from 8.8.8.8: icmp_seq=1 ttl=121 time=34.7 ms64 bytes from 8.8.8.8: icmp_seq=2 ttl=121 time=22.9 ms64 bytes from 8.8.8.8: icmp_seq=3 ttl=121 time=27.8 ms--- 8.8.8.8 ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 2004msrtt min/avg/max/mdev = 22.980/28.526/34.788/4.849 msrahim@websrv01ubuntu:~$ ping -c3 websvr01ubuntuping: websvr01ubuntu: Temporary failure in name resolutionrahim@websrv01ubuntu:~$ ping -c3 www.google.comPING www.google.com(ams16s32-in-x04.1e100.net (2a00:1450:400e:80c::2004)) 56 data bytes--- www.google.com ping statistics ---3 packets transmitted, 0 received, 100% packet loss, time 2042ms

I know 18.04 uses netplan and this is how it the 50-cloud-init.yaml file is configured for static IP address.

network:  version: 2  renderer: networkd  ethernets:    enp0s3:      dhcp4: no      addresses: [192.168.0.200/24]      gateway4: 192.168.0.1      nameservers:        addresses: [8.8.8.8,8.8.4.4]

rahim@websrv01ubuntu:~$ ping -c3 google.comPING google.com(ams16s32-in-x0e.1e100.net (2a00:1450:400e:80c::200e)) 56 data bytes--- google.com ping statistics ---3 packets transmitted, 0 received, 100% packet loss, time 2038ms

rahim@websrv01ubuntu:~$ ping -c3 www.google.comPING www.google.com(ams15s21-in-x04.1e100.net (2a00:1450:400e:800::2004)) 56 data bytes--- www.google.com ping statistics ---3 packets transmitted, 0 received, 100% packet loss, time 2034ms

rahim@websrv01ubuntu:~$ ping -c3 www.servingyoubetter.co.ukPING fwd3.hosts.co.uk (85.233.160.22) 56(84) bytes of data.--- fwd3.hosts.co.uk ping statistics ---3 packets transmitted, 0 received, 100% packet loss, time 2055ms

I am using Ubuntu 18 minimal image to create an Ubuntu server with VirtualBox. I created a host only network and added adapter to vm along with NAT adapter (already configured).

The original configuration of netplan was the following:

network:  version: 2  renderer: networkd  ethernets:    enp0s3:      dhcp4: yes

I changed this configuration to the following to enable host only adapter (enp0s8):

network:  version: 2  renderer: networkd  ethernets:    enp0s3:      dhcp4: ye    enp0s8:      dhcp4: no      addresses: [192.168.56.101/24]      gateway4: 192.168.56.1

Now I am successfully able to access the VM from the host machine over the network. But internet inside the VM stops working :(. I have tried so many different solutions but either I get internet working (provided by NAT adapter) by disabling host only adapter, or can access vm from host by enabling host only adapter.

I suspect the VM is trying to connect to internet via host only adapter. How can I change this?

I had SSH working with keys, but for some reason it stopped and I can't figure out why. I've tried reconfiguring by copying over my public key, I've tried making sure its loaded in the client, and I've even messed a little with the SSH config on the remote machine. I have ssh -v but I'm not sure what the issue is. Here is my output (with some masking)

[USER]@[USER]s-MBP ~ % ssh -v [USER]@[SERVER]OpenSSH_8.1p1, LibreSSL 2.7.3debug1: Reading configuration data /Users/[USER]/.ssh/configdebug1: /Users/[USER]/.ssh/config line 1: Applying options for *debug1: Reading configuration data /usr/local/etc/ssh_configdebug1: Reading configuration data /etc/ssh/ssh_configdebug1: /etc/ssh/ssh_config line 47: Applying options for *debug1: Connecting to [SERVER] port 22.debug1: Connection established.debug1: identity file /Users/[USER]/.ssh/id_rsa type 0debug1: identity file /Users/[USER]/.ssh/id_rsa-cert type -1debug1: identity file /Users/[USER]/.ssh/id_dsa type -1debug1: identity file /Users/[USER]/.ssh/id_dsa-cert type -1debug1: identity file /Users/[USER]/.ssh/id_ecdsa type -1debug1: identity file /Users/[USER]/.ssh/id_ecdsa-cert type -1debug1: identity file /Users/[USER]/.ssh/id_ed25519 type -1debug1: identity file /Users/[USER]/.ssh/id_ed25519-cert type -1debug1: identity file /Users/[USER]/.ssh/id_xmss type -1debug1: identity file /Users/[USER]/.ssh/id_xmss-cert type -1debug1: Local version string SSH-2.0-OpenSSH_8.1debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002debug1: Authenticating to [SERVER]:22 as '[USER]'debug1: SSH2_MSG_KEXINIT sentdebug1: SSH2_MSG_KEXINIT receiveddebug1: kex: algorithm: curve25519-sha256debug1: kex: host key algorithm: ecdsa-sha2-nistp256debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: nonedebug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: nonedebug1: expecting SSH2_MSG_KEX_ECDH_REPLYdebug1: Server host key: ecdsa-sha2-nistp256 SHA256:C3ILGqhuYcsr/6Vox2PCpZ05JKr/gUQI3y8RpB7Ai9Udebug1: Host '[SERVER]' is known and matches the ECDSA host key.debug1: Found key in /Users/[USER]/.ssh/known_hosts:12debug1: rekey out after 134217728 blocksdebug1: SSH2_MSG_NEWKEYS sentdebug1: expecting SSH2_MSG_NEWKEYSdebug1: SSH2_MSG_NEWKEYS receiveddebug1: rekey in after 134217728 blocksdebug1: Will attempt key: [1] touchid-mac ECDSA SHA256:D2nlwjzZ/l7+0ruNCKJ2uTaVD2kkcRghhVW1MBCcpK0 agentdebug1: Will attempt key: /Users/[USER]/.ssh/id_rsa RSA SHA256:g5VEpqkXbAcFYTJwtLiIk+4f84Bshudqx9CXLEfo9rgdebug1: Will attempt key: /Users/[USER]/.ssh/id_dsa debug1: Will attempt key: /Users/[USER]/.ssh/id_ecdsa debug1: Will attempt key: /Users/[USER]/.ssh/id_ed25519 debug1: Will attempt key: /Users/[USER]/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO receiveddebug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>debug1: SSH2_MSG_SERVICE_ACCEPT receiveddebug1: Authentications that can continue: publickey,passworddebug1: Next authentication method: publickeydebug1: Offering public key: [1] touchid-mac ECDSA SHA256:D2nlwjzZ/l7+0ruNCKJ2uTaVD2kkcRghhVW1MBCcpK0 agentdebug1: Authentications that can continue: publickey,passworddebug1: Offering public key: /Users/[USER]/.ssh/id_rsa RSA SHA256:g5VEpqkXbAcFYTJwtLiIk+4f84Bshudqx9CXLEfo9rgdebug1: Authentications that can continue: publickey,passworddebug1: Trying private key: /Users/[USER]/.ssh/id_dsadebug1: Trying private key: /Users/[USER]/.ssh/id_ecdsadebug1: Trying private key: /Users/[USER]/.ssh/id_ed25519debug1: Trying private key: /Users/[USER]/.ssh/id_xmssdebug1: Next authentication method: password

I recently -- in reaction to pandemy -- installed a wired connection to my Ubuntu 18.04 laptop:

• Dell XPS13 Intel Core i7-8550U CPU @ 1.80GHz × 4
• ST: D61NHR2
• EX: 28663743134

Once I connect, quite rapidly, in a matter of minutes the computer stops working correctly: network connection is lost, system monitor window asks for wait or shut down but shut down not possible, etc. Needs an on/off button hard restart.

As seen here, I append the results of the command

zzzzzzz@PDXP13-D61NHR2:~$ sudo lshw -C Network && lspci -knn | grep -i ether -A 3 && lsb_release -a && uname -a  *-network                        description: Interface réseau sans fil       produit: QCA6174 802.11ac Wireless Network Adapter       fabriquant: Qualcomm Atheros       identifiant matériel: 0       information bus: pci@0000:02:00.0       nom logique: wlp2s0       version: 32       numéro de série: 9c:b6:d0:92:35:73       bits: 64 bits       horloge: 33MHz       fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless       configuration: broadcast=yes driver=ath10k_pci driverversion=5.3.0-45-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.1.4 latency=0 link=yes multicast=yes wireless=IEEE 802.11       ressources: irq:143 mémoire:dc000000-dc1fffff  *-network       description: Ethernet interface       identifiant matériel: 2       nom logique: docker0       numéro de série: 02:42:a3:d4:58:d8       fonctionnalités: ethernet physical       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes

everyone I am a newbie to linux. Yesterday I have installed Ubuntu 18.04.4 LTS on my Lenovo e41-25 laptop and it shows Wifi adapter not found but when I installed Ubuntu the wifi was working but after I reboot my laptop,it shows wifi adapter not found and I am unable to access my wifi with it. If there is any solution available please help me.I am newbie to linux

Please see my setup here:

NAT is set up here:

Host-only adapter is enabled here:

network for virtual box is configured here:

then I set up interface on the server like this:

then I run sudo netplan apply and I should be all set. I can ping myself on the server:

but can't ping the server from my local computer:

Hence the network isn't actually connected to the Internet.What am I doing wrong here ?

I have recently installed Ubuntu 19.10 on my new Windows laptop in dual boot. When I try to connect to a network, some wireless networks are shown but mine isn't (in Windows it does appear).

At first, my wifi card was UNCLAIMED so I downloaded the driver in the 'Additional' Drivers app. I can connect with Ethernet, but my WiFi network isn't shown either in the Wifi Settings or in the 'Select a wireless network' popup. I have tried rebooting several times, and using another network manager (Wicd).

I am new to Linux, please help :)

yesterday I have install the new Ubuntu 19.10 on my laptop, and the WiFi its not working , I have try to install the wireless driver but the same , I have saw how the Ubuntu don't recognise my Wireless driver.If somebody know how I can repair that please text me , thank you very much

I setup an ubuntu server with nginx. hostname tleis.nl. I can access the url locally www.tleis.nl. From outside the server I can ping the server tleis.nl. I can also access the nginx website via its ip 192.168.x.y. But when I try to access www.tleis.nl. It fails.I have the port forwarding setting on my router to forward public ip access to my local server's ip 192.168.x.y.What could the issue be?

I'm using https://github.com/hanazuki/docker-ubuntu-cups to run cups PDF on an ubuntu docker. I mapped like this:

sudo docker run -it -p 6310:631 -e ADMIN_USERNAME=admin -e CUPS_ADMIN_PASSWORD=admin -v $HOME/cups:/var/spool/cups-pdf/ANONYMOUS cups

so my 6130 port is 613 inside cups. I can access the web admin panel. However, I tried adding several printer types from this list:

Add PrinterLocal Printers:     CUPS-BRF (Virtual Braille BRF Printer)CUPS-PDF (Virtual PDF Printer)Discovered Network Printers:    Other Network Printers:     Backend Error HandlerInternet Printing Protocol (https)AppSocket/HP JetDirectInternet Printing Protocol (ipps)Internet Printing Protocol (ipp)Internet Printing Protocol (http)LPD/LPR Host or Printer

but none of them appears in my firefox (which is in the same machine) when I try to print something. I checked "share printer" in all of them.

How do I make a printer appear at firefox so I can print and get a PDF from it?

I have been fighting with the interface of my ubuntu 16 lts server to connect to a wifi on startup. Currently I connect using wpa_supplicant and dhclient. If I do both manually, I get connected without problems.When I want both to launch from startup, it seems wpa_supplicant is working fine but not dhclient.I have set up the service with this configuration:

[Unit]Description= DHCP ClientBefore=network.target[Service]Type=simpleExecStart=/sbin/dhclient wlp58s0 -vExecStop=/sbin/dhclient wlp58s0 -r[Install]WantedBy=multi-user.target

And it seems it loads ok, connects and after some seconds it disconnects...

● dhclient.service - DHCP Client   Loaded: loaded (/etc/systemd/system/dhclient.service; enabled; vendor preset: enabled)   Active: inactive (dead) since mar 2020-04-07 16:13:06 CEST; 18min ago  Process: 1862 ExecStop=/sbin/dhclient wlp58s0 -r (code=exited, status=0/SUCCESS)  Process: 809 ExecStart=/sbin/dhclient wlp58s0 -v (code=exited, status=0/SUCCESS) Main PID: 809 (code=exited, status=0/SUCCESS)abr 07 16:12:55 RB1B0-190625AB dhclient[809]: DHCPOFFER of 192.168.0.33 from 192.168.0.1abr 07 16:12:55 RB1B0-190625AB dhclient[809]: DHCPREQUEST of 192.168.0.33 on wlp58s0 to 255.255.255.255 port 67 (xid=0x42ec0a9b)abr 07 16:12:55 RB1B0-190625AB dhclient[809]: DHCPOFFER of 192.168.0.33 from 192.168.0.1abr 07 16:12:55 RB1B0-190625AB dhclient[809]: DHCPACK of 192.168.0.33 from 192.168.0.1abr 07 16:12:55 RB1B0-190625AB dhclient[809]: DHCPACK of 192.168.0.33 from 192.168.0.1abr 07 16:13:05 RB1B0-190625AB dhclient[809]: bound to 192.168.0.33 -- renewal in 42791 seconds.abr 07 16:13:05 RB1B0-190625AB dhclient[809]: bound to 192.168.0.33 -- renewal in 42791 seconds.abr 07 16:13:05 RB1B0-190625AB dhclient[1862]: Killed old client processabr 07 16:13:05 RB1B0-190625AB dhclient[1862]: Killed old client processabr 07 16:13:06 RB1B0-190625AB dhclient[1862]: DHCPRELEASE on wlp58s0 to 192.168.0.1 port 67 (xid=0x636812e7)

More details in the syslog seems that the bound was ok

Apr  7 16:13:05 RB1B0-190625AB dhclient[809]: bound to 192.168.0.33 -- renewal in 42791 seconds.Apr  7 16:13:05 RB1B0-190625AB dhclient[809]: bound to 192.168.0.33 -- renewal in 42791 seconds.Apr  7 16:13:05 RB1B0-190625AB dhclient[1862]: Killed old client processApr  7 16:13:05 RB1B0-190625AB dhclient[1862]: Killed old client processApr  7 16:13:06 RB1B0-190625AB dhclient[1862]: DHCPRELEASE on wlp58s0 to 192.168.0.1 port 67 (xid=0x636812e7)

First of all it seems there are duplicated messages for everything. I don't think this is normal and I have been looking for possible duplicated processes, but it does not seem so.

Also, I paste my network/interfaces

allow-hotplug wlp58s0iface wlp58s0 inet dhcpwpa-driver wext#pre-up killall -q wpa_supplicantwpa-roam /etc/wpa_supplicant.conf

This is a copy of a post I made to photo.stackexchange.com. I felt I should put it here due to the more technical side of the question, and it barely relating to photography.

I have a Nikon D5300 with built in WiFi. I'm interested in tinkering/hacking with its network protocol and transferring photos wirelessly.

After looking into the network protocols and ports, I found this:

http://cdn-10.nikon-cdn.com/pdf/manuals/dslr/D4NWG_En_01.pdf

It talks about how you can use FTP on some WiFi chips in different camera models, but I'm not sure if it includes mine.

I know there are two ports used for the connection; one is 15740 to transfer the photos, and one is 5353 to connect. I also found that the chip uses the Media Transfer Protocol (MTP).

Is there a way I can directly browse or transfer pictures from Ubuntu?

I am trying to configure a DHCP server on a Ubuntu 18.04 virtual machine. I am able to configure it with the following configuration:

File: /etc/dhcp/dhcpd.conf

Settings:

default-lease-time 600;max-lease-time 7200;option subnet-mask 255.255.255.0;option broadcast-address 192.168.1.255;option routers 192.168.1.254;option domain-name-servers 192.168.1.1, 192.168.1.2;option domain-name "mydomain.example";subnet 192.168.1.0 netmask 255.255.255.0 {range 192.168.1.10 192.168.1.100;range 192.168.1.150 192.168.1.200;} 

When I run

sudo systemctl restart isc-dhcp-server

and then

sudo systemctl status isc-dhcp-server.service

I see that the dhcp server is active and running, but it is not giving out IPs to the other virtual machines on the local network.

The dhcp server is setup to eth1:

File: /etc/default/isc-dhcp-server

Settings:

INTERFACESv4="eth1"INTERFACESv6=""

I already setup the eth0 and eth1 with netplan as follow:

network:  version: 2  renderer: networkd  ethernets:    eth0:      dhcp4: true      dhcp6: no    eth1:      dhcp4: no      addresses: [192.168.2.1/24]      gateway4: 192.168.2.1      nameservers:        addresses: [8.8.8.8]

eth0 is setup to 192.168.1.15 which is connecting to an external network.

Any suggestion is welcome.

Thank you,

Server : Ubuntu Server 18.04.4

Router : pfSense 2.4.4

Switch : tp-link TL-SG1016DE

The Short : How do I configure multiple NIC on the same subnet/VLAN? Would like traffic that goes in one NIC to go out the same interface. This was working not sure what happened.

The Long:

Not sure what happened but my configuration seems to have borked itself and I am unable to ping or access the onboard NIC enp9s0. I'm at a loss as it was working before.

Accessing the VM's that are behind enp4s0f1 seem to be functioning correctly.

Attempts to PING or SSH into enp9s0 (192.168.2.2) fails.

If I delete the the ARP entry on pfSense for 192.168.2.2 then I am able to PING or SSH into enp9s0 (192.168.2.2) but will drop off shortly there after.

If however I then start a PING from within 192.168.2.2, after SSHing in, out to to another device on the LAN, the the connection remains stable.

However viewing the ARP table on pfSense now show the wrong MAC address associated with 192.168.2.2. It show the MAC address of enp4s0f1 rather than enp9s0.

Furthermore the ARP on the HOST shows matching hardware address that I have not seen before.

EDIT: The ARP on the HOST is showing the MAC address of the NIC on pfSense.

The three following NIC's are installed:

onboard : enp9s0 ( MACADDRESS:ad )

dual port : enp4s0f0 ( MACADDRESS:74 ) ; enp4s0f1 ( MACADDRESS:75 )

single port : enp7s0 ( MACADDRESS:ba )

#arpAddress                  HWtype  HWaddress           Flags Mask            IfaceHOSTNAME.localdomain              (incomplete)                              enp4s0f1_gateway                 ether   MACADDRESS:e1   C                            enp4s0f1_gateway                 ether   MACADDRESS:e1   C                            enp9s0    enp4s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                inet 192.168.2.4  netmask 255.255.255.0  broadcast 192.168.2.255                ether MACADDRESS:74  txqueuelen 1000  (Ethernet)                RX packets 46104  bytes 3302633 (3.3 MB)                RX errors 0  dropped 30263  overruns 0  frame 0                TX packets 821  bytes 66602 (66.6 KB)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0                device memory 0xf6420000-f643ffff          enp4s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                inet 192.168.2.5  netmask 255.255.255.0  broadcast 192.168.2.255                ether MACADDRESS:75  txqueuelen 1000  (Ethernet)                RX packets 106881  bytes 10461480 (10.4 MB)                RX errors 0  dropped 30268  overruns 0  frame 0                TX packets 72174  bytes 61517403 (61.5 MB)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0                device memory 0xf6400000-f641ffff          enp7s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500                ether MACADDRESS:ba  txqueuelen 1000  (Ethernet)                RX packets 0  bytes 0 (0.0 B)                RX errors 0  dropped 0  overruns 0  frame 0                TX packets 0  bytes 0 (0.0 B)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        enp9s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                inet 192.168.2.2  netmask 255.255.255.0  broadcast 192.168.2.255                ether MACADDRESS:ad  txqueuelen 1000  (Ethernet)                RX packets 46202  bytes 3022408 (3.0 MB)                RX errors 0  dropped 30259  overruns 0  frame 0                TX packets 10206  bytes 2482014 (2.4 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                loop  txqueuelen 1000  (Local Loopback)                RX packets 7175  bytes 51455539 (51.4 MB)                RX errors 0  dropped 0  overruns 0  frame 0                TX packets 7175  bytes 51455539 (51.4 MB)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        macvtap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                ether MACADDRESS:c3  txqueuelen 500  (Ethernet)                RX packets 72168  bytes 7205751 (7.2 MB)                RX errors 4  dropped 4  overruns 0  frame 0                TX packets 22353  bytes 6380506 (6.3 MB)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        macvtap1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                ether MACADDRESS:c7  txqueuelen 500  (Ethernet)                RX packets 44247  bytes 3085964 (3.0 MB)                RX errors 0  dropped 0  overruns 0  frame 0                TX packets 820  bytes 66536 (66.5 KB)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500                inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255                ether MACADDRESS:bb  txqueuelen 1000  (Ethernet)                RX packets 0  bytes 0 (0.0 B)                RX errors 0  dropped 0  overruns 0  frame 0                TX packets 0  bytes 0 (0.0 B)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500                ether MACADDRESS:bb  txqueuelen 1000  (Ethernet)                RX packets 0  bytes 0 (0.0 B)                RX errors 0  dropped 0  overruns 0  frame 0                TX packets 0  bytes 0 (0.0 B)                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0        ----------------------------------------● 1: lo               Link File: /lib/systemd/network/99-default.link            Network File: n/a                    Type: loopback                   State: carrier (unmanaged)                 Address: 127.0.0.1● 2: enp7s0               Link File: /run/systemd/network/10-netplan-enp7s0.link            Network File: /run/systemd/network/10-netplan-enp7s0.network                    Type: ether                   State: no-carrier (configuring)                    Path: pci-0000:07:00.0                  Driver: r8169                  Vendor: Realtek Semiconductor Co., Ltd.                   Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (TG-3468 Gigabit PCI Express Network Adapter)              HW Address: MACADDRESS:ba (TP-LINK TECHNOLOGIES CO.,LTD.)                     DNS: 192.168.2.1          Search Domains: localdomain● 3: enp9s0               Link File: /run/systemd/network/10-netplan-enp9s0.link            Network File: /run/systemd/network/10-netplan-enp9s0.network                    Type: ether                   State: routable (configured)                    Path: pci-0000:09:00.0                  Driver: r8169                  Vendor: Realtek Semiconductor Co., Ltd.                   Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (Motherboard (one of many))              HW Address: MACADDRESS:ad (ASRock Incorporation)                 Address: 192.168.2.2                 Gateway: 192.168.2.1 (TP-LINK TECHNOLOGIES CO.,LTD.)                     DNS: 192.168.2.1          Search Domains: localdomain            Connected To: No Site Name on port 192.168.1.120 (No Site Name)● 4: enp4s0f0               Link File: /run/systemd/network/10-netplan-enp4s0f0.link            Network File: /run/systemd/network/10-netplan-enp4s0f0.network                    Type: ether                   State: routable (configured)                    Path: pci-0000:04:00.0                  Driver: igb                  Vendor: Intel Corporation                   Model: 82576 Gigabit Network Connection (Gigabit ET Dual Port Server Adapter)              HW Address: MACADDRESS:74 (Shenzhen Lianrui Electronics Co.,Ltd)                 Address: 192.168.2.4                 Gateway: 192.168.2.1                     DNS: 192.168.2.1          Search Domains: localdomain            Connected To: No Site Name on port 192.168.1.120 (No Site Name)● 5: enp4s0f1               Link File: /run/systemd/network/10-netplan-enp4s0f1.link            Network File: /run/systemd/network/10-netplan-enp4s0f1.network                    Type: ether                   State: routable (configured)                    Path: pci-0000:04:00.1                  Driver: igb                  Vendor: Intel Corporation                   Model: 82576 Gigabit Network Connection (Gigabit ET Dual Port Server Adapter)              HW Address: MACADDRESS:75 (Shenzhen Lianrui Electronics Co.,Ltd)                 Address: 192.168.2.5                 Gateway: 192.168.2.1 (TP-LINK TECHNOLOGIES CO.,LTD.)                     DNS: 192.168.2.1          Search Domains: localdomain            Connected To: No Site Name on port 192.168.1.120 (No Site Name)● 6: virbr0               Link File: /lib/systemd/network/99-default.link            Network File: n/a                    Type: ether                   State: no-carrier (unmanaged)                  Driver: bridge              HW Address: MACADDRESS:bb                 Address: 192.168.122.1● 7: virbr0-nic               Link File: /lib/systemd/network/99-default.link            Network File: n/a                    Type: ether                   State: off (unmanaged)                  Driver: tun              HW Address: MACADDRESS:bb● 8: macvtap0               Link File: /lib/systemd/network/99-default.link            Network File: n/a                    Type: ether                   State: carrier (unmanaged)                  Driver: macvlan              HW Address: MACADDRESS:c3● 9: macvtap1               Link File: /lib/systemd/network/99-default.link            Network File: n/a                    Type: ether                   State: carrier (unmanaged)                  Driver: macvlan              HW Address: MACADDRESS:c7        ----------------------------------------        Kernel IP routing table        Destination     Gateway         Genmask         Flags Metric Ref    Use Iface        0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 enp4s0f1        0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 enp9s0        0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 enp4s0f0        192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 enp4s0f1        192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 enp9s0        192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 enp4s0f0        192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0        ----------------------------------------        ethtool enp9s0        Settings for enp9s0:            Supported ports: [ TP MII ]            Supported link modes:   10baseT/Half 10baseT/Full                                     100baseT/Half 100baseT/Full                                     1000baseT/Half 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: Symmetric Receive-only            Advertised auto-negotiation: Yes            Advertised FEC modes: Not reported            Link partner advertised link modes:  10baseT/Half 10baseT/Full                                                  100baseT/Half 100baseT/Full                                                  1000baseT/Full             Link partner advertised pause frame use: No            Link partner advertised auto-negotiation: Yes            Link partner advertised FEC modes: Not reported            Speed: 1000Mb/s            Duplex: Full            Port: MII            PHYAD: 0            Transceiver: internal            Auto-negotiation: on            Supports Wake-on: pumbg            Wake-on: g            Current message level: 0x00000033 (51)                           drv probe ifdown ifup            Link detected: yes        ----------------------------------------        Apr 05 17:53:01 systemname kernel: r8169 0000:09:00.0 enp9s0: renamed from eth1        Apr 05 17:53:01 systemname kernel: r8169 0000:09:00.0 enp9s0: link down        Apr 05 17:53:01 systemname kernel: r8169 0000:09:00.0 enp9s0: link down        Apr 05 17:53:02 systemname systemd-networkd[929]: enp9s0: Link UP        Apr 05 17:53:05 systemname systemd-networkd[929]: enp9s0: Gained carrier        Apr 05 17:53:05 systemname systemd-networkd[929]: enp9s0: Configured        Apr 05 17:53:05 systemname kernel: r8169 0000:09:00.0 enp9s0: link up        ----------------------------------------        04:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)        04:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)        07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)        09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)        ----------------------------------------        modinfo r8169        filename:       /lib/modules/4.15.0-91-generic/kernel/drivers/net/ethernet/realtek/r8169.ko        firmware:       rtl_nic/rtl8107e-2.fw        firmware:       rtl_nic/rtl8107e-1.fw        firmware:       rtl_nic/rtl8168h-2.fw        firmware:       rtl_nic/rtl8168h-1.fw        firmware:       rtl_nic/rtl8168g-3.fw        firmware:       rtl_nic/rtl8168g-2.fw        firmware:       rtl_nic/rtl8106e-2.fw        firmware:       rtl_nic/rtl8106e-1.fw        firmware:       rtl_nic/rtl8411-2.fw        firmware:       rtl_nic/rtl8411-1.fw        firmware:       rtl_nic/rtl8402-1.fw        firmware:       rtl_nic/rtl8168f-2.fw        firmware:       rtl_nic/rtl8168f-1.fw        firmware:       rtl_nic/rtl8105e-1.fw        firmware:       rtl_nic/rtl8168e-3.fw        firmware:       rtl_nic/rtl8168e-2.fw        firmware:       rtl_nic/rtl8168e-1.fw        firmware:       rtl_nic/rtl8168d-2.fw        firmware:       rtl_nic/rtl8168d-1.fw        version:        2.3LK-NAPI        license:        GPL        description:    RealTek RTL-8169 Gigabit Ethernet driver        author:         Realtek and the Linux r8169 crew <netdev@vger.kernel.org>        srcversion:     68D71F7AFFEBF88AE55BB02        alias:          pci:v00000001d00008168sv*sd00002410bc*sc*i*        alias:          pci:v00001737d00001032sv*sd00000024bc*sc*i*        alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*        alias:          pci:v00001259d0000C107sv*sd*bc*sc*i*        alias:          pci:v00001186d00004302sv*sd*bc*sc*i*        alias:          pci:v00001186d00004300sv*sd*bc*sc*i*        alias:          pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*        alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*        alias:          pci:v000010FFd00008168sv*sd*bc*sc*i*        alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*        alias:          pci:v000010ECd00008167sv*sd*bc*sc*i*        alias:          pci:v000010ECd00008161sv*sd*bc*sc*i*        alias:          pci:v000010ECd00008136sv*sd*bc*sc*i*        alias:          pci:v000010ECd00008129sv*sd*bc*sc*i*        alias:          pci:v000010ECd00002600sv*sd*bc*sc*i*        alias:          pci:v000010ECd00002502sv*sd*bc*sc*i*        depends:        mii        retpoline:      Y        intree:         Y        name:           r8169        vermagic:       4.15.0-91-generic SMP mod_unload         signat:         PKCS#7        signer:                 sig_key:                sig_hashalgo:   md4        parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)        parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)        ----------------------------------------        smod | grep r8169        r8169                  86016  0        mii                    16384  1 r8169        ----------------------------------------        [    1.825213] r8169 0000:09:00.0 eth1: RTL8168h/8111h at 0x        (ptrval), 70:85:c2:f4:23:ad, XID 14100800 IRQ 54        [    1.833730] r8169 0000:09:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]        [    1.916285] r8169 0000:09:00.0 enp9s0: renamed from eth1        [    2.550164] igb 0000:04:00.1: added PHC on eth1        [    2.550169] igb 0000:04:00.1: eth1: (PCIe:2.5Gb/s:Width x1) 6c:b3:11:1c:a0:75        [    2.550175] igb 0000:04:00.1: eth1: PBA No: Unknown        [    2.550733] igb 0000:04:00.1 enp4s0f1: renamed from eth1        [    1.916285] r8169 0000:09:00.0 enp9s0: renamed from eth1        [    5.694631] r8169 0000:09:00.0 enp9s0: link down        [    5.694633] r8169 0000:09:00.0 enp9s0: link down        [    5.694711] IPv6: ADDRCONF(NETDEV_UP): enp9s0: link is not ready        [    8.803624] r8169 0000:09:00.0 enp9s0: link up        [    8.803628] IPv6: ADDRCONF(NETDEV_CHANGE): enp9s0: link becomes ready        [    1.812022] r8169 0000:07:00.0 eth0: RTL8168e/8111e at 0x        (ptrval), 7c:8b:ca:03:76:ba, XID 0c200000 IRQ 53        [    1.812023] r8169 0000:07:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]        [    1.868198] r8169 0000:07:00.0 enp7s0: renamed from eth0        [    2.334161] igb 0000:04:00.0: added PHC on eth0        [    2.334165] igb 0000:04:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 6c:b3:11:1c:a0:74        [    2.334170] igb 0000:04:00.0: eth0: PBA No: Unknown        [    2.596602] igb 0000:04:00.0 enp4s0f0: renamed from eth0        [    1.868198] r8169 0000:07:00.0 enp7s0: renamed from eth0        [    5.867125] r8169 0000:07:00.0 enp7s0: link down        [    5.867187] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready        [    2.550733] igb 0000:04:00.1 enp4s0f1: renamed from eth1        [    5.391859] IPv6: ADDRCONF(NETDEV_UP): enp4s0f1: link is not ready        [    7.712704] igb 0000:04:00.1 enp4s0f1: igb: enp4s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX        [    7.928351] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0f1: link becomes ready        [    2.596602] igb 0000:04:00.0 enp4s0f0: renamed from eth0        [    5.639862] IPv6: ADDRCONF(NETDEV_UP): enp4s0f0: link is not ready        [   13.868125] igb 0000:04:00.0 enp4s0f0: igb: enp4s0f0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX        [   13.868266] igb 0000:04:00.0 enp4s0f0: Link Speed was downgraded by SmartSpeed        [   13.868513] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0f0: link becomes ready        ----------------------------------------        YAML FILES        01-netcfg.yaml        network:          version: 2          renderer: networkd          ethernets:            enp9s0:              match:                macaddress: MACADDRESS:ad              addresses: [192.168.2.2/24]              gateway4: 192.168.2.1              nameservers:                addresses: [192.168.2.1,208.67.222.222,208.67.220.220]                search: [localdomain]        02-netcfg.yaml        network:          version: 2          renderer: networkd          ethernets:            enp7s0:              match:                macaddress: MACADDRESS:ba              addresses: [192.168.2.3/24]              gateway4: 192.168.2.1              nameservers:                addresses: [192.168.2.1,208.67.222.222,208.67.220.220]                search: [localdomain]        03-netcfg.yaml        network:          version: 2          renderer: networkd          ethernets:            enp4s0f0:              match:                macaddress: MACADDRESS:74              addresses: [192.168.2.4/24]              gateway4: 192.168.2.1              nameservers:                addresses: [192.168.2.1,208.67.222.222,208.67.220.220]                search: [localdomain]        04-netcfg.yaml        network:          version: 2          renderer: networkd          ethernets:            enp4s0f1:              match:                macaddress: MACADDRESS:75              addresses: [192.168.2.5/24]              gateway4: 192.168.2.1              nameservers:                addresses: [192.168.2.1,208.67.222.222,208.67.220.220]                search: [localdomain]

I have an error, but not a spelling error.

Here is my netplan config:

network:  ethernets:    ens32:      addresses: [172.16.120.74/16]      nameservers:        addresses: [127.0.0.53, 172.16.1.5]  renderer: networkd  version: '2'

This displays the error:

Error in network definition //etc/netplan/99.clw_netcfg.yaml line 3 column 6: unknown key nameservers

Does anyone have any ideas?

I want to use the webcam on my laptop as video device on my pc to use it for video conferencing etc.

So I not just want to stream the video. I actually want to "stream" the entire device over network.