Quantcast
Channel: Ubuntu Forums - Networking & Wireless
Viewing all 23300 articles
Browse latest View live

[kubuntu] wifi stopped working after update to 18.10: wlp3s0: link is not ready

$
0
0
Hi there,

I updated from Kubuntu 18.04 to 18.10 on my Thinkpad T450s yesterday. Wifi worked all day. But when I switched on my laptop again this morning, wifi had stopped working. What can I do?

I can see the connections in the network manager, but when I try them, it says "waiting for authorization" forever. Any ideas what I could try?

Here is all sorts of output from the terminal. I think the most relevant parts are at the end, where dmesg says: "IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready"

Thanks!

NFS shares don't mount at boot

$
0
0
I have a couple of nfs mounts activating in my /etc/fstab. This has been working flawlessly ... like forever. But I just discovered that it's not. Did a bunch of time-wasting sleuthing, and installed 18.10 hoping that might change things. Nope. I've done what debugging that I can, but don't see any errors.

In /etc/fstab I have

Code:

mellowood:/ftp /ftp                      nfs rsize=8192,wsize=8192,timeo=14,auto,user 0 0
But, no luck with that.

However, using "mount -a nfs" in a command line prompt after booting works perfectly. I have changed the timeo value to 3000 and just deleted the option. No change.

Code:

$ journalctl | grep nfs
Mar 14 20:01:04 mellownet kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 14 20:01:06 mellownet kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 14 20:01:11 mellownet systemd[1]: Mounting /media/nfs-usb...
Mar 14 20:01:11 mellownet kernel: FS-Cache: Netfs 'nfs' registered for caching
Mar 14 20:01:11 mellownet mount[948]: mount.nfs: Network is unreachable
Mar 14 20:01:11 mellownet systemd[1]: media-nfs\x2dusb.mount: Mount process exited, code=exited status=32
Mar 14 20:01:11 mellownet systemd[1]: Failed to mount /media/nfs-usb.
Mar 14 20:01:11 mellownet systemd[1]: media-nfs\x2dusb.mount: Unit entered failed state.
Mar 14 20:01:11 mellownet mount[947]: mount.nfs: Network is unreachable
Mar 14 20:03:18 mellownet sudo[2003]:      bob : TTY=pts/0 ; PWD=/home/bob ; USER=root ; COMMAND=/bin/mount -a nfs

Tells me that the network can't be reached ... that's silly since it's a Ethernet cable between computers. Besides, if I do:

Code:

mount -a nfs
A few seconds after booting it works just fine.

Suggestions?

new usb dongle but not working rtl8191su

$
0
0
New usb dongle but not working it is a realtek 300m RTL8191SU Any help would be appreciated. I am running Linux Mint 18.3 - 64 bit - if it helps.

Going in Circles

$
0
0
I need to install the drivers for an Alfa AWUS036ach WiFi device on
an 18.04 install of Ubuntu. The internal WiFi device of the box is a
Broadcom product and have been unable to get the Broadcom network
NIC, and WiFi to work. So I opted to install the Alfa WiFi device.

Since I have no network connectivity I downloaded the RTL8812AU
debian package from the Ubuntu repository. Shoeleather expressed
the file to the 18.04 Ubuntu box on a USB thumb drive. From their
I type:
sudo apt install ./rtl8812au-dkms_4.3.8.12175.20140902+dfsg-0ubuntu8_all.deb

The routine starts and then balks with an error message that 'dkms'
is missing.

Located dkms on the Ububntu repository, download, shoeleather
expressed it to the Ubuntu box. Then typed

sudo apt install ./dkms_2.3-3ubuntu11_all.deb

Another fail with an error message that there are dependencies
which need to be met.

I locate the dependencies, shoeleather express them to the Ubuntu
box, attempt to install only to receive more messages that other
dependencies need to be met.

Is there a way to install the Alfa drivers without network connectivity
and not keep chasing my tail trying to solve the seeming never ending
dependencies list?

TIA

Mel

[server] Ubuntu server reachable from LAN IP but not WAN IP within network

$
0
0
Hello,
I'm building an ubuntu server at home for a nodejs project.
I've configured DMZ settings of my DSL modem to route WAN IP to the server's LAN IP and it works fine.
The problem is when I try to reach server via WAN IP from any of local computers I can't reach the server but I can reach the server via it's LAN IP from browser and SSH etc.
Server is also reachable from WAN IP from outside of the local network.
I know it's a bit confusing but I'd appreciate any help.

Network adaptor no longer founs6

$
0
0
Hi again, I am a person with an Acer Aspire R5-471T laptop and an often uncooperative Qualcomm Atheros QCA6174 wireless network adapter, now running Ubuntu 18.04.

