Upgrading the software from v3.019 to the beta v3.022 solved the issue.
The release note (https://dl.gl-inet.com/firmware/ar300m/testing/) state:
1.Optimize Repeater Auto Connection.
where "optimize" might stand for "fix bug"...
Use the same troubleshooting you would use with Debian 9; run ip -a and look for the real name of the wireless port, because wlan0 is not a likely port name for Debian going on six years now: See the answer at Why is my wlan device being renamed? for an explanation. iwconfig is also depreciated, being replaced with iw.
Run iw dev PORTNAME link for ...
Function daemonize() has been removed from new kernel version.
You have to download driver source from TP-Link site. Then unpack rtl8188EUS_linux_v18.104.22.168_25483.20171222.zip and cd to unpacked directory. Type make and you will got 8188eu.ko.
Compilation works under Debian Stretch with 4.9.0-9 kernel.
Strikethrough text is obsolete for 4.9 kernel which is ...
Here is some new log that I got on a Raspi 3B+. It still doesn't work but it's different...
May 17 14:25:37 raspberrypi kernel: [ 7843.980834] usb 1-1.4: new high-speed USB device number 7 using dwc_otg
May 17 14:25:37 raspberrypi kernel: [ 7844.128434] usb 1-1.4: New USB device found, idVendor=148f, idProduct=5370, bcdDevice= 1.01
May 17 14:25:37 ...
Honestly, I did fight many times with broadcom wireless cards, under linux and windows and those cards are crap.
card not detected correctly
network SSID randomly visible
impossible to connect on some access points for unknown reasons
connected on AP but no traffic possible
And this with all possible kernels, drivers, tools, tricks and all.
If you're trying to discover what your card supports, iw phy is a nice solution with a lot more information (including supported bands).
iwlist is showing more what's available and/or allowed in your locale, what was disabled due to DFS channels, etc., not what your device supports. From the iwlist man page:
Give the list ...
As you have connection to your router, your routes are properly configured, and you have no internet connection to outside of the LAN - then the problem should lie within the router and its internet connection/configuration, not yours. It is also not a problem with DNS, as you're pinging simple IP addresses.
What can I try to get a working internet ...
I do not know of any ready-made tool that can be used for your purpose, but you could build one yourself.
The necessary tools and programs are available on Raspbian.
Luckily, wpa-supplicant allows for interactive control of scanning for networks and manually connecting to networks.
To be specific you can either use the program wpa_cli or use the wpa_ctrl ...
As of Ubuntu 18.04 (and corresponding Debian versions) ifconfig and ifup/ifdown are deprecated, and the recommended way to bring up the interface is with the ip command:
ip link set dev <interface> up
ip link set dev <interface> down
And you can check your available interfaces with:
And you can show your interfaces' assigned ip ...
You should upgrade your netplan.io package to make this work.
The ubuntu repository on http://nl.archive.ubuntu.com/ubuntu/pool/main/n/netplan.io/ contains a version like netplan.io_0.96-0ubuntu0.18.04.4_amd64.deb, or whatever architecture you might have. The default version is too old.
I installed this on my ubuntu 18.04 LTS with:
dpkg -i netplan.io_0.96-...
I was able to resolve this. Turns out I had enabled multiple network services (netctl, NetworkManager, and wpa_supplicant) and they were conflicting.
Disabling netctl and wpa_supplicant via sudo systemctl disable netctl, sudo systemctl disable wpa_supplicant and then rebooting resolved the issue.
As an alternate answer you could sign the drivers with the MOK Key
The full write up is here
This way you can keep secure boot enabled!
Writing up the basis of it all from downloading the repo to finish would look like this:
(Note I signed more modules then I probably needed to. I'm not sure which ones govern what except rtl8822be was my driver so I ...
The problem is with the firmware of the chipset I am using. The vendor has disabled the channel bonding in the configuration. Once I enabled it I can connect it to the 40 Mhz Channel.
The Qualcomm chipset requires the gChannelBondingMode24GHz variable to be set as one in the configuration file
After a fresh install of Linux Mint my wifi was not working duo to a missing driver Realtek RTL8822BE.
To install I had to follow these steps:
sudo apt install build-essential git
git clone -b extended https://github.com/lwfinger/rtlwifi_new.git
sudo make install
sudo modprobe rtl8822be
Note that I am cloning the extended branch ...
What worked for me was removing the reference to the wifi device from any of the /etc/network/interfaces configurations.
e.g. I had a file in /etc/network/interfaces.d/something.conf that contained
iface wlx... inet dhcp
(this is probably wlan0 for many users, instead of the wlx... interface I have).
Removing (or commenting out with a #...
Not being able to connect to a 40 MHz Wifi Channel is not a problem on the Linux side per se in this case. WiFi is a complex protocol, and even more down to the definition of the protocol and particular bits of how to is implemented by different vendors.
As we can see from the output of your commands, you are using Cisco equipment and the client is in the 2....
I think I have resolved this issue by changing the kernel configuration to build the cfg80211 code as a module (CONFIG_CFG80211=m) instead of a built-in (CONFIG_CFG80211=y). This forces the code that loads the regulatory database file as firmware to run after the root file system is mounted.