Quantcast
Channel: Active questions tagged networking - Ask Ubuntu
Viewing all 23091 articles
Browse latest View live

Need help getting ASUS USB-AC53 Nano (USB wifi adapter) working on Ubuntu 16.04

$
0
0

Very much a noob but I am trying to get this wireless wi-fi adapter to work on an old computer my sister uses. Old wireless wifi adapter was an ASUS but it died. Any step by step help would be appreciated. I have computer on a wired connection currently. Thanks.


Ubuntu 19.10 Wireless Not Working after Resume

$
0
0

The problem

Wifi seems to connect fine after system bootup or reboot, but if I suspend my computer (which is a laptop, so this is happening whenever I close the laptop lid), when the computer wakes, wifi indefinitely attempts to connect and fails.

Details

I've been trying to diagnose what's going on primarily by looking at the output ofjournalctl --follow.

Here's the bad version (where authentication seems to time out every time), which I recorded after opening my laptop from a suspended state:

$ journalctl --follow-- Logs begin at Thu 2019-11-14 11:44:13 EST. --Nov 29 10:09:56 polystichum kernel: wlp3s0: authentication with 38:70:0c:3e:a0:c5 timed outNov 29 10:09:56 polystichum NetworkManager[9032]: <info>  [1575040196.5416] device (wlp3s0): supplicant interface state: authenticating -> disconnectedNov 29 10:09:56 polystichum NetworkManager[9032]: <info>  [1575040196.6415] device (wlp3s0): supplicant interface state: disconnected -> scanningNov 29 10:09:59 polystichum wpa_supplicant[9052]: wlp3s0: SME: Trying to authenticate with 38:70:0c:3e:a0:c5 (SSID='ARRIS-A0C2-5G' freq=5745 MHz)Nov 29 10:09:59 polystichum kernel: wlp3s0: authenticate with 38:70:0c:3e:a0:c5Nov 29 10:09:59 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 1/3)Nov 29 10:09:59 polystichum NetworkManager[9032]: <info>  [1575040199.5399] device (wlp3s0): supplicant interface state: scanning -> authenticatingNov 29 10:10:00 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 2/3)Nov 29 10:10:00 polystichum systemd[1]: NetworkManager-dispatcher.service: Succeeded.Nov 29 10:10:01 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 3/3)Nov 29 10:10:02 polystichum kernel: wlp3s0: authentication with 38:70:0c:3e:a0:c5 timed outNov 29 10:10:02 polystichum NetworkManager[9032]: <info>  [1575040202.5534] device (wlp3s0): supplicant interface state: authenticating -> disconnectedNov 29 10:10:03 polystichum NetworkManager[9032]: <info>  [1575040203.0548] device (wlp3s0): supplicant interface state: disconnected -> scanningNov 29 10:10:05 polystichum wpa_supplicant[9052]: wlp3s0: SME: Trying to authenticate with 38:70:0c:3e:a0:c5 (SSID='ARRIS-A0C2-5G' freq=5745 MHz)Nov 29 10:10:05 polystichum kernel: wlp3s0: authenticate with 38:70:0c:3e:a0:c5Nov 29 10:10:05 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 1/3)Nov 29 10:10:05 polystichum NetworkManager[9032]: <info>  [1575040205.9801] device (wlp3s0): supplicant interface state: scanning -> authenticatingNov 29 10:10:06 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 2/3)Nov 29 10:10:07 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 3/3)Nov 29 10:10:08 polystichum kernel: wlp3s0: authentication with 38:70:0c:3e:a0:c5 timed outNov 29 10:10:08 polystichum NetworkManager[9032]: <info>  [1575040208.5791] device (wlp3s0): supplicant interface state: authenticating -> disconnectedNov 29 10:10:09 polystichum NetworkManager[9032]: <info>  [1575040209.5787] device (wlp3s0): supplicant interface state: disconnected -> scanningNov 29 10:10:12 polystichum wpa_supplicant[9052]: wlp3s0: SME: Trying to authenticate with 38:70:0c:3e:a0:c5 (SSID='ARRIS-A0C2-5G' freq=5745 MHz)Nov 29 10:10:12 polystichum kernel: wlp3s0: authenticate with 38:70:0c:3e:a0:c5Nov 29 10:10:12 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 1/3)Nov 29 10:10:12 polystichum NetworkManager[9032]: <info>  [1575040212.5327] device (wlp3s0): supplicant interface state: scanning -> authenticatingNov 29 10:10:13 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 2/3)Nov 29 10:10:14 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 3/3)Nov 29 10:10:15 polystichum kernel: wlp3s0: authentication with 38:70:0c:3e:a0:c5 timed out

And here's the good version, which I recorded after rebooting my laptop with the wifi disabled and then enabling it after I'd started journalctl --follow:

$ journalctl --follow-- Logs begin at Thu 2019-11-14 11:44:13 EST. --Nov 29 10:20:18 polystichum gnome-software[1991]: not handling error failed for action get-category-apps: persistent network error: Get https://api.snapcraft.io/api/v1/snaps/search?confinement=strict%2Cclassic&fields=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_384%2Csummary%2Cdescription%2Cbinary_filesize%2Cdownload_url%2Clast_updated%2Cpackage_name%2Cprices%2Cpublisher%2Cratings_average%2Crevision%2Csnap_id%2Clicense%2Cbase%2Cmedia%2Csupport_url%2Ccontact%2Ctitle%2Ccontent%2Cversion%2Corigin%2Cdeveloper_id%2Cdeveloper_name%2Cdeveloper_validation%2Cprivate%2Cconfinement%2Ccommon_ids&scope=wide&section=photo-and-video: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolutionNov 29 10:20:18 polystichum systemd[1]: systemd-localed.service: Succeeded.Nov 29 10:20:18 polystichum PackageKit[1222]: resolve transaction /231_ecddddcc from uid 1000 finished with success after 421msNov 29 10:20:18 polystichum gnome-software[1991]: hiding category graphics featured applications: found only 1 to show, need at least 9Nov 29 10:20:19 polystichum PackageKit[1222]: resolve transaction /232_ebdebccd from uid 1000 finished with success after 369msNov 29 10:20:19 polystichum tracker-store[1909]: OKNov 29 10:20:19 polystichum systemd[1412]: tracker-store.service: Succeeded.Nov 29 10:20:19 polystichum PackageKit[1222]: resolve transaction /233_cadbceba from uid 1000 finished with success after 372msNov 29 10:20:19 polystichum gnome-software[1991]: Only 8 apps for popular list, hidingNov 29 10:20:23 polystichum systemd[1]: systemd-timedated.service: Succeeded.Nov 29 10:20:36 polystichum geoclue[1219]: Service not used for 60 seconds. Shutting down..Nov 29 10:20:36 polystichum systemd[1]: geoclue.service: Main process exited, code=killed, status=15/TERMNov 29 10:20:36 polystichum systemd[1]: geoclue.service: Succeeded.Nov 29 10:20:45 polystichum xdg-desktop-por[1586]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowedNov 29 10:20:48 polystichum gnome-software-service.desktop[2294]: Unable to acquire bus name 'org.gnome.Software'Nov 29 10:20:50 polystichum gnome-shell[1643]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.123/org/ayatana/NotificationItem/software_update_availableNov 29 10:20:50 polystichum gnome-shell[1643]: [AppIndicatorSupport-FATAL] unable to update overlay iconNov 29 10:20:50 polystichum gnome-shell[1643]: [AppIndicatorSupport-FATAL] unable to update overlay iconNov 29 10:20:52 polystichum kernel: iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio.Nov 29 10:20:52 polystichum kernel: iwlwifi 0000:03:00.0: reporting RF_KILL (radio enabled)Nov 29 10:20:52 polystichum systemd[1]: Starting Load/Save RF Kill Switch Status...Nov 29 10:20:52 polystichum systemd[1]: Started Load/Save RF Kill Switch Status.Nov 29 10:20:52 polystichum kernel: usb 1-1.4: new full-speed USB device number 5 using ehci-pciNov 29 10:20:52 polystichum kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6, bcdDevice= 1.12Nov 29 10:20:52 polystichum kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3Nov 29 10:20:52 polystichum kernel: usb 1-1.4: Product: BCM20702A0Nov 29 10:20:52 polystichum kernel: usb 1-1.4: Manufacturer: Broadcom CorpNov 29 10:20:52 polystichum kernel: usb 1-1.4: SerialNumber: 9C2A7081F312Nov 29 10:20:52 polystichum mtp-probe[2342]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"Nov 29 10:20:52 polystichum mtp-probe[2342]: bus: 1, device: 5 was not an MTP deviceNov 29 10:20:52 polystichum kernel: Bluetooth: Core ver 2.22Nov 29 10:20:52 polystichum kernel: NET: Registered protocol family 31Nov 29 10:20:52 polystichum kernel: Bluetooth: HCI device and connection manager initializedNov 29 10:20:52 polystichum kernel: Bluetooth: HCI socket layer initializedNov 29 10:20:52 polystichum kernel: Bluetooth: L2CAP socket layer initializedNov 29 10:20:52 polystichum kernel: Bluetooth: SCO socket layer initializedNov 29 10:20:52 polystichum kernel: usbcore: registered new interface driver btusbNov 29 10:20:53 polystichum mtp-probe[2355]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"Nov 29 10:20:53 polystichum mtp-probe[2355]: bus: 1, device: 5 was not an MTP deviceNov 29 10:20:53 polystichum systemd[1]: Starting Bluetooth service...Nov 29 10:20:53 polystichum bluetoothd[2360]: Bluetooth daemon 5.50Nov 29 10:20:53 polystichum systemd[1]: Started Bluetooth service.Nov 29 10:20:53 polystichum systemd[1]: Reached target Bluetooth.Nov 29 10:20:53 polystichum bluetoothd[2360]: Starting SDP serverNov 29 10:20:53 polystichum dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.577' (uid=0 pid=2360 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")Nov 29 10:20:53 polystichum kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3Nov 29 10:20:53 polystichum kernel: Bluetooth: BNEP filters: protocol multicastNov 29 10:20:53 polystichum kernel: Bluetooth: BNEP socket layer initializedNov 29 10:20:53 polystichum bluetoothd[2360]: Bluetooth management interface 1.14 initializedNov 29 10:20:53 polystichum NetworkManager[944]: <info>  [1575040853.0706] bluez: use BlueZ version 5Nov 29 10:20:53 polystichum systemd[1]: Starting Hostname Service...Nov 29 10:20:53 polystichum kernel: Bluetooth: hci0: BCM: chip id 63Nov 29 10:20:53 polystichum kernel: Bluetooth: hci0: BCM: features 0x07Nov 29 10:20:53 polystichum kernel: Bluetooth: hci0: BCM20702ANov 29 10:20:53 polystichum kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000Nov 29 10:20:53 polystichum kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2Nov 29 10:20:53 polystichum kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e6.hcd not foundNov 29 10:20:53 polystichum kernel: Bluetooth: RFCOMM TTY layer initializedNov 29 10:20:53 polystichum kernel: Bluetooth: RFCOMM socket layer initializedNov 29 10:20:53 polystichum kernel: Bluetooth: RFCOMM ver 1.11Nov 29 10:20:53 polystichum NetworkManager[944]: <info>  [1575040853.1843] bluez5: NAP: added interface 9C:2A:70:81:F3:12Nov 29 10:20:53 polystichum bluetoothd[2360]: Endpoint registered: sender=:1.186 path=/MediaEndpoint/A2DPSink/sbcNov 29 10:20:53 polystichum bluetoothd[2360]: Endpoint registered: sender=:1.186 path=/MediaEndpoint/A2DPSource/sbcNov 29 10:20:53 polystichum dbus-daemon[941]: [system] Successfully activated service 'org.freedesktop.hostname1'Nov 29 10:20:53 polystichum systemd[1]: Started Hostname Service.Nov 29 10:20:55 polystichum gnome-software[1991]: not GsPlugin error snapd-error-quark:1: Failed to write to snapd: Operation was cancelledNov 29 10:20:55 polystichum gnome-software[1991]: not handling error failed for action refine: Failed to write to snapd: Operation was cancelledNov 29 10:20:58 polystichum systemd[1]: systemd-rfkill.service: Succeeded.Nov 29 10:20:58 polystichum NetworkManager[944]: <info>  [1575040858.1624] manager: rfkill: Wi-Fi hardware radio set enabledNov 29 10:20:58 polystichum systemd[1]: Starting Load/Save RF Kill Switch Status...Nov 29 10:20:58 polystichum systemd[1]: Started Load/Save RF Kill Switch Status.Nov 29 10:20:58 polystichum kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0Nov 29 10:20:58 polystichum kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0Nov 29 10:20:58 polystichum NetworkManager[944]: <info>  [1575040858.5702] audit: op="radio-control" arg="wireless-enabled" pid=1643 uid=1000 result="success"Nov 29 10:20:58 polystichum NetworkManager[944]: <info>  [1575040858.5711] manager: rfkill: Wi-Fi now enabled by radio killswitchNov 29 10:20:58 polystichum wpa_supplicant[943]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failedNov 29 10:20:58 polystichum NetworkManager[944]: <info>  [1575040858.6541] sup-iface[0x55a3e0f86920,wlp3s0]: supports 5 scan SSIDsNov 29 10:20:58 polystichum NetworkManager[944]: <info>  [1575040858.6548] device (wlp3s0): supplicant interface state: starting -> readyNov 29 10:20:58 polystichum NetworkManager[944]: <info>  [1575040858.6548] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6506] policy: auto-activating connection 'ARRIS-A0C2-5G' (9e0beb06-0d17-4c0f-b878-2a55277edca0)Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6527] device (wlp3s0): Activation: starting connection 'ARRIS-A0C2-5G' (9e0beb06-0d17-4c0f-b878-2a55277edca0)Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6528] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6559] manager: NetworkManager state is now CONNECTINGNov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6565] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6573] device (wlp3s0): Activation: (wifi) access point 'ARRIS-A0C2-5G' has security, but secrets are required.Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6574] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6578] sup-iface[0x55a3e0f86920,wlp3s0]: wps: type pbc start...Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6617] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6624] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6629] device (wlp3s0): Activation: (wifi) connection 'ARRIS-A0C2-5G' has security, and secrets exist.  No new secrets needed.Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6630] Config: added 'ssid' value 'ARRIS-A0C2-5G'Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6630] Config: added 'scan_ssid' value '1'Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6631] Config: added 'bgscan' value 'simple:30:-80:86400'Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6631] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6631] Config: added 'auth_alg' value 'OPEN'Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6631] Config: added 'psk' value '<hidden>'Nov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: SME: Trying to authenticate with 38:70:0c:3e:a0:c5 (SSID='ARRIS-A0C2-5G' freq=5745 MHz)Nov 29 10:21:01 polystichum kernel: wlp3s0: authenticate with 38:70:0c:3e:a0:c5Nov 29 10:21:01 polystichum kernel: wlp3s0: send auth to 38:70:0c:3e:a0:c5 (try 1/3)Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6925] device (wlp3s0): supplicant interface state: ready -> authenticatingNov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: Trying to associate with 38:70:0c:3e:a0:c5 (SSID='ARRIS-A0C2-5G' freq=5745 MHz)Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.6944] device (wlp3s0): supplicant interface state: authenticating -> associatingNov 29 10:21:01 polystichum kernel: wlp3s0: authenticatedNov 29 10:21:01 polystichum kernel: wlp3s0: waiting for beacon from 38:70:0c:3e:a0:c5Nov 29 10:21:01 polystichum kernel: wlp3s0: associate with 38:70:0c:3e:a0:c5 (try 1/3)Nov 29 10:21:01 polystichum kernel: wlp3s0: RX AssocResp from 38:70:0c:3e:a0:c5 (capab=0x411 status=0 aid=4)Nov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: Associated with 38:70:0c:3e:a0:c5Nov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0Nov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=USNov 29 10:21:01 polystichum kernel: wlp3s0: associatedNov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.8243] device (wlp3s0): supplicant interface state: associating -> 4-way handshakeNov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: WPA: Key negotiation completed with 38:70:0c:3e:a0:c5 [PTK=CCMP GTK=CCMP]Nov 29 10:21:01 polystichum wpa_supplicant[943]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 38:70:0c:3e:a0:c5 completed [id=0 id_str=]Nov 29 10:21:01 polystichum kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes readyNov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.8735] device (wlp3s0): supplicant interface state: 4-way handshake -> completedNov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.8736] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "ARRIS-A0C2-5G"Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.8738] device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.8743] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)Nov 29 10:21:01 polystichum avahi-daemon[926]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::2c9b:8eda:7342:9144.Nov 29 10:21:01 polystichum avahi-daemon[926]: New relevant interface wlp3s0.IPv6 for mDNS.Nov 29 10:21:01 polystichum avahi-daemon[926]: Registering new address record for fe80::2c9b:8eda:7342:9144 on wlp3s0.*.Nov 29 10:21:01 polystichum kernel: wlp3s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 38:70:0c:3e:a0:c5Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9604] dhcp4 (wlp3s0): state changed unknown -> boundNov 29 10:21:01 polystichum avahi-daemon[926]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.0.9.Nov 29 10:21:01 polystichum avahi-daemon[926]: New relevant interface wlp3s0.IPv4 for mDNS.Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9666] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum avahi-daemon[926]: Registering new address record for 192.168.0.9 on wlp3s0.IPv4.Nov 29 10:21:01 polystichum dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=944 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")Nov 29 10:21:01 polystichum systemd[1]: Starting Network Manager Script Dispatcher Service...Nov 29 10:21:01 polystichum whoopsie[1091]: [10:21:01] Cannot reach: https://daisy.ubuntu.comNov 29 10:21:01 polystichum dbus-daemon[941]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'Nov 29 10:21:01 polystichum systemd[1]: Started Network Manager Script Dispatcher Service.Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9949] device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9953] device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')Nov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9960] manager: NetworkManager state is now CONNECTED_LOCALNov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9980] manager: NetworkManager state is now CONNECTED_SITENov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9982] policy: set 'ARRIS-A0C2-5G' (wlp3s0) as default for IPv4 routing and DNSNov 29 10:21:01 polystichum NetworkManager[944]: <info>  [1575040861.9993] device (wlp3s0): Activation: successful, device activated.Nov 29 10:21:02 polystichum gsd-sharing[1804]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.Nov 29 10:21:02 polystichum gsd-sharing[1804]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.Nov 29 10:21:02 polystichum systemd-resolved[897]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Nov 29 10:21:02 polystichum systemd-resolved[897]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.Nov 29 10:21:02 polystichum wpa_supplicant[943]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-44 noise=9999 txrate=27000Nov 29 10:21:02 polystichum NetworkManager[944]: <info>  [1575040862.2098] manager: NetworkManager state is now CONNECTED_GLOBALNov 29 10:21:02 polystichum whoopsie[1091]: [10:21:02] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1Nov 29 10:21:02 polystichum whoopsie[1091]: [10:21:02] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1Nov 29 10:21:02 polystichum whoopsie[1091]: [10:21:02] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1Nov 29 10:21:03 polystichum systemd-timesyncd[898]: Synchronized to time server for the first time 91.189.94.4:123 (ntp.ubuntu.com).Nov 29 10:21:04 polystichum systemd[1]: systemd-rfkill.service: Succeeded.Nov 29 10:21:04 polystichum NetworkManager[944]: <info>  [1575040864.4291] dhcp6 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)Nov 29 10:21:05 polystichum whoopsie[1091]: [10:21:05] online