I had been using the internet normally for a few months, but as of yesterday it stopped working yesterday, and the control panel says no wireless adapter is detected. Often this is solved by rebooting once or twice, but not this time.

lspci shows nothing like "network adaptor" or "Ethernet adaptor," and `dmesg | grep - ath` is returning nothing. More worryingly, I checked to see if the wireless worked in the small Windows partition I keep for troubleshooting, and it doesn't seem to be visible there, either. It actually says there's some unidentified USB device with a problem, which I'm worried could be my wireless card.

What can I do about this?

[ubuntu] Ubuntu could not connect windows 7 but windows 10 is ok

$
0
0
Hello EV1

First, sorry for my english, i'm from VN

i have just installed ubuntu on a PC in my office, everything is ok.

In my office, i have 2 pcs with windows 7 and windows 10 with same config about network but i only can connect to windows 10 and could not connect windows 7, it's display error




Help me solve this problem

PS: all windows 10 and XP in my Office could connect to windows 7 as good

Command line to access wifi

$
0
0
Hi,

Is there any command line to check wifi status? I am not running network manager, so cannot use nmcli. I am running connman, it cannot scan the wifi due to the wifi is not switched on.

Thank you.

Kind regards,

- jh

Dell QCA6174 802.11ac Wireless - Wifi randomly disconnects

$
0
0
Hi, I have a Dell Inspiron 7472 and installed Ubuntu 18.04 on it. Since I started using, the wifi randomly disconnects and the network widget stops working. I've already changed the firmware to the new version on github and set the power management to 2. Didn't work. There is also another thing going on with this notebook. The special keys when I press them after a while not using, there is a delay. I'm not sure if it's related to the installation, I already reboot the OS and nothing changed. Here is the paste from the wireless script. Thanks!

http://paste.ubuntu.com/p/nBSxyTDNsv/

USB tethering : Can't open google related sites and some other sites as well

$
0
0
I am on Ubuntu 16.04 on Asus i7 4th gen. with dual boot for windows.
LAN from router is sometimes not detected.
Wifi doesn't list any wifi connections ever.
I am using internet from tethered phone(android). Can't open google related sites and some other sites as well, while using android tethering.
Fortunately I can open all the sites with bluetooth teathering. (Also bluetooth of laptop doesn't work, I use usb dongle).

P.S. I have reinstalled Ubuntu and the same problems persist

Any help appreciated.

[ubuntu] Persistent tap device on boot

$
0
0
Hello,

I have been trying to setup a virtual machine running Ubuntu 18.04 (on AWS) to automatically create a tap device and configure it with L3 address. The main reason behind wanting to do this is a light-weight VPN so that I can use of "ssh -w ..." to tunnel subnets between my local machine and the remote machine without needing to setup a full VPN.

I am able to set this up manually with out any issues by entering the following commands:
Code:

tunctl -u ubuntu -t tap0
ip addr add 10.1.0.2/30 dev tap0
ip link set dev tap0 up
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sysctl net.ipv4.ip_forward=1
sed -i 's/#PermitTunnel no/PermitTunnel yes/' /etc/ssh/sshd_config

However, I have been having a problem making line 2 above persistent. While I first tried netplan, it did not appear to work (I did not see any errors, but it did not apply the config on boot or "netplan --debug apply"). So I investigated using networkd. See config files below:

Config files are as follows:
Code:

ubuntu@xxx:~$ cat /etc/systemd/network/tap0.netdev 
[NetDev]
Name=tap0
Kind=tap
[Tap]
User=ubuntu


ubuntu@xxx:~$ cat /etc/systemd/network/50-tap0.network 
[Match]
Name=tap0


[Link]
MACAddress=00:11:11:11:11:11


[Network]
Address=10.0.0.2/24

On boot, I was expecting device tap0 to be created with layer 2 and 3 addresses as defined above. Alas, only layer 2 address is applied. That is,

Code:

ubuntu@ip-172-31-21-213:~$ ip addr show dev tap0
3: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:11:11:11:11:11 brd ff:ff:ff:ff:ff:ff

From reading the man pages for systemd.netdev and systemd.network I dont see anything obvious missing. Also, extracting the debug log file from networkd below I dont see any errors or warning that might be relevant, see below. Can anyone give me a suggestion on what I am not doing correctly?

Code:

-- Logs begin at Tue 2019-03-19 09:55:32 UTC, end at Tue 2019-03-19 12:19:08 UTC. --
Mar 19 12:14:57 ip-172-31-21-213 systemd[1]: Starting Network Service...
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Bus n/a: changing state UNSET → OPENING
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Added inotify watch for /run on bus n/a: 2
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Added inotify watch for /run/dbus on bus n/a: -1
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Bus n/a: changing state OPENING → WATCH_BIND
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: timestamp of '/etc/systemd/network' changed
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: timestamp of '/run/systemd/network' changed
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /etc/systemd/network/50-tap0.network, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /run/systemd/network/10-netplan-eth0.network, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /run/systemd/network/10-netplan-eth0.link, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /lib/systemd/network/80-container-ve.network, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /lib/systemd/network/80-container-host0.network, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /lib/systemd/network/80-container-vz.network, because it's not a regular file with suffix .netdev.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: loaded tap
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Created
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /etc/systemd/network/tap0.netdev, because it's not a regular file with suffix .network.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /run/systemd/network/10-netplan-eth0.link, because it's not a regular file with suffix .network.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .network.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Flags change: +MULTICAST +BROADCAST
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Link 3 added
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: udev initialized link
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: netdev has index 3
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Saved original MTU: 1500
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Flags change: +MULTICAST +BROADCAST
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Link 2 added
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: udev initialized link
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Saved original MTU: 1500
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Link 1 added
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: udev initialized link
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Saved original MTU: 0
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Adding address: ::1/128 (valid forever)
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Adding address: 127.0.0.1/8 (valid forever)
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: rtnl: received address with invalid family 129, ignoring
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Enumeration completed
Mar 19 12:14:57 ip-172-31-21-213 systemd[1]: Started Network Service.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Flags change: +UP +LOWER_UP +RUNNING
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Gained carrier
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Adding address: 172.31.21.213/20 (valid forever)
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Flags change: -UP -LOWER_UP -RUNNING
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Lost carrier
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Removing address: 172.31.21.213/20 (valid forever)
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Link state is up-to-date
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: found matching network '/etc/systemd/network/50-tap0.network'
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Link is not managed by us
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Link is not managed by us
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Bringing link up
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: IPv6 successfully enabled
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Link state is up-to-date
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: found matching network '/run/systemd/network/10-netplan-eth0.network'
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Link does not request DHCPv6 prefix delegation
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Link is not managed by us
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Bringing link up
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: IPv6 successfully enabled
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Link state is up-to-date
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Virtualization Xen found in DMI (/sys/class/dmi/id/sys_vendor)
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Virtualization XEN, found /sys/hypervisor/properties/features with value 00000705, XENFEAT_dom0 (indicating the 'hardware domain') is not set.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Found VM virtualization xen
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: lo: Unmanaged
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: MAC address: 00:11:11:11:11:11
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Flags change: +UP
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: LLDP: Started LLDP client
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: tap0: Started LLDP.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Flags change: +UP +LOWER_UP +RUNNING
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: LLDP: Started LLDP client
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Started LLDP.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Gained carrier
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Acquiring DHCPv4 lease
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): STARTED on ifindex 2
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): DISCOVER
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): OFFER
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): REQUEST (requesting)
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): ACK
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): lease expires in 59min 58s
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): T2 expires in 52min 27s
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: DHCP CLIENT (0x95a68647): T1 expires in 29min 59s
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: DHCPv4 address 172.31.21.213/20 via 172.31.16.1
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Setting MTU: 9001
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Setting transient hostname: 'ip-172-31-21-213'
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: Not connected to system bus, not setting hostname.
Mar 19 12:14:57 ip-172-31-21-213 systemd-networkd[598]: eth0: Updating address: 172.31.21.213/20 (valid for 1h)

[SOLVED] Can Mount Network Drive GUI but Not via Commanline Mount