As you can see, in the second example, it seems like the network connection sets up just fine. Both attempts (good & bad) are using Ubuntu 19.10's wifi set up straight out of the box. It looks like authentication times out in the bad example, but I don't know why that would be happening or how to fix it.

Things I've Tried

I've tried restarting the network manager with sudo systemctl restart network-manager -- that didn't help.

I've tried setting wifi.powersave = 2 in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf as suggested here.

Some system details

$ screenfetch                          ./+o+-       @polystichum                  yyyyy- -yyyyyy+      OS: Ubuntu 19.10 eoan               ://+//////-yyyyyyo      Kernel: x86_64 Linux 5.3.0-23-generic           .++ .:/++++++/-.+sss/`      Uptime: 24m         .:++o:  /++++++++/:--:/-      Packages: 1932        o:+o+:++.`..```.-/oo+++++/     Shell: bash 5.0.3       .:+o:+o/.          `+sssoo+/    Resolution: 1600x900  .++/+:+oo+o:`             /sssooo.   DE: GNOME  /+++//+:`oo+o               /::--:.   WM: GNOME Shell \+/+o+++`o++o               ++////.   WM Theme:   .++.o+++oo+:`             /dddhhh.   GTK Theme: Yaru-dark [GTK2/3]       .+.o+oo:.          `oddhhhh+    Icon Theme: Yaru        \+.++o+o``-````.:ohdhhhhh+     Font: Ubuntu 11         `:o+++ `ohhhhhhhhyo++os:      CPU: Intel Core i7-3667U @ 4x 3.2GHz           .o:`.syhhhhhhh/.oo++o`      GPU: i915drmfb               /osyyyyyyo++ooo+++/     RAM: 2165MiB / 7643MiB                   ````` +oo+++o\:                              `oo++.      $ lspci00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04)00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)00:1f.0 ISA bridge: Intel Corporation QS77 Express Chipset LPC Controller (rev 04)00:1f.2 IDE interface: Intel Corporation 7 Series Chipset Family 4-port SATA Controller [IDE mode] (rev 04)00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)00:1f.5 IDE interface: Intel Corporation 7 Series Chipset Family 2-port SATA Controller [IDE mode] (rev 04)02:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07)03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 96)$ sudo lshw # ... description: Notebookproduct: 3443CTO (LENOVO_MT_3443)vendor: LENOVOversion: ThinkPad X1 Carbonserial: R9X52A4width: 64 bitscapabilities: smbios-2.7 dmi-2.7 smp vsyscall32# ... 