$
0
0
I am trying to set up a raspberry pi as a file server. I have everything working except for one small thing. I can mount the network file system through the gui - clicking on the filesystem in nemo - but when I try to mount this through the commandline mount, it gives me [mount: special device //raspberrypi/multimedia/ does not exist]. I have tried mounting with

* smb://raspberrypi/multimedia
* //raspberrypi/multimedia
* //192.168.1.15/multimedia
* smb://192.168.1.15/multimedia

and it keeps giving me that error. I need this to be able to mount though mount so that I can auto mount this share through fstab or autofs. Can someone please tell me what I am doing wrong?

[ubuntu] broken wifi on Dell Precision 3520 running 16.04

$
0
0
Hello,

A routine package upgrade I did this morning broke my WiFi. It appeared that the package compat-iwlwifi-core19-intel8265 failed to install properly. The WiFi stopped working after the update. Trying to fix it following various threads I found online probably made things worse.

I found these threads, but they haven't helped much:
https://ubuntuforums.org/showthread.php?t=1314693
https://ubuntuforums.org/showthread.php?t=2370912

Here's where things stand at the moment:

Network Manager no longer gives the "Enable Wireless Networking" option.

The device is there, but there's no driver for it.
Code:

$ sudo lshw -C network
  *-network UNCLAIMED   
      description: Network controller
      product: Wireless 8265 / 8275
      vendor: Intel Corporation
      physical id: 0
      bus info: pci@0000:02:00.0
      version: 78
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress cap_list
      configuration: latency=0
      resources: memory:ef200000-ef201fff
  *-network
      description: Ethernet interface
      product: Ethernet Connection (5) I219-LM
      vendor: Intel Corporation
      physical id: 1f.6
      bus info: pci@0000:00:1f.6
      logical name: enp0s31f6
      version: 31
      serial: d4:81:d7:be:51:2d
      size: 1Gbit/s
      capacity: 1Gbit/s
      width: 32 bits
      clock: 33MHz
      capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
      configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.1-4 ip=192.168.1.147 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
      resources: irq:129 memory:ef300000-ef31ffff

The firmware is there:
Code:

$ ls /lib/firmware/ | grep 8265
iwlwifi-8265-21.ucode
iwlwifi-8265-21.ucode.wifi-intel8265
iwlwifi-8265-22.ucode
iwlwifi-8265-27.ucode
iwlwifi-8265-31.ucode
iwlwifi-8265-34.ucode
iwlwifi-8265-36.ucode

I have even downloaded the firmware from
https://git.kernel.org/cgit/linux/ke...-8265-31.ucode
and used it instead of the original firmware, but that didn't help either. I also downloaded v22 of the firmware from
https://wireless.wiki.kernel.org/en/...language=en_US
but that didn't help.

I have tried to load the kernel module with
Code:

sudo modprobe iwlwifi
but to no avail. The kernel provides firmware loader support
Code:

$ grep CONFIG_FW_LOADER=y /boot/config-4.4.0-143-generic
CONFIG_FW_LOADER=y

so these should have worked. I tried loading the wl module instead of iwlwifi, but no luck.

I'm not sure what to do next. I've probably screwed something up. Please advise.

Thanks!

Need help with wifi on Lenovo H50-00, Ubuntu 16.04

$
0
0
Hi everyone!

I am a newbie and trying to understand what I need to get wifi to work on a desktop computer in Ubuntu. I have a wifi adapter that I failed to get working, but I now also read that you can do it with a driver without an adapter, but maybe I understood it wrong. And I couldn't find the driver.

Hope that somebody can help me with this :confused:.

[ubuntu] XPS 13 (9380) wifi dropping and crashing network-manager

$
0
0
I have dual booted my XPS13 with ubuntu 18.04.2 and since day 1 of using ubuntu I've had problems with the wifi randomly dropping, crashing the netwrok-manager and sometimes freezing the system (sudo hangs and system becomes unresponsive). I have tried updating the kernel and the ath10k firmware, as suggested in other posts, but I kept encountering the same problems. The wifi works perfectly on the windows partition.

This is the wireless info of my current drivers. I'm running kernel 5.0.3 as it is the one that has kept the wifi working for the longest so far.
Code:

########## wireless info START ##########

Report from: 20 Mar 2019 15:55 GMT +0000

Booted last: 20 Mar 2019 00:00 GMT +0000

Script from: 22 Oct 2018 03:34 UTC +0000

##### release ###########################

Distributor ID:    Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:    18.04
Codename:    bionic

##### kernel ############################

Linux 5.0.3-050003-generic #201903191333 SMP Tue Mar 19 13:35:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Parameters: ro, quiet, splash, vt.handoff=1

##### desktop ###########################

Ubuntu

##### lspci #############################

02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
    Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a]
    Kernel driver in use: ath10k_pci

##### lsusb #############################

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 002: ID 0c45:6723 Microdia
Bus 001 Device 004: ID 27c6:5385 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

##### PCMCIA card info ##################

##### rfkill ############################

0: hci0: Bluetooth
    Soft blocked: yes
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

##### secure boot #######################

SecureBoot disabled

##### lsmod #############################

dell_laptop            20480  0
ledtrig_audio          16384  3 snd_hda_codec_generic,snd_hda_codec_realtek,dell_laptop
ath10k_pci            40960  0
ath10k_core          434176  1 ath10k_pci
dell_wmi              20480  0
dell_smbios            28672  2 dell_wmi,dell_laptop
ath                    36864  1 ath10k_core
mac80211              806912  1 ath10k_core
dell_wmi_descriptor    20480  2 dell_wmi,dell_smbios
intel_wmi_thunderbolt    20480  0
wmi_bmof              16384  0
cfg80211              671744  3 ath,mac80211,ath10k_core
sparse_keymap          16384  2 intel_hid,dell_wmi
wmi                    28672  5 intel_wmi_thunderbolt,dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor
video                  45056  3 dell_wmi,dell_laptop,i915

##### interfaces ########################

[/etc/network/interfaces]
auto lo
iface lo inet loopback

##### ifconfig ##########################

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback <MAC address> brd <MAC address>
    inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether <MAC 'wlp2s0' [IF1]> brd <MAC address>
    inet 192.168.1.9/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp2s0
      valid_lft 86261sec preferred_lft 86261sec
    inet6 fd00:5a13:7f16:b700:e43b:a1ad:98ea:3518/64 scope global temporary dynamic
      valid_lft 7062sec preferred_lft 3462sec
    inet6 fd00:5a13:7f16:b700:fb7:3ccf:77ad:f466/64 scope global dynamic mngtmpaddr noprefixroute
      valid_lft 7062sec preferred_lft 3462sec
    inet6 fe80::4655:2a1f:cf8:651b/64 scope link noprefixroute
      valid_lft forever preferred_lft forever

##### iwconfig ##########################

lo        no wireless extensions.

wlp2s0    IEEE 802.11  ESSID:"TALKTALK7F16B7" 
          Mode:Managed  Frequency:5.22 GHz  Access Point: <MAC 'TALKTALK7F16B7' [AC1]> 
          Bit Rate=6 Mb/s  Tx-Power=30 dBm 
          Retry short limit:7  RTS thr:off  Fragment thr:off
          Power Management:off
          Link Quality=69/70  Signal level=-41 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:3  Missed beacon:0

##### route #############################

default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.9 metric 600

##### resolv.conf #######################

[777 root '/etc/resolv.conf' -> '../run/systemd/resolve/stub-resolv.conf']

nameserver 127.0.0.53
options edns0
search lan

##### network managers ##################

Installed:

    NetworkManager

Running:

root      873    1  0 15:53 ?        00:00:00 /usr/sbin/NetworkManager --no-daemon

##### NetworkManager info ###############