Lastly, I should say that my previous setup was Ubuntu 16.04 (which I ran XFCE and I think some of the Xubuntu packages on top of) on this same machine, and I don't think I ever had the same problem there.

Ubuntu 16.04 Unknown interface

$
0
0

I have an issue when configuring a second nic for my ubuntu server. Look at this:

root@ubuntubox01:~# lshw -short | grep network/0/100/15/0          ens160      network    VMXNET3 Ethernet Controller/0/100/16/0          ens192      network    VMXNET3 Ethernet Controller

When I look at the IP Addresses:

root@ubuntubox01:~# ip addr sh1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lo   valid_lft forever preferred_lft foreverinet6 ::1/128 scope host    valid_lft forever preferred_lft forever2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ffinet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160   valid_lft forever preferred_lft foreverinet6 fe80::250:56ff:feb6:5289/64 scope link    valid_lft forever preferred_lft forever3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ffinet6 fe80::250:56ff:feb6:e22d/64 scope link    valid_lft forever preferred_lft forever

But if I do:

root@ubuntubox01:~# ifup ens192Unknown interface ens192

Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?

I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.

Greetings,

C.

No Wifi Adapter Found - MSI Modern 14 A10M

$
0
0

I've looking an answer to this problem for days now and I can't seem to find it. I installed Ubuntu 18.04 LTS on my MSI Modern 14 A10M and it won't recognize my iwlwifi wifi adapter. The main problem I have is that some of the solutions I've found I can't try because this laptop has no ethernet ports, so I can't try installing packages that would fix it. I've tried installing Ubuntu 19.10 - where the WiFi adapter works just fine - but the main problem is that it has lot of trouble with temp sensors (overheating) and battery life won't go beyond an hour or two. Can anyone help me get a solution where I don't need to sudo install packages because there's no internet at all on this device

I have a bootable USB, during installation the adaptar wasn't recognized either so I don't know if there's anything that I can do with it to troubleshoot it.

Thanks in advance

Transmission daemon over OpenVPN

$
0
0