GENERAL.DEVICE:                        wlp2s0
GENERAL.TYPE:                          wifi
GENERAL.NM-TYPE:                        NMDeviceWifi
GENERAL.VENDOR:                        Qualcomm Atheros
GENERAL.PRODUCT:                        QCA6174 802.11ac Wireless Network Adapter
GENERAL.DRIVER:                        ath10k_pci
GENERAL.DRIVER-VERSION:                5.0.3-050003-generic
GENERAL.FIRMWARE-VERSION:              RM.4.4.1.c2-00057-QCARMSWP-1
GENERAL.HWADDR:                        <MAC 'wlp2s0' [IF1]>
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.REASON:                        0 (No reason given)
GENERAL.UDI:                            /sys/devices/pci0000:00/0000:00:1c.6/0000:02:00.0/net/wlp2s0
GENERAL.IP-IFACE:                      wlp2s0
GENERAL.IS-SOFTWARE:                    no
GENERAL.NM-MANAGED:                    yes
GENERAL.AUTOCONNECT:                    yes
GENERAL.FIRMWARE-MISSING:              no
GENERAL.NM-PLUGIN-MISSING:              no
GENERAL.PHYS-PORT-ID:                  --
GENERAL.CONNECTION:                    TALKTALK7F16B7
GENERAL.CON-UUID:                      acbdaed4-6834-4aa3-ba78-833e104d64fe
GENERAL.CON-PATH:                      /org/freedesktop/NetworkManager/ActiveConnection/1
GENERAL.METERED:                        no (guessed)
CAPABILITIES.CARRIER-DETECT:            no
CAPABILITIES.SPEED:                    6 Mb/s
CAPABILITIES.IS-SOFTWARE:              no
CAPABILITIES.SRIOV:                    no
WIFI-PROPERTIES.WEP:                    yes
WIFI-PROPERTIES.WPA:                    yes
WIFI-PROPERTIES.WPA2:                  yes
WIFI-PROPERTIES.TKIP:                  yes
WIFI-PROPERTIES.CCMP:                  yes
WIFI-PROPERTIES.AP:                    yes
WIFI-PROPERTIES.ADHOC:                  yes
WIFI-PROPERTIES.2GHZ:                  yes
WIFI-PROPERTIES.5GHZ:                  yes
IP4.ADDRESS[1]:                        192.168.1.9/24
IP4.GATEWAY:                            192.168.1.1
IP4.ROUTE[1]:                          dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 600
IP4.ROUTE[2]:                          dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 600
IP4.ROUTE[3]:                          dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]:                            192.168.1.1
IP4.DOMAIN[1]:                          lan
DHCP4.OPTION[1]:                        requested_host_name = 1
DHCP4.OPTION[2]:                        requested_domain_search = 1
DHCP4.OPTION[3]:                        requested_broadcast_address = 1
DHCP4.OPTION[4]:                        requested_time_offset = 1
DHCP4.OPTION[5]:                        requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[6]:                        requested_ms_classless_static_routes = 1
DHCP4.OPTION[7]:                        requested_domain_name = 1
DHCP4.OPTION[8]:                        domain_name = lan
DHCP4.OPTION[9]:                        requested_wpad = 1
DHCP4.OPTION[10]:                      next_server = 0.0.0.0
DHCP4.OPTION[11]:                      expiry = 1553183598
DHCP4.OPTION[12]:                      dhcp_message_type = 5
DHCP4.OPTION[13]:                      dhcp_rebinding_time = 75600
DHCP4.OPTION[14]:                      routers = 192.168.1.1
DHCP4.OPTION[15]:                      ip_address = 192.168.1.9
DHCP4.OPTION[16]:                      requested_subnet_mask = 1
DHCP4.OPTION[17]:                      subnet_mask = 255.255.255.0
DHCP4.OPTION[18]:                      requested_static_routes = 1
DHCP4.OPTION[19]:                      dhcp_renewal_time = 43200
DHCP4.OPTION[20]:                      dhcp_lease_time = 86400
DHCP4.OPTION[21]:                      requested_netbios_scope = 1
DHCP4.OPTION[22]:                      domain_name_servers = 192.168.1.1 192.168.1.1
DHCP4.OPTION[23]:                      requested_netbios_name_servers = 1
DHCP4.OPTION[24]:                      broadcast_address = 192.168.1.255
DHCP4.OPTION[25]:                      requested_routers = 1
DHCP4.OPTION[26]:                      requested_ntp_servers = 1
DHCP4.OPTION[27]:                      requested_interface_mtu = 1
DHCP4.OPTION[28]:                      network_number = 192.168.1.0
DHCP4.OPTION[29]:                      dhcp_server_identifier = 192.168.1.1
DHCP4.OPTION[30]:                      requested_domain_name_servers = 1
IP6.ADDRESS[1]:                        fd00:5a13:7f16:b700:e43b:a1ad:98ea:3518/64
IP6.ADDRESS[2]:                        fd00:5a13:7f16:b700:fb7:3ccf:77ad:f466/64
IP6.ADDRESS[3]:                        fe80::4655:2a1f:cf8:651b/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                          dst = fd00:5a13:7f16:b700::/64, nh = ::, mt = 600
IP6.ROUTE[2]:                          dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[3]:                          dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[4]:                          dst = fe80::/64, nh = ::, mt = 600
IP6.DNS[1]:                            fe80::1
DHCP6.OPTION[1]:                        dhcp6_name_servers = fe80::1
DHCP6.OPTION[2]:                        requested_dhcp6_domain_search = 1
DHCP6.OPTION[3]:                        dhcp6_server_id = 0:1:0:1:12:cf:f7:a6:0:5a:13:7f:16:b7
DHCP6.OPTION[4]:                        requested_dhcp6_client_id = 1
DHCP6.OPTION[5]:                        requested_dhcp6_name_servers = 1
DHCP6.OPTION[6]:                        dhcp6_client_id = 0:4:b3:3f:95:4c:16:4e:c7:45:39:b2:eb:74:11:7b:3:66
CONNECTIONS.AVAILABLE-CONNECTION-PATHS: /org/freedesktop/NetworkManager/Settings/{1}
CONNECTIONS.AVAILABLE-CONNECTIONS[1]:  acbdaed4-6834-4aa3-ba78-833e104d64fe | TALKTALK7F16B7

SSID            BSSID              MODE  CHAN  FREQ      RATE        SIGNAL  BARS  SECURITY  ACTIVE  IN-USE
TALKTALK7F16B7  <MAC 'TALKTALK7F16B7' [AC2]>  Infra  1    2412 MHz  270 Mbit/s  82      ▂▄▆█  WPA1 WPA2  no           
TALKTALK7F16B7  <MAC 'TALKTALK7F16B7' [AC1]>  Infra  44    5220 MHz  270 Mbit/s  80      ▂▄▆_  WPA1 WPA2  yes    *     
PLUSNET-2NG5    <MAC 'PLUSNET-2NG5' [AC4]>  Infra  6    2437 MHz  130 Mbit/s  64      ▂▄▆_  WPA2      no           
--              <MAC '

I know Dell sells a Developer edition of this laptop (same hardware) that comes with Ubuntu preinstalled, so there must be a stable configuration for the wifi. If anyone knows what the kernel and drivers the 2019 XPS13 developer edition ships with, or how to fix the unstable wifi issue, it would be very helpful. Thank you.


To add a quick unrelated issue, I have partitioned the ssd and installed ubuntu without disabling bitlocker encryption, and on some boots into windows I am asked for my bitlocker key. Is it safe to unencrypt the ssd now, or is there a way to avoid having to type the key in?

vsftpd connection

$
0
0
Dear sir ,
In my office i have configured the ftp server (vsftpd)
but when i try to connect it says connection refused,
and we have fortigate firewall in our office
so should i open the port or mapp to my public ip address ?

[lubuntu] trying to make edimax dongle work

$
0
0
i purchased an edimax ew-7611ulb dongle, which is wifi and bluetooth in one.

i downloaded their driver package from here:
https://www.edimax.com/edimax/downlo...50/ew-7611ulb/

i tried the make config without success.
even under sudo su, it appears to do something, but gives loads of errors..

Code:

$sudo make install -s
Copy RTL8723BU fw/config to /lib/firmware
rmmod: ERROR: Module btusb is not currently loaded
mv: cannot stat '/lib/modules/4.18.0-16-generic/kernel/drivers/bluetooth/btusb.ko': No such file or directory
rmmod: ERROR: Module rtk_btusb is not currently loaded
Makefile:970: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
/home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9/bluetooth_usb_driver/rtk_coex.c: In function ‘rtk_check_setup_timer’:
/home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9/bluetooth_usb_driver/rtk_coex.c:544:3: error: implicit declaration of function ‘setup_timer’; did you mean ‘sk_stop_timer’? [-Werror=implicit-function-declaration]
  setup_timer(&(btrtl_coex.a2dp_count_timer),
  ^~~~~~~~~~~
  sk_stop_timer
/home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9/bluetooth_usb_driver/rtk_coex.c: In function ‘rtk_btcoex_open’:
/home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9/bluetooth_usb_driver/rtk_coex.c:2544:2: error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’? [-Werror=implicit-function-declaration]
  init_timer(&btrtl_coex.polling_timer);
  ^~~~~~~~~~
  init_timers
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:327: /home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9/bluetooth_usb_driver/rtk_coex.o] Error 1
make[2]: *** [Makefile:1534: _module_/home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9/bluetooth_usb_driver] Error 2
make[1]: *** [Makefile:10: all] Error 2
make: *** [Makefile:12: install] Error 2
root@hb-pc:/home/hb/Downloads/EW-7611ULB_Linux_Bluetooth_Driver_1.0.0.9# h

[ubuntu] Atheros Communications AR81Family Gigabit/Fast Ethernet Driver

$
0
0
what should be done when installed ubuntu 18.04 and done the updates even so it does not recognize network card?
Thanks for listening.

Atheros Communications AR81Family Gigabit/Fast Ethernet Driver
Atheros Wireless LAN Driver.

[lubuntu] BGH Positivo AT 300 Wireless & Bluetooth Problem

$
0
0
Hi,

I install Lubuntu 18.04 and I have problems with the PCI, it's not recognized.

Here is the info of the script in the post with the information

I try to reinstall Lubuntu, but the problem persist.

Tnks.

[ubuntu] Setting up Squid. What to configure ports?

$
0
0
Hello.
I want to make Wifi-hotspot with authorization by SMS. I found an article on the Internet in which I try to work, but which I do not understand in subtle details.
Available: old computer under the server; workstation with which I write; TP-Link TL-WR720N router. I thought another modem to take to receive SMS, which MTS sells.


I installed an old computer in my home network and installed Ubuntu Server 16.04.6 LTS 32-bit on it. By default, I also installed SSH, for access from my other computer.
I changed file /etc/network/interfaces:
Code:

employee@wifi-server:/etc/squid$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*
It changed only the addresses from 10.x.x.x to the addresses of my subnet 192.168.0.x. It is very possible that I made a mistake already at this step, since I do not understand which addresses here should be assigned.
Then I check ports sudo ss -lnptu | grep: 3128
# The loopback network interface
#auto lo
#iface lo inet loopback

# The primary network interface
#auto enp5s2
#iface enp5s2 inet dhcp


auto enp5s2
iface enp5s2 inet static
        address 192.168.0.10
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.1
        dns-nameservers 8.8.8.8

I installed the program as in the article:
Code:

apt-get install git fakeroot build-essential devscripts
apt-cache policy squid3
apt-get build-dep squid3
apt-get build-dep libecap2
apt-get install libssl-dev libgnutls28-dev

Next, I installed Squid from the repository version 3.6.12, because I did not want to suffer with the build of the source (I do not really understand this).
I did not correct the error as in the article (messages in the logs: SECURITY ALERT: Host header detected on local = ...: 443 remote = ...: *).

Output systemctl status -l squid:
Code:

employee@wifi-server:/etc/squid$ systemctl status -l squid
● squid.service - LSB: Squid HTTP Proxy version 3.x
  Loaded: loaded (/etc/init.d/squid; bad; vendor preset: enabled)
  Active: active (running) since Чт 2019-03-21 20:24:11 +05; 1h 22min ago
    Docs: man:systemd-sysv-generator(8)
  CGroup: /system.slice/squid.service
          ├─2938 /usr/sbin/squid -YC -f /etc/squid/squid.conf
          ├─2944 (squid-1) -YC -f /etc/squid/squid.conf
          └─2945 (logfile-daemon) /var/log/squid/access.log