I have recently acquired a BeagleBone Black, onto which I've installed Ubuntu using this method. It has all worked so far. I want to use my BeagleBone as a torrent box, but I don't want to do it directly over my Internet connection (I don't think my ISP will like it) - so I've purchased a VPN subscription from a European server. I've manually connected my laptop to this VPN before and the run Transmission. I know that the VPN connection works in Ubuntu, and the host provides setup information for OpenVPN. Annoyingly, the dynamic nature of the assigned IP address means it would change frequently, so when I used my laptop with the VPN I would manually set the listening address in Transmission to the required value.

Ideally I'd like the following setup:

  • Transmission runs only over the VPN, and is prohibited from running torrents over the normal WAN connection
  • Only traffic directed to Transmission will be accepted or sent through the VPN, all other unsolicited traffic will be dropped
  • Transmission uses the appropriate port to listen on, based on the assigned IP address
  • OpenVPN starts automatically on boot, which then subsequently starts Transmission
  • Transmission's web GUI can be accessed over the LAN, and possibly over the Internet from my WAN connection (i.e. not back through the VPN)

Even after removing vlan entry in /etc/network interfaces file, ifconfig is showing the intreface

$
0
0

I had set up a vlan in interfaces file. Later on, even after removing the entries and restarting network, the ifconfig command is displaying that interface. Even ifdown isnt taking it down. Ifdown throws error message that the interface isnt configured.

Even after multiple times of examination, I am seeing the same thing again. Wondering why it worked in the same way in the Oracle VM Virtual Box also.Even after commenting-out in the interfaces file, networking restart, networking stop / start, ifdown && ifup, even machine reboot also..!! Same experience..!! Could somebody please try this and explain..?

connected to VPN but IP address not changing (routing problem?)

$
0
0

I would like to connect to my university VPN using openfortivpn client. The client is connecting and the tunnel is up and running.However,my IP (curl ifconfig.me) does not change once connected.I used the same configuration on another machine (same OS, different internet provider) and I could use the VPN without any problem.

My OS is Ubuntu 18.04.4 LTS.

before vpn connection:

$ route -n Destination     Gateway         Genmask         Flags Metric Ref    Use Iface0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 enp5s0169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 docker0172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 enp5s0

After vpn connection:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 enp5s0 1.1.1.1         0.0.0.0         255.255.255.255 UH    0      0        0 ppp010.0.0.0        10.146.0.194    255.0.0.0       UG    0      0        0 ppp0128.243.0.0     10.146.0.194    255.255.0.0     UG    0      0        0 ppp0128.243.50.254  192.168.1.1     255.255.255.255 UGH   0      0        0 enp5s0169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 docker0172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 enp5s0

It seems for me that the

0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 enp5s0

is wrong but I don't know what to do.

Thanks,

Charlie

Cannot get rid of errors in the elaboration

$
0
0

Please help me if u can see through the fog, that's the answer to my different attempts like:

sudo apt-get install -f 0 da rimuovere e 0 non aggiornati.9 non completamente installati o rimossi.Dopo quest'operazione, verranno occupati 0 B di spazio su disco.debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailableConfigurazione di libpam-systemd:amd64 (237-3ubuntu10.39)...debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailabledpkg: errore nell'elaborare il pacchetto libpam-systemd:amd64 (--configure): il sottoprocesso installato pacchetto libpam-systemd:amd64 script post-installation ha restituito lo stato di errore 1Configurazione di hddtemp (0.3-beta15-53)...debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailabledpkg: errore nell'elaborare il pacchetto hddtemp (--configure): il sottoprocesso installato pacchetto hddtemp script post-installation ha restituito lo stato di errore 1Configurazione di linux-base (4.5ubuntu1.1)...debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailabledpkg: errore nell'elaborare il pacchetto linux-base (--configure): il sottoprocesso installato pacchetto linux-base script post-installation ha restituito lo stato di errore 1dpkg: problemi con le dipendenze impediscono la configurazione di network-manager: network-manager dipende da libpam-systemd; tuttavia:  Il pacchetto libpam-systemd:amd64 non è ancora configurato.dpkg: errore nell'elaborare il pacchetto network-manager (--configure): problemi con le dipendenze - lasciato non configuratodpkg: problemi con le dipendenze impediscono la configurazione di gnome-settings-daemon: gnome-settings-daemon dipende da libpam-systemd; tuttavia:  Il pacchetto libpam-systemd:amd64 non è ancora configurato.dpkg: errore nell'elaborare il pacchetto gnome-settings-daemon (--configure): problemi con le dipendenze - lasciato non configuratodpkg: problemi con le dipendenze impediscono la configurazione di network-manager-config-connectivity-ubuntu: network-manager-config-connectivity-ubuntu dipende da network-manager (>= 1.10.6-2ubuntu1.4); tuttavia:  Il pacchetto network-manager non è ancora configurato.dpkg: errore nell'elaborare il pacchetto network-manager-config-connectivity-ubuntu (--configure): problemi con le dipendenze - lasciato non configuratodpkg: problemi con le dipendenze impediscono la configurazione di gala: gala dipende da gnome-settings-daemon (>= 3.15.2); tuttavia:  Il pacchetto gnome-settings-daemon non è ancora configurato.dpkg: errore nell'elaborare il pacchetto gala (--configure): problemi con le dipendenze - lasciato non configuratodpkg: problemi con le dipendenze impediscono la configurazione di switchboard-plug-pantheon-shell: switchboard-plug-pantheon-shell dipende da gala; tuttavia:  Il pacchetto gala non è ancora configurato.dpkg: errore nell'elaborare il pacchetto switchboard-plug-pantheon-shell (--configure): problemi con le dipendenze - lasciato non configuratodpkg: problemi con le dipendenze impediscono la configurazione di switchboard-plug-notifications: switchboard-plug-notifications dipende da gala; tuttavia:  Il pacchetto gala non è ancora configurato.dpkg: errore nell'elaborare il pacchetto switchboard-plug-notifications (--configure): problemi con le dipendenze - lasciato non configuratodpkg: problemi con le dipendenze impediscono l'elaborazione dei trigger per initramfs-tools: initramfs-tools dipende da linux-base; tuttavia:  Il pacchetto linux-base non è ancora configurato.dpkg: errore nell'elaborare il pacchetto initramfs-tools (--configure): problemi con le dipendenze - trigger non elaboratiSi sono verificati degli errori nell'elaborazione: libpam-systemd:amd64 hddtemp linux-base network-manager gnome-settings-daemon network-manager-config-connectivity-ubuntu gala switchboard-plug-pantheon-shell switchboard-plug-notifications initramfs-toolsE: Sub-process /usr/bin/dpkg returned an error code (1)

Wifi won't connect on Ubuntu 17.04 with Windows 8.1 dual boot

$
0
0

I partitioned my SSD and installed Ubuntu 17.04 alongside Windows 8.1. When I boot into Windows, wifi connects and works perfectly. When I boot into Ubuntu and click the network icon, it shows all the same available connections, but when I make a selection it just tries connecting for 30 seconds before saying "Disconnected - you are now offline".

I'm a noob when it comes to Linux so I'll do my best to follow along. I'm using a TP-LINK TL-WN822N wireless adapter and a RTL8192CU wireless driver. I don't know if I have a problem in my settings, driver, or something else, but I've been looking at 'duplicate Qs' and posts with similar problems for days and haven't gotten anywhere, so I'd really appreciate some help troubleshooting this. Let me know what info I need to add.

Telnet issue on remote port 80

$
0
0

I'm having issue when doing a telnet on port 80. I'm getting the following error "telnet: Unable to connect to remote host: Cannot assign requested address".

I'm trying to telnet to google.com on port 80 from any of my Ubuntu servers but when I tried it from Windows it works.

Thanks in advance for you help.

WPA Enterprise (PEAP - MSCHAPv2) on Ubuntu 18.04

$
0
0

As many of us know, wpa_supplicant has a bug that afflicts the wpa-enterprise (PEAP - MSCHAPv2) to disconnect frequently.

In my experience the wifi went down and retried to reconnect randomly making me very crazy because I couldn't go online !I didn't find out if it depend of the wifi driver (I have a ALFA AWUS 1900 with a rtl8814au chipset) or directly from the wpa_supplicant bug.

Anyway, I tried many distro like debian, fedora and so on... But in the last days I tried Ubuntu 14.04.6 on VirtualBox linked directly the usb wifi adapter, and after installed the driver and set up the network I saw the network worked very well without the frequent disconnections. So today I installed the wpa_supplicant package version from Ubuntu trusty (14.04) on my Ubuntu 18.04 and it seems it works as expected.So I need your help to confirm my suppositions and maybe bring the all community to fix that strange behavior.

Ubuntu 19.04 network bonding two wireless interface not working

$
0
0

I was a beginner and trying to bond my two nic. They are both wireless and support bonding.I was planning to create a bond0 and use it as the primary "nic" to connect to wifi

For my etc/netplan/my_plan.yaml, I have it as below:

network:  version: 2  wifis:    wlx04d9f5c452a9:      dhcp4: yes      dhcp6: yes      addresses: [192.168.1.246/24]      gateway4: 192.168.0.1      nameservers:        addresses: [8.8.8.8,4.4.4.4]      access-points:"wifi":          password: "psswrd"    wlp4s0:      dhcp4: yes      dhcp6: yes      addresses: [192.168.1.110/24]      gateway4: 192.168.0.1      nameservers:        addresses: [8.8.8.8,4.4.4.4]      access-points:"wifi":          password: "psswrd"  bonds:    bond0:      dhcp4: yes      dhcp6: yes      interfaces:        - wlp4s0        - wlx04d9f5c452a9      parameters:        mode: balance-alb

wlp4s0 and the other are both connecting via wifi

for my /etc/network/interfaces

auto loiface lo inet loopbackauto wlp4s0iface wlp4s0 inet dhcpbond-master bond0auto wlx04d9f5c452a9iface wlx04d9f5c452a9 inet dhcpbond-master bond0auto bond0iface bond0 inet dhcpbond-mode balance-albbond-miimon 100bond-slave wlx04d9f5c452a9 wlp4s0

but however, in my cat /proc/net/bonding/bond0, it shows MII status: down

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)Bonding Mode: load balancing (round-robin)MII Status: downMII Polling Interval (ms): 0Up Delay (ms): 0Down Delay (ms): 0Peer Notification Delay (ms): 0

And I use route -n and didn't see bond0 beeing used.

I want to use those two nic to create a bond and use that bond to connect to wifi as default or higher priority (which i guess is done by ifenslave), butI couldn't make the bond works.

I really need your help. Much appreciated!!

My ISP is adding a domain suffix .numericable.fr on my DNS resolution

$
0
0

With remote working due to coronavirus, I am working at home, and my local kubernetes dns resolution is failing.

when I type:

nslookup localhost

I get:

Server:     127.0.0.53Address:    127.0.0.53#53Non-authoritative answer:localhost.numericable.fr    canonical name = nc-ass-vip.sdv.fr.Name:   nc-ass-vip.sdv.frAddress: 212.95.74.75

and this is messing around with kubernetes dns resolution.

How should I remove the suffix .numericable.fr ( my ISP )

I am running on Ubuntu 19.04

GOA: Google account unreachable using wired connection

$
0
0

Besides taking a few minutes, I can successfully add a Google account through GOA using a wired network, but accessing it (through Nautilus or Geary for example) returns timeout errors.

Problem appears to be network related cause when I switch to Wifi, it works fine adding and accessing.

I am directly connected to my ISP router, not using any proxy.

What would you advice me to do?Thank you

Wireless issue on Lenovo Thinkpad L540

$
0
0

I recently installed Ubuntu 13.10 on my Lenovo Thinkpad L540. It has problem with the wifi connection. When just booted it works then suddenly it drops the connection and cannot even see the wifi networks.

  • I tried to install the windows driver for the wireless card Intel 7260 but I'm not able to extract the .inf file from the .exe that I download from Intel website. With the .inf file I should then be able to install the driver using ndiswrapper but, since I cannot get the .inf file, this way is gone.

  • I tried also following other ways. I upgraded the Kernel to the 3.13 from 3.11 but still it doesn't work.

  • I tried also to follow instructions such as those from Intel wireless 7260 driver crashes, how do I work around it? but every time I give the command sudo modprobe -r iwlwifi I get:

    FATAL: Module iwlwifi is in use.

6-April-EDIT:

  • The command sudo modprobe -rf iwlmvm before sudo modprobe -r iwlwifi, doesn't change the situationi. Still the output to the second command is

    FATAL: Module iwlwifi is in use.

  • The output to uname -r is

    3.13.1-031301-generic

  • The output to dmesg | grep iwl is a long list made of elements like the following

    [ 2028.111303] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S

    plus some few exception lines which give

    [ 2031.232825] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.


Which application send/receive data through network?

$
0
0
$ lsb_release -aNo LSB modules are available.Distributor ID: UbuntuDescription:    Ubuntu 19.10Release:    19.10Codename:   eoan

Shortly after system boot, before I start any application, I open the System Monitor and in Network History graph see something like that:

Network History from System Monitor

How do I find out which application or process is responsible for this traffic?

Intel Wireless 3165 not working in Dell Inspiron 7559 with Ubuntu 18.04 LTS

$
0
0

I am kind of new in linux environment and I must say that I am loving it even though I am in the learning curve. I have installed Ubuntu 64 bit 18.04 LTS on my Dell Inspiron 7559 using a live ISO over the network.

Everything went like a charm but I see that my Intel 3165 wireless driver is not detected and it says manual-install = true. I did some research and performed below mentioned steps.

  1. Downloaded latest Intel 3165 drivers from Intel's website in the form of tar.gz
  2. Extracted them and as per the installation guide that came with it I placed the .ucode files in /lib/firmware
  3. Rebooted the system

I have also tried the solution posted in of the posts and copied the 7265 ucode files and pasted them as 3165 ucode files in /lib/firmware.

Even after doing above mentioned I am not able to use wifi. Additional driver section in Update manager shows the device grayed out. Wifi works when first booted but after sometime it stops working and system never detects it back again unless I do a fresh installation, hence I am not using wifi now and using ethernet now.

Can anyone please help me with this and guide me on how to install the drivers? Below are the outputs of some commands:

sudo uname -aLinux abhishek-Ubuntu64bit-7559 5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

After Reboot:

rfkill list all0: hci0: Bluetooth    Soft blocked: no    Hard blocked: nolsmod | grep iwliwlwifi               348160  0cfg80211              704512  1 iwlwifisudo modprobe iwlwifi && dmesg | grep iwl--> Returns nothingsudo ubuntu-drivers devices[sudo] password for abhishek: == /sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0 ==modalias : pci:v000010DEd0000139Bsv00001028sd00000706bc03sc02i00vendor   : NVIDIA Corporationmodel    : GM107M [GeForce GTX 960M]driver   : nvidia-driver-390 - distro non-freedriver   : nvidia-driver-430 - distro non-freedriver   : nvidia-driver-435 - distro non-free recommendeddriver   : xserver-xorg-video-nouveau - distro free builtinsudo lspci | grep Network--> Returns nothingsudo dmesg | grep iwl--> Returns nothingsudo cat /etc/modprobe.d/iwlwifi.conf# /etc/modprobe.d/iwlwifi.conf# iwlwifi will dyamically load either iwldvm or iwlmvm depending on the# microcode file installed on the system.  When removing iwlwifi, first# remove the iwl?vm module and then iwlwifi.remove iwlwifi \(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \&& /sbin/modprobe -r mac80211sudo iwconfiglo        no wireless extensions.enp4s0    no wireless extensions.

Before Reboot:

sudo ubuntu-drivers devices== /sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0 ==modalias : pci:v00008086d00003165sv00008086sd00004410bc02sc80i00vendor   : Intel Corporationmodel    : Wireless 3165manual_install: Truedriver   : backport-iwlwifi-dkms - distro freesudo lspci | grep Network05:00.0 Network controller: Intel Corporation Wireless 3165 (rev 79)sudo cat /etc/modprobe.d/iwlwifi.conf# /etc/modprobe.d/iwlwifi.conf# iwlwifi will dyamically load either iwldvm or iwlmvm depending on the# microcode file installed on the system.  When removing iwlwifi, first# remove the iwl?vm module and then iwlwifi.remove iwlwifi \(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \&& /sbin/modprobe -r mac80211sudo ls -ltr /etc/modprobe.dtotal 44-rw-r--r-- 1 root root  156 Jul 30  2015 blacklist-modem.conf-rw-r--r-- 1 root root 2507 Jul 30  2015 alsa-base.conf-rw-r--r-- 1 root root  347 Jan 28  2018 iwlwifi.conf-rw-r--r-- 1 root root  583 Jan 28  2018 blacklist-rare-network.conf-rw-r--r-- 1 root root  697 Jan 28  2018 blacklist-framebuffer.conf-rw-r--r-- 1 root root  210 Jan 28  2018 blacklist-firewire.conf-rw-r--r-- 1 root root  325 Jan 28  2018 blacklist-ath_pci.conf-rw-r--r-- 1 root root 1667 Nov 12  2018 blacklist.conf-rw-r--r-- 1 root root  127 Oct 14 04:50 dkms.conf-rw-r--r-- 1 root root  154 Nov 25 13:52 amd64-microcode-blacklist.conf-rw-r--r-- 1 root root  154 Dec  2 11:23 intel-microcode-blacklist.conflrwxrwxrwx 1 root root   41 Apr  4 13:09 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.confsudo dmesg | grep iwl[    8.225602] iwlwifi 0000:05:00.0: enabling device (0000 -> 0002)[    8.267415] iwlwifi 0000:05:00.0: loaded firmware version 29.1044073957.0 op_mode iwlmvm[    8.495468] iwlwifi 0000:05:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210[    8.524665] iwlwifi 0000:05:00.0: base HW address: dc:53:60:6d:bc:44[    8.586743] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'[    8.605973] iwlwifi 0000:05:00.0 wlp5s0: renamed from wlan0sudo iwconfigenp4s0    no wireless extensions.lo        no wireless extensions.wlp5s0    IEEE 802.11  ESSID:off/any            Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm             Retry short limit:7   RTS thr:off   Fragment thr:off          Encryption key:off          Power Management:on

vlc android streaming by ubuntu

$
0
0

I have tried to play video from my PC to android app but the android app can not find the PC vlc.