мар 21 20:24:10 wifi-server systemd[1]: Starting LSB: Squid HTTP Proxy version 3.x...
мар 21 20:24:10 wifi-server squid[2895]:  * Starting Squid HTTP Proxy squid
мар 21 20:24:11 wifi-server squid[2895]:    ...done.
мар 21 20:24:11 wifi-server systemd[1]: Started LSB: Squid HTTP Proxy version 3.x.
мар 21 20:24:11 wifi-server squid[2938]: Squid Parent: will start 1 kids
мар 21 20:24:11 wifi-server squid[2938]: Squid Parent: (squid-1) process 2944 started
мар 21 20:24:34 wifi-server systemd[1]: Started LSB: Squid HTTP Proxy version 3.x.
мар 21 20:43:11 wifi-server systemd[1]: Started LSB: Squid HTTP Proxy version 3.x.
мар 21 21:21:33 wifi-server systemd[1]: Started LSB: Squid HTTP Proxy version 3.x.

Created the configuration file /etc/squid/squid.conf:
Code:

employee@wifi-server:/etc/squid$ cat squid.conf
acl localnet src 192.168.0.0/24
acl SSL_ports port 443
acl Safe_ports port 80          # http
acl Safe_ports port 21          # ftp
acl Safe_ports port 443        # https
acl Safe_ports port 70          # gopher
acl Safe_ports port 210        # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280        # http-mgmt
acl Safe_ports port 488        # gss-http
acl Safe_ports port 591        # filemaker
acl Safe_ports port 777        # multiling http
acl CONNECT method CONNECT

dns_nameservers 10.66.66.1
http_access deny !Safe_ports

http_access deny CONNECT !SSL_ports

http_access allow localhost manager
http_access deny manager

http_access allow localnet
http_access allow localhost
http_access deny all

#http_port 3128
#прозрачный порт указывается опцией intercept
http_port 192.168.0.10:3128 intercept options=NO_SSLv3:NO_SSLv2

#также нужно указать непрозрачный порт, ибо если захотите вручную указать адрес
#прокси в браузере, указав прозрачный порт, вы получите ошибку доступа, поэтому нужно
#указывать непрозрачный порт в браузере, если конечно такое желание будет, к тому же в логах #сыпятся ошибки о том, что непрохрачный порт не указан=)
http_port 192.168.0.10:3130 options=NO_SSLv3:NO_SSLv2

#и наконец, указываем HTTPS порт с нужными опциями
https_port 192.168.0.10:3129 intercept ssl-bump options=ALL:NO_SSLv3:NO_SSLv2 connection-auth=off cert=/etc/squid/squidCA.pem

always_direct allow all
sslproxy_cert_error allow all
sslproxy_flags DONT_VERIFY_PEER

#укажем правило со списком блокируемых ресурсов (в файле домены вида .domain.com)
acl blocked ssl::server_name  "/etc/squid/blocked_https.txt"
acl step1 at_step SslBump1
ssl_bump peek step1

#терминируем соединение, если клиент заходит на запрещенный ресурс
ssl_bump terminate blocked
ssl_bump splice all

sslcrtd_program /usr/lib/squid/ssl_crtd -s /var/lib/ssl_db -M 4MB

coredump_dir /var/spool/squid
refresh_pattern ^ftp:          1440    20%    10080
refresh_pattern ^gopher:        1440    0%      1440
refresh_pattern -i (/cgi-bin/|\?) 0    0%      0
refresh_pattern .              0      20%    4320
cache_dir aufs /var/spool/squid 2048 49 256
maximum_object_size 61440 KB
minimum_object_size 3 KB

cache_swap_low 90
cache_swap_high 95
maximum_object_size_in_memory 512 KB
memory_replacement_policy lru

#logfile_rotate 31
logfile_daemon /usr/lib/squid/log_db_daemon
access_log daemon:/127.0.0.1:3306/base/table/user/password squid

It changed only the addresses from 10.x.x.x to the addresses of my subnet 192.168.0.x. It is very possible that I made a mistake already at this step, since I do not understand which addresses here should be assigned.
Then I check ports sudo ss -lnptu | grep: 3128
The terminal does not output anything to the following commands:
Code:

sudo ss -lnptu | grep :3129
sudo ss -lnptu | grep :3130

Do I understand correctly that these ports are not open? Should they be open?

Dear forum users, I ask your criticism of my mistakes and explanations of how to fix it, since I do not understand everything in this operating system.
Is this equipment enough? Have I assigned the correct ports? Why are some ports closed? Was it necessary to correct the error SECURITY ALERT?


Or, please forward me to another place to ask this question.
Thank.
Viewing all 23300 articles
Browse latest View live


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