When i run the vlc on my PC i have this error:

 vlcVLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)[00005577d41cb470] [cli] lua interface: Listening on host "*console".VLC media player 3.0.8 VetinariCommand Line Interface initialized. Type `help' for help.> [00005577d41d57b0] [http] lua interface: Lua HTTP interface[00005577d41d57b0] [http] main interface error: socket bind error: Address already in use[00005577d40ee570] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.[00005577d41e3a20] [telnet] lua interface: Listening on host "telnet://:1234".[00005577d40f24e0] main playlist: playlist is empty[00007fa24c7a4890] [http] lua interface: Lua HTTP interface[00007fa24c7a4890] [http] lua interface error: Error loading script /usr/lib/x86_64-linux-gnu/vlc/lua/intf/http.luac: lua/intf/http.lua:244: Failed to create HTTPd file.

And in this time i have this port open:

so@so-notebook:~$  netstat -lp |grep vlc(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)tcp        0      0 0.0.0.0:1234            0.0.0.0:*               LISTEN      2083/vlc            tcp6       0      0 [::]:http-alt           [::]:*                  LISTEN      2083/vlc            tcp6       0      0 [::]:1234               [::]:*                  LISTEN      2083/vlc       

The vlc setting is :

enter image description here

and the $HOME/.config/vlc/vlcrc file is like this.

Also at app port is settled on 8080, pass is 1234 and the IP is settled by ifconfig output result in PC.

So what do you thin i mus to do?

Thanks.

iwlwifi Wifi Microcode SW error detected (Ubuntu 18.04 x64)

$
0
0

I can connect to my home wifi network. However, internet browsing speed is just very slow.

Interesting fact is, I can connect to the same network from my Windows machine and I don't see any problems with speed. It seems this Ubuntu specific issue.

My Ubuntu laptop has Intel® Dual Band Wireless-AC 3168. I did some research online, found that this issue could be related to linux-firmware. I am using v29.1044073957.0.

But still not sure what the problem is.

I ran wireless-info tool which generated this report.

Report shows some errors:-

[  213.909410] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.[  213.909528] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:[  213.909530] iwlwifi 0000:02:00.0: Status: 0x00000100, count: 6[  213.909532] iwlwifi 0000:02:00.0: Loaded firmware version: 29.1044073957.0[  213.909534] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       [  213.909535] iwlwifi 0000:02:00.0: 0x00800634 | trm_hw_status0[  213.909537] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1[  213.909538] iwlwifi 0000:02:00.0: 0x00043D54 | branchlink2[  213.909539] iwlwifi 0000:02:00.0: 0x0004AFA6 | interruptlink1[  213.909541] iwlwifi 0000:02:00.0: 0x00024558 | interruptlink2[  213.909542] iwlwifi 0000:02:00.0: 0x00000000 | data1[  213.909544] iwlwifi 0000:02:00.0: 0x00000080 | data2[  213.909545] iwlwifi 0000:02:00.0: 0x07030000 | data3[  213.909547] iwlwifi 0000:02:00.0: 0x0E80A919 | beacon time[  213.909548] iwlwifi 0000:02:00.0: 0xF5FB26E5 | tsf low[  213.909549] iwlwifi 0000:02:00.0: 0x00000033 | tsf hi[  213.909551] iwlwifi 0000:02:00.0: 0x00000000 | time gp1[  213.909552] iwlwifi 0000:02:00.0: 0x00C099B8 | time gp2[  213.909554] iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type[  213.909555] iwlwifi 0000:02:00.0: 0x0000001D | uCode version major[  213.909557] iwlwifi 0000:02:00.0: 0x3E3B4DE5 | uCode version minor[  213.909558] iwlwifi 0000:02:00.0: 0x00000220 | hw version[  213.909559] iwlwifi 0000:02:00.0: 0x00C89200 | board version[  213.909561] iwlwifi 0000:02:00.0: 0x0ABD001C | hcmd[  213.909562] iwlwifi 0000:02:00.0: 0xA4022002 | isr0[  213.909564] iwlwifi 0000:02:00.0: 0x00000000 | isr1[  213.909565] iwlwifi 0000:02:00.0: 0x0000000A | isr2[  213.909566] iwlwifi 0000:02:00.0: 0x004028C5 | isr3[  213.909568] iwlwifi 0000:02:00.0: 0x00000000 | isr4[  213.909569] iwlwifi 0000:02:00.0: 0x0503001C | last cmd Id[  213.909571] iwlwifi 0000:02:00.0: 0x00000000 | wait_event[  213.909572] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control[  213.909573] iwlwifi 0000:02:00.0: 0x00012030 | l2p_duration[  213.909575] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid[  213.909576] iwlwifi 0000:02:00.0: 0x00000080 | l2p_addr_match[  213.909578] iwlwifi 0000:02:00.0: 0x00000007 | lmpm_pmg_sel[  213.909579] iwlwifi 0000:02:00.0: 0x03041751 | timestamp[  213.909580] iwlwifi 0000:02:00.0: 0x00342028 | flow_handler

Full Report:

I uploaded it here

Output of sudo dpkg -s linux-firmware

Package: linux-firmwareStatus: install ok installedPriority: optionalSection: miscInstalled-Size: 271097Maintainer: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>Architecture: allMulti-Arch: foreignVersion: 1.173.1Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-commonProvides: atmel-firmwareBreaks: linux-firmware-snapdragon (<= 1.2-0ubuntu1)Conflicts: atmel-firmwareDescription: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers.

Cannot ping or be pinged by any other devices on network

$
0
0

I have just completed a fresh install of Ubuntu Server on an old PC. The PC is being connected to my local network via Wi-Fi. The Wi-Fi card is a TP-Link TL-WN751ND.

The server connects to the network fine and has Internet access. The issue is that it cannot successfully ping my desktop system and the desktop system cannot ping the server. The server can ping all of the other devices on my network, which, in turn, can ping the server too.

I'm at a loss as to why the Ubuntu PC and my (Windows 10) desktop cannot communicate but everything else can. My network card in the desktop is based on an Intel Dual Band Wireless-AC 7260. The router is a BT HomeHub4 and all systems use DHCP but the router is set to assign each device a static IP. Both systems correctly receive their allocated IPs.

Desktop: 192.168.1.69Server: 192.168.1.70Gateway: 192.168.1.254Subnet: 255.255.255.0

It's probably worth mentioning that the issue persists when using the Ubuntu Desktop 15.04 install I have on the same PC but I'm not sure if this is being caused by a Windows - Linux issue (unlikely, other machines communicate with server fine as mentioned) or something wrong with one of the network cards preventing the two communicating.

Any advice appreciated,Ilmiont

On server (192.168.1.70): ip route get 192.168.1.69

192.168.1.69 dev wlan0  src 192.168.1.70    cache

tracert (Desktop)

Tracing route to HPPavilionSlim-UbuntuServer.home [192.168.1.70]over a maximum of 30 hops: 1  IlmiontDesktop.home [192.168.1.69]  reports: Destination host unreachable. Trace complete.
Viewing all 23091 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>