Leap 42.3, Fresh install cannot connect to Public WiFi that is in a Captive Portal

English Network/Internet
#1

I have a new laptop that dual-boots Leap 42.3 and Windows 10. The install is fully up-to-date and completely vanilla with the following exceptions:
o Linux is installed on encrypted, LVM
o Root, SWAP and Home are all enlarged from the base specification
o Desktop customized by the Desktop Manager for ease of operation

I can connect with both Leap 42.3 and Windows 10 at using both wired (ETH0) and wireless (WLAN0). The router at home is protected using WPA-PSK and functions as required.
I can connect at home using an old laptop (openSuSE 13.2, Network Manager, No Windows on this machine).
The Public WiFi installations to which I have access all require the acknowledgement of Terms and Conditions and/or an email address sign-in before first access.
I can connect to Public WiFi using either the old laptop on 13.2 or the new laptop on Windows 10.

I CANNOT connect to Public WiFi using the new laptop on Leap 42.3. The example session attempt I have documented will not even stay activated long enough to bring up a browser to ask for internet access or to run CLI commands to check the connection.
Before I flood the forum with data, what would be most helpful to this discussion? I have currently available:
o complete journal of the most current failed session extracted via CLI journalctl (181kb)
o ip addr (at home)
o /etc/NetworkManager.conf
o /etc/sysconfig/network/config
o the contents of /etc/NetworkManager/system connections
o the contents of /etc/NetworkManager/dispatcher.d
If you need something else, I can get that.

#2

What exactly is “session” here? Do you mean your system gets deauthentcated from AP?

#3

Watch the NetoworkManager logging while you attempt to connect to the Public WiFi service. Open a terminal and do

sudo journalctl -fu NetworkManager

then try connecting. That will show if you are getting deauthenticated, or even connected at all.

#4

From the captured journal the first failure message is during NetworkManager startup -


Nov 16 09:39:50 linux-poqz.suse NetworkManager[1582]: <info>  connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving 'conncheck.opensuse.org': Name or service not known'

I am not surprised by this because of the Captive Portal. The bootup processing continues.

Further down I get connected -


Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  keyfile: add connection /etc/NetworkManager/system-connections/@Ground Control Free WiFi (e5437e09-df9b-4b8d-9daa-5073d79805c3,"@Ground Control Free WiFi")
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): Activation: starting connection '@Ground Control Free WiFi' (e5437e09-df9b-4b8d-9daa-5073d79805c3)
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  NetworkManager state is now CONNECTING
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): Activation: (wifi) connection '@Ground Control Free WiFi' requires no security.  No secrets needed.
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  Config: added 'ssid' value '@Ground Control Free WiFi'
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  Config: added 'scan_ssid' value '1'
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  Config: added 'key_mgmt' value 'NONE'
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  Config: set interface ap_scan to 1
Nov 16 09:42:51 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): supplicant interface state: inactive -> scanning
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: kwalletd5 started
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: openAsync for  ":1.4"
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: Setting useNewHash to true
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: Wallet new enough, using new hash
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: Migration agent starting...
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: old wallets were already migrated
Nov 16 09:42:52 linux-poqz.suse org.kde.kwalletd5[2791]: Migration agent stop.
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <warn>  (wlan0): Activation: (wifi) association took too long, failing activation
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <info>  NetworkManager state is now DISCONNECTED
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <warn>  (wlan0): Activation: failed for connection '@Ground Control Free WiFi'
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <info>  (wlan0): supplicant interface state: scanning -> disconnected
Nov 16 09:43:16 linux-poqz.suse NetworkManager[1582]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.

I don’t know how long “(wifi) association” is supposed to take but 42:51 til 43:16 (25 seconds) was considered too long.
At this point I shut the system down and the rest of the journal reflects the shut-down.

It is late evening here. I plan to try a different location in the morning and attempt access there. I will record the same series of events and attempt any additional items requested.

#5

Additional information from @Ground Control Free WiFi -


[connection]
id=@Ground Control Free WiFi
uuid=e5437e09-df9b-4b8d-9daa-5073d79805c3
type=wifi
permissions=user:freda:;
secondaries=

[wifi]
mac-address=3C:95:09:96:98:1D
mac-address-blacklist=
mode=infrastructure
seen-bssids=
ssid=@Ground Control Free WiFi

[ipv4]
dns-search=
method=auto

[ipv6]
dns-search=
method=auto

A ssid= statement is clearly shown.

#6

If you do a scan with the iw command, what is returned?

iw dev wlan0 scan
  • The output may be lengthy depending on the number of APs around. You could upload to https://paste.opensuse.org/ and share the link that it provides here.

Wireless hardware details please…

/usr/sbin/hwinfo --wlan
#7

I’m pretty sure what you’re describing is an AP that requires a web browser re-direction for you to either acknowledge TOS or enter credentials.

I’ve personally also seen problems on certain AP systems, and it doesn’t seem to be limited to Linux, I also see the same problem on my Android phone at times. The fault is the AP, not on the client side more-or-less… The AP manufacturer just doesn’t test their system on anythin but Windows and <sometimes> a mobile device or two.

My Workaround…

Determine the IP address of the redirected web page… It might be, but is not always the same as the Default Gateway.
Open a web browser (no particular address) <before> you attempt to connect.
Enter the IP address of the re-direct page, but don’t hit <Enter> which would activate going to that page.
Connect to your wireless.
Within about a few seconds, <now> hit <Enter> in your web browser. If you have the correct IP address, you should be able to open the web page and enter confirmation.

So,
The trick is to overcome the malfunctioning re-direct, so how to find that address? Note that name resolution <may> not work, so at least nowadays I enter the IP address… In any case, I doubt that the confirmation web page is running on a big webserver with multiple websites… Most of these public APs are small machines with limited resources.

  1. Use a Windows machine (I see you dual boot with Windows). Commands like netstat are the same as on Linux to display all your network connections, you can use “route” to display your routing table. Maybe a web browser or network log could be easier but I haven’t used those.
  2. When you boot with your openSUSE, before you’re disconnected you can run “ip route” to display your routing table and “ip addr” for other info that may or may not be useful.

And,
If you’re successful, don’t forget to bookmark the confirmation page so you don’t have to re-discover it the next time you connect…

HTH,
TSU

#8

Yes, 25 seconds is exactly the value of default timeout for external authentication; in this case it is timeout waiting for supplicant.

How exactly you are supposed to acknowledge “Terms and Conditions”? You say “captive portal”, but captive portal is normally displayed after client got associated to AP; it needs existing connection so it can access captive portal in the first place. In your log there is no association - is your AP (mis-)using external authentication to request confirmation?

You can try to workaround it by setting 802-1x.auth-timeout connection property to higher value. But I’d say 25 seconds should be pretty much enough to display any pertinent information, I do not think it is going to help. You really need to explain what AP expects from you.

#9

Requested information -
For iw dev wlan0 scan (it is short)


sudo /usr/sbin/iw dev wlan0 scan
BSS 00:25:84:0f:14:a0(on wlan0)
    TSF: 30417883763041 usec (352d, 01:24:43)
    freq: 2452
    beacon interval: 100 TUs
    capability: ESS ShortPreamble ShortSlotTime (0x0421)
    signal: -74.00 dBm
    last seen: 292 ms ago
    Information elements from Probe Response frame:
    SSID: wildflower-g
    Supported rates: 1.0* 2.0* 5.5* 6.0 9.0 11.0* 12.0 18.0 
    DS Parameter set: channel 9
    ERP: <no flags>
    Extended supported rates: 24.0 36.0 48.0 54.0 
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 31-1023, AIFSN 3
         * BK: CW 31-1023, AIFSN 7
         * VI: CW 15-31, AIFSN 2, TXOP 6016 usec
         * VO: CW 7-15, AIFSN 2, TXOP 3264 usec

For hwinfo


sudo /usr/sbin/hwinfo --wlan
26: PCI 300.0: 0282 WLAN controller
  [Created at pci.378]
  Unique ID: y9sn.ir4uVzTW3gD
  Parent ID: Rtk9.fX2jjCxTjj4
  SysFS ID: /devices/pci0000:00/0000:00:02.4/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Device Name: "WLAN Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2"
  Model: "Realtek RTL8723BE PCIe Wireless Network Adapter"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0xb723 "RTL8723BE PCIe Wireless Network Adapter"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x81c1 
  Driver: "rtl8723be"
  Driver Modules: "rtl8723be"
  Device File: wlan0
  Features: WLAN
  I/O Ports: 0xd000-0xd0ff (rw)
  Memory Range: 0xfe800000-0xfe803fff (rw,non-prefetchable)
  IRQ: 41 (no events)
  HW Address: 3c:95:09:96:98:1d
  Permanent HW Address: 3c:95:09:96:98:1d
  Link detected: no
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v000010ECd0000B723sv0000103Csd000081C1bc02sc80i00"
  Driver Info #0:
    Driver Status: rtl8723be is active
    Driver Activation Cmd: "modprobe rtl8723be"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #8 (PCI bridge)

At this location I stay connected and it shows in the journal.


Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  keyfile: add connection /etc/NetworkManager/system-connections/wildflower-g (2fe48f90-fccc-4cee-9e0a-9d1f1ad56aa7,"wildflower-g")
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): Activation: starting connection 'wildflower-g' (2fe48f90-fccc-4cee-9e0a-9d1f1ad56aa7)
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  NetworkManager state is now CONNECTING
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): Activation: (wifi) connection 'wildflower-g' requires no security.  No secrets needed.
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  Config: added 'ssid' value 'wildflower-g'
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  Config: added 'scan_ssid' value '1'
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  Config: added 'key_mgmt' value 'NONE'
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  Config: set interface ap_scan to 1
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: kwalletd5 started
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: openAsync for  ":1.4"
Nov 17 09:58:49 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): supplicant interface state: inactive -> scanning
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: Setting useNewHash to true
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: Wallet new enough, using new hash
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: Migration agent starting...
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: old wallets were already migrated
Nov 17 09:58:49 linux-poqz.suse org.kde.kwalletd5[2838]: Migration agent stop.
Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: authenticate with 00:25:84:0f:14:a0
Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: send auth to 00:25:84:0f:14:a0 (try 1/3)
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): supplicant interface state: scanning -> authenticating
Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: authenticated
Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: associate with 00:25:84:0f:14:a0 (try 1/3)
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): supplicant interface state: authenticating -> associating
Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: RX AssocResp from 00:25:84:0f:14:a0 (capab=0x421 status=0 aid=10)
Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: associated
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): supplicant interface state: associating -> completed
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'wildflower-g'.
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <info>  dhclient started with pid 3497
Nov 17 09:58:50 linux-poqz.suse NetworkManager[1633]: <warn>  libnl does not support extended IFA_FLAGS needed by NM for IPv6 private addresses. This feature is not available
Nov 17 09:58:52 linux-poqz.suse avahi-daemon[1505]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::3e95:9ff:fe96:981d.
Nov 17 09:58:52 linux-poqz.suse avahi-daemon[1505]: New relevant interface wlan0.IPv6 for mDNS.
Nov 17 09:58:52 linux-poqz.suse avahi-daemon[1505]: Registering new address record for fe80::3e95:9ff:fe96:981d on wlan0.*.
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    address 172.16.17.221
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    plen 24 (255.255.255.0)
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    gateway 172.16.17.1
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    server identifier 172.16.17.1
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    lease time 3600
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    nameserver '205.171.3.65'
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>    nameserver '8.8.8.8'
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): DHCPv4 state changed unknown -> bound
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  NetworkManager state is now CONNECTED_LOCAL
Nov 17 09:58:55 linux-poqz.suse avahi-daemon[1505]: Joining mDNS multicast group on interface wlan0.IPv4 with address 172.16.17.221.
Nov 17 09:58:55 linux-poqz.suse avahi-daemon[1505]: New relevant interface wlan0.IPv4 for mDNS.
Nov 17 09:58:55 linux-poqz.suse avahi-daemon[1505]: Registering new address record for 172.16.17.221 on wlan0.IPv4.
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  NetworkManager state is now CONNECTED_SITE
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  Policy set 'wildflower-g' (wlan0) as default for IPv4 routing and DNS.
Nov 17 09:58:55 linux-poqz.suse nscd[1520]: 1520 monitored file `/etc/resolv.conf` was written to
Nov 17 09:58:55 linux-poqz.suse NetworkManager[1633]: <info>  (wlan0): Activation: successful, device activated.
Nov 17 09:58:55 linux-poqz.suse dbus[1479]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 17 09:58:55 linux-poqz.suse systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 17 09:58:55 linux-poqz.suse dbus[1479]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 17 09:58:55 linux-poqz.suse systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 17 09:58:55 linux-poqz.suse nm-dispatcher[3607]: Dispatching action 'up' for wlan0
Nov 17 09:59:27 linux-poqz.suse kernel: fuse init (API version 7.23)
Nov 17 09:59:27 linux-poqz.suse systemd[1]: Mounting FUSE Control File System...
Nov 17 09:59:27 linux-poqz.suse systemd[1]: Mounted FUSE Control File System.
Nov 17 09:59:45 linux-poqz.suse NetworkManager[1633]: <info>  connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving 'conncheck.opensuse.org': Temporary failure in name resolution'
Nov 17 09:59:45 linux-poqz.suse NetworkManager[1633]: <info>  connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving 'conncheck.opensuse.org': Temporary failure in name resolution'

Note that the connectivity check fails. I remained connected as long as I desired so that I could collect the requested information.
Opening Firefox and attempting to access www.example.com and address 172.16.17.221 failed to find the host in both cases. I will have to try the gateway another time.

What triggers the

Nov 17 09:58:50 linux-poqz.suse kernel: wlan0: authenticate with 00:25:84:0f:14:a0

sequence as that did not occur at the other site?
I will attempt to collect the “iw scan” information at the other site tomorrow so it can be compared.

#10

The output that counts is the one in relation to the public wifi situation where clearly the association doesn’t complete as the original NM logging showed (and arvidjaar commented on already).

#11

Examine the kernel output while trying to connect to the public wifi

dmesg --follow

That might help with progressing this (although it may well be an 802.1X supplicant related issue I suppose).

#12

A clarification requested by arvidjaar -
[Problem]
Access to a Public WiFi Access Point in most cases requires agreeing to a set of “Terms and Conditions”, providing an email address, entering an assigned password.
Sometimes more than one of these is required. In order to assure that this is done, the Access Point (AP) blocks access to the internet until a form on a browser page is completed and submitted.
This process can be automatic (in Windows 10, connecting to the AP triggers the browser to start and displays the page sent by the AP. The user completes the form and submits it.) or manual (An AP is selected via the Network Manager, the user manually opens their browser of choice and attempts to access the internet. The AP returns its browser page, the user completes the page and submits it).
All of this AP processing is commonly referred to as a “Captive Portal”. Numerous descriptions of this exist including the one on Wikipedia at https://en.wikipedia.org/wiki/Captive_portal
There appears to be no standard implementation for the operation of a “Captive Portal” which makes troubleshooting issues difficult.

My specific problem is that a vanilla install of Leap 42.3 cannot manage this process. An old install of openSUSE 13.2 and a current install of Windows 10 both work properly. Both of the non-Leap systems navigate thru the process and allow access to the internet.
[/Problem]

You can watch Windows’s process when you select an AP for connection. The AP is selected, Edge is brought up with msftconnecttest.com in the address bar. This is replaced with the link address of the Captive Portal Login Page which is then displayed.
A CURL request to the Microsoft address returns a response.


curl --include http://msftconnecttest.com/
HTTP/1.1 302 Found
Cache-Control: private
Content-Type: text/html; charset=utf-8
Location: http://www.msftconnecttest.com/
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Sun, 19 Nov 2017 23:27:13 GMT
Content-Length: 113



<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head><title>

</title></head>

</html>

The openSUSE connectivity section specified in the NetworkManager.conf file acts in a similar manner but returns a different code and no content.


curl --include http://conncheck.opensuse.org
HTTP/1.0 204 No Content
Cache-Control: no-cache
X-NetworkManager-Status: online
Connection: close
Content-Type: text/plain

I attempted access today at the most troublesome location. I used both Windows 10 and Leap 42.3 and collected data as requested earlier in this thread.
The AP in which I am interested is “@Ground Control Free WiFi”.

First Windows 10 after the connection has been made -


ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LAPTOP-UC1BBOTS
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller #2
   Physical Address. . . . . . . . . : 3C-52-82-CF-AE-97
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 3E-95-09-96-98-1D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Realtek RTL8723BE 802.11 bgn Wi-Fi Adapter
   Physical Address. . . . . . . . . : 3C-95-09-96-98-1D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::101c:a58f:2c89:355d%4(Preferred) 
   IPv4 Address. . . . . . . . . . . : 10.231.114.39(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.0.0.0
   Lease Obtained. . . . . . . . . . : Sunday, November 19, 2017 17:15:02
   Lease Expires . . . . . . . . . . : Monday, November 20, 2017 17:15:02
   Default Gateway . . . . . . . . . : 10.128.128.128
   DHCP Server . . . . . . . . . . . : 10.128.128.128
   DHCPv6 IAID . . . . . . . . . . . : 104633609
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-9B-F8-6E-3C-52-82-CF-AE-97
   DNS Servers . . . . . . . . . . . : 10.128.128.128
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 3C-95-09-96-98-1E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:838:2c43:f518:8dd8(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::838:2c43:f518:8dd8%11(Preferred) 
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 486539264
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-9B-F8-6E-3C-52-82-CF-AE-97
   NetBIOS over Tcpip. . . . . . . . : Disabled




netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:445            LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:6646           LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:8733           LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:13148          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:49664          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:49665          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:49666          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:49667          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:49668          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    0.0.0.0:49669          LAPTOP-UC1BBOTS:0      LISTENING
  TCP    10.231.114.39:139      LAPTOP-UC1BBOTS:0      LISTENING
  TCP    10.231.114.39:49763    msnbot-65-52-108-212:https  ESTABLISHED
  TCP    10.231.114.39:49788    bn3sch020010626:https  ESTABLISHED
  TCP    10.231.114.39:49851    a23-209-177-217:http   ESTABLISHED
  TCP    127.0.0.1:5354         LAPTOP-UC1BBOTS:0      LISTENING
  TCP    127.0.0.1:8092         LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:135               LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:445               LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:8733              LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:13148             LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:49664             LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:49665             LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:49666             LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:49667             LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:49668             LAPTOP-UC1BBOTS:0      LISTENING
  TCP    ::]:49669             LAPTOP-UC1BBOTS:0      LISTENING
  UDP    0.0.0.0:5050           *:*                    
  UDP    0.0.0.0:5353           *:*                    
  UDP    0.0.0.0:5355           *:*                    
  UDP    0.0.0.0:6646           *:*                    
  UDP    0.0.0.0:49664          *:*                    
  UDP    10.231.114.39:137      *:*                    
  UDP    10.231.114.39:138      *:*                    
  UDP    10.231.114.39:1900     *:*                    
  UDP    10.231.114.39:5353     *:*                    
  UDP    10.231.114.39:51659    *:*                    
  UDP    127.0.0.1:1900         *:*                    
  UDP    127.0.0.1:51660        *:*                    
  UDP    ::]:5353              *:*                    
  UDP    ::]:5355              *:*                    
  UDP    ::]:49665             *:*                    
  UDP    ::1]:1900             *:*                    
  UDP    ::1]:5353             *:*                    
  UDP    ::1]:51658            *:*                    
  UDP    [fe80::101c:a58f:2c89:355d%4]:1900  *:*                    
  UDP    [fe80::101c:a58f:2c89:355d%4]:51657  *:*
#13

Then Leap 42.3 after the failure to connect -


sudo /usr/sbin/iw dev wlan0 scan

BSS f4:f2:6d:b0:cb:a1(on wlan0)
    TSF: 145070693125 usec (1d, 16:17:50)
    freq: 2437
    beacon interval: 100 TUs
    capability: ESS ShortSlotTime RadioMeasure (0x1401)
    signal: -70.00 dBm
    last seen: 436 ms ago
    Information elements from Probe Response frame:
    SSID: TP-LINK_Extender_2.4GHz
    Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
    DS Parameter set: channel 6
    ERP: <no flags>
    ERP D4.0: <no flags>
    Extended supported rates: 6.0 9.0 12.0 48.0 
    HT capabilities:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT RX MCS rate indexes supported: 0-23, 32
        HT TX MCS rate indexes are undefined
    HT operation:
         * primary channel: 6
         * secondary channel offset: above
         * STA channel width: any
         * RIFS: 1
         * HT protection: no
         * non-GF present: 0
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    Extended capabilities: Extended Channel Switching, 6
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 15-1023, AIFSN 3
         * BK: CW 15-1023, AIFSN 7
         * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
         * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 94:10:3e:82:2d:a8(on wlan0)
    TSF: 82479821141 usec (0d, 22:54:39)
    freq: 2457
    beacon interval: 100 TUs
    capability: ESS Privacy ShortPreamble ShortSlotTime APSD (0x0c31)
    signal: -82.00 dBm
    last seen: 9896 ms ago
    Information elements from Probe Response frame:
    SSID: 
    Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0 
    DS Parameter set: channel 10
    Extended supported rates: 6.0 12.0 24.0 48.0 
    Country: US    Environment: Indoor/Outdoor
        Channels [1 - 11] @ 20 dBm
    TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x80 (+ 1 octet)
    ERP: Use_Protection
    HT capabilities:
        Capabilities: 0x106e
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            No RX STBC
            Max AMSDU length: 3839 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT RX MCS rate indexes supported: 0-15, 32
        HT TX MCS rate indexes are undefined
    HT operation:
         * primary channel: 10
         * secondary channel offset: no secondary
         * STA channel width: 20 MHz
         * RIFS: 0
         * HT protection: 20 MHz
         * non-GF present: 1
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    Overlapping BSS scan params:
         * passive dwell: 20 TUs
         * active dwell: 10 TUs
         * channel width trigger scan interval: 300 s
         * scan passive total per channel: 200 TUs
         * scan active total per channel: 20 TUs
         * BSS width channel transition delay factor: 5
         * OBSS Scan Activity Threshold: 0.25 %
    Extended capabilities: HT Information Exchange Supported
    RSN:     * Version: 1
         * Group cipher: CCMP
         * Pairwise ciphers: CCMP
         * Authentication suites: PSK
         * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 15-1023, AIFSN 3
         * BK: CW 15-1023, AIFSN 7
         * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
         * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
    BSS Load:
         * station count: 6
         * channel utilisation: 78/255
         * available admission capacity: 31250 *32us]
BSS c4:ea:1d:3a:f1:80(on wlan0)
    TSF: 145086464387 usec (1d, 16:18:06)
    freq: 2437
    beacon interval: 100 TUs
    capability: ESS Privacy ShortSlotTime (0x0411)
    signal: -86.00 dBm
    last seen: 492 ms ago
    Information elements from Probe Response frame:
    SSID: CenturyLink0607
    Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
    DS Parameter set: channel 6
    TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0
    ERP: <no flags>
    ERP D4.0: <no flags>
    RSN:     * Version: 1
         * Group cipher: TKIP
         * Pairwise ciphers: CCMP
         * Authentication suites: PSK
         * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
    Extended supported rates: 6.0 9.0 12.0 48.0 
    HT capabilities:
        Capabilities: 0x183c
            HT20
            SM Power Save disabled
            RX Greenfield
            RX HT20 SGI
            No RX STBC
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT RX MCS rate indexes supported: 0-15
        HT TX MCS rate indexes are undefined
    HT operation:
         * primary channel: 6
         * secondary channel offset: no secondary
         * STA channel width: 20 MHz
         * RIFS: 1
         * HT protection: no
         * non-GF present: 0
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    WPS:     * Version: 1.0
         * Wi-Fi Protected Setup State: 2 (Configured)
         * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
    WPA:     * Version: 1
         * Group cipher: TKIP
         * Pairwise ciphers: TKIP
         * Authentication suites: PSK
         * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
    WMM:     * Parameter version 1
         * BE: CW 15-1023, AIFSN 3
         * BK: CW 15-1023, AIFSN 7
         * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
         * VO: CW 3-7, AIFSN 2, TXOP 1504 usec




sudo /usr/sbin/hwinfo --wlan

26: PCI 300.0: 0282 WLAN controller
  [Created at pci.378]
  Unique ID: y9sn.ir4uVzTW3gD
  Parent ID: Rtk9.fX2jjCxTjj4
  SysFS ID: /devices/pci0000:00/0000:00:02.4/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Device Name: "WLAN Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2"
  Model: "Realtek RTL8723BE PCIe Wireless Network Adapter"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0xb723 "RTL8723BE PCIe Wireless Network Adapter"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x81c1 
  Driver: "rtl8723be"
  Driver Modules: "rtl8723be"
  Device File: wlan0
  Features: WLAN
  I/O Ports: 0xd000-0xd0ff (rw)
  Memory Range: 0xfe800000-0xfe803fff (rw,non-prefetchable)
  IRQ: 41 (no events)
  HW Address: 3c:95:09:96:98:1d
  Permanent HW Address: 3c:95:09:96:98:1d
  Link detected: no
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v000010ECd0000B723sv0000103Csd000081C1bc02sc80i00"
  Driver Info #0:
    Driver Status: rtl8723be is active
    Driver Activation Cmd: "modprobe rtl8723be"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #8 (PCI bridge)

I am posting the journal in paste.opensuse.org. URL: http://paste.opensuse.org/36405450

#14

Your openSUSE scan results didn’t show the SSID:’@Ground Control Free WiFi’

Also I’d like to see the ‘dmesg -w’ output related to a connection attempt.

#15

I note that the RSSI values for all the APs picked up in the scan results are very weak (-70dBm and worse). That might be an issue here. I note a number of reports concerning some wireless hardware using the rtl8723be driver, related to internal antenna mis-configuration with some hardware implementations, and it results in low received signal levels. The driver can be loaded with the antenna number specfied explicitly at boot…

https://github.com/lwfinger/rtlwifi_new/issues/88

#16

I know what captive portal is, you did not need to repeat that. What you apparently miss is the fact that accessing captive portal requires that connection to AP is established and IP address is configured - and your system never gets as far.

This log shows connection to AP that is not listed in scan results. Also it is different from previous log snippets in that authentication was actually started, but apparently AP does not respond to it.

#17

Apparently the failure causes a modification to the listing and I missed it. The listing before the Leap attempt has the SSID.
I realize the authentication fails so the AP isn’t connected to. I just don’t know why.


iw listing before connection attempt with <<<<<=====   The one we want

BSS f4:f2:6d:b0:cb:a1(on wlan0)
    TSF: 144761282091 usec (1d, 16:12:41)
    freq: 2437
    beacon interval: 100 TUs
    capability: ESS ShortSlotTime RadioMeasure (0x1401)
    signal: -64.00 dBm
    last seen: 7188 ms ago
    Information elements from Probe Response frame:
    SSID: TP-LINK_Extender_2.4GHz
    Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
    DS Parameter set: channel 6
    ERP: <no flags>
    ERP D4.0: <no flags>
    Extended supported rates: 6.0 9.0 12.0 48.0 
    HT capabilities:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT RX MCS rate indexes supported: 0-23, 32
        HT TX MCS rate indexes are undefined
    HT operation:
         * primary channel: 6
         * secondary channel offset: above
         * STA channel width: any
         * RIFS: 1
         * HT protection: no
         * non-GF present: 0
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    Extended capabilities: Extended Channel Switching, 6
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 15-1023, AIFSN 3
         * BK: CW 15-1023, AIFSN 7
         * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
         * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 00:02:6f:12:34:56(on wlan0)
    TSF: 144963686787 usec (1d, 16:16:03)
    freq: 2412
    beacon interval: 100 TUs
    capability: ESS ShortPreamble ShortSlotTime RadioMeasure (0x1421)
    signal: -82.00 dBm
    last seen: 836 ms ago
    Information elements from Probe Response frame:
    SSID: .Public WiFi
    Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 
    DS Parameter set: channel 1
    TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0
    Country: US    Environment: Indoor/Outdoor
        Channels [1 - 11] @ 30 dBm
    ERP: <no flags>
    Extended supported rates: 24.0 36.0 48.0 54.0 
    BSS Load:
         * station count: 0
         * channel utilisation: 47/255
         * available admission capacity: 0 *32us]
    HT capabilities:
        Capabilities: 0x9ad
            RX LDPC
            HT20
            SM Power Save disabled
            RX HT20 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            No DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: No restriction (0x00)
        HT TX/RX MCS rate indexes supported: 0-15
    HT operation:
         * primary channel: 1
         * secondary channel offset: no secondary
         * STA channel width: 20 MHz
         * RIFS: 0
         * HT protection: nonmember
         * non-GF present: 0
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    Extended capabilities: Extended Channel Switching, Proxy ARP Service, TFS, WNM-Sleep Mode, TIM Broadcast, BSS Transition, DMS, 6
    VHT capabilities:
        VHT Capabilities (0x338959b2):
            Max MPDU length: 11454
            Supported Channel Width: neither 160 nor 80+80
            RX LDPC
            short GI (80 MHz)
            TX STBC
            SU Beamformer
            SU Beamformee
            MU Beamformer
            RX antenna pattern consistency
            TX antenna pattern consistency
        VHT RX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT RX highest supported: 0 Mbps
        VHT TX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT TX highest supported: 0 Mbps
    VHT operation:
         * channel width: 0 (20 or 40 MHz)
         * center freq segment 1: 0
         * center freq segment 2: 0
         * VHT basic MCS set: 0xfffc
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 0-0, AIFSN 0, TXOP 2528 usec
         * BK: CW 0-0, AIFSN 0, TXOP 2528 usec
         * VI: CW 0-0, AIFSN 0, TXOP 4096 usec
         * VO: CW 0-0, AIFSN 0, TXOP 2080 usec
BSS 06:02:6f:12:34:56(on wlan0)                                              <<<<<=====   The one we want
    TSF: 144963689400 usec (1d, 16:16:03)
    freq: 2412
    beacon interval: 100 TUs
    capability: ESS ShortPreamble ShortSlotTime RadioMeasure (0x1421)
    signal: -82.00 dBm
    last seen: 832 ms ago
    Information elements from Probe Response frame:
    SSID: @Ground Control Free WiFi
    Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 
    DS Parameter set: channel 1
    TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0
    Country: US    Environment: Indoor/Outdoor
        Channels [1 - 11] @ 30 dBm
    ERP: <no flags>
    Extended supported rates: 24.0 36.0 48.0 54.0 
    BSS Load:
         * station count: 0
         * channel utilisation: 47/255
         * available admission capacity: 0 *32us]
    HT capabilities:
        Capabilities: 0x9ad
            RX LDPC
            HT20
            SM Power Save disabled
            RX HT20 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            No DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: No restriction (0x00)
        HT TX/RX MCS rate indexes supported: 0-15
    HT operation:
         * primary channel: 1
         * secondary channel offset: no secondary
         * STA channel width: 20 MHz
         * RIFS: 0
         * HT protection: nonmember
         * non-GF present: 0
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    Extended capabilities: Extended Channel Switching, Proxy ARP Service, TFS, WNM-Sleep Mode, TIM Broadcast, BSS Transition, DMS, 6
    VHT capabilities:
        VHT Capabilities (0x338959b2):
            Max MPDU length: 11454
            Supported Channel Width: neither 160 nor 80+80
            RX LDPC
            short GI (80 MHz)
            TX STBC
            SU Beamformer
            SU Beamformee
            MU Beamformer
            RX antenna pattern consistency
            TX antenna pattern consistency
        VHT RX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT RX highest supported: 0 Mbps
        VHT TX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT TX highest supported: 0 Mbps
    VHT operation:
         * channel width: 0 (20 or 40 MHz)
         * center freq segment 1: 0
         * center freq segment 2: 0
         * VHT basic MCS set: 0xfffc
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 0-0, AIFSN 0, TXOP 2528 usec
         * BK: CW 0-0, AIFSN 0, TXOP 2528 usec
         * VI: CW 0-0, AIFSN 0, TXOP 4096 usec
         * VO: CW 0-0, AIFSN 0, TXOP 2080 usec
BSS 94:10:3e:82:2d:a8(on wlan0)
    TSF: 82293145970 usec (0d, 22:51:33)
    freq: 2457
    beacon interval: 100 TUs
    capability: ESS Privacy ShortPreamble ShortSlotTime APSD (0x0c31)
    signal: -86.00 dBm
    last seen: 6816 ms ago
    Information elements from Probe Response frame:
    SSID: 
    Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0 
    DS Parameter set: channel 10
    Extended supported rates: 6.0 12.0 24.0 48.0 
    Country: US    Environment: Indoor/Outdoor
        Channels [1 - 11] @ 20 dBm
    TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x80 (+ 1 octet)
    ERP: Use_Protection
    HT capabilities:
        Capabilities: 0x106e
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            No RX STBC
            Max AMSDU length: 3839 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT RX MCS rate indexes supported: 0-15, 32
        HT TX MCS rate indexes are undefined
    HT operation:
         * primary channel: 10
         * secondary channel offset: no secondary
         * STA channel width: 20 MHz
         * RIFS: 0
         * HT protection: 20 MHz
         * non-GF present: 1
         * OBSS non-GF present: 0
         * dual beacon: 0
         * dual CTS protection: 0
         * STBC beacon: 0
         * L-SIG TXOP Prot: 0
         * PCO active: 0
         * PCO phase: 0
    Overlapping BSS scan params:
         * passive dwell: 20 TUs
         * active dwell: 10 TUs
         * channel width trigger scan interval: 300 s
         * scan passive total per channel: 200 TUs
         * scan active total per channel: 20 TUs
         * BSS width channel transition delay factor: 5
         * OBSS Scan Activity Threshold: 0.25 %
    Extended capabilities: HT Information Exchange Supported
    RSN:     * Version: 1
         * Group cipher: CCMP
         * Pairwise ciphers: CCMP
         * Authentication suites: PSK
         * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
    WMM:     * Parameter version 1
         * u-APSD
         * BE: CW 15-1023, AIFSN 3
         * BK: CW 15-1023, AIFSN 7
         * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
         * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
    BSS Load:
         * station count: 6
         * channel utilisation: 26/255
         * available admission capacity: 31250 *32us]

Another possible reason for the weak signal numbers may be that the AP broadcast signal strength may be turned down to a whisper. This is sometimes done to keep the signal within a certain physical space.

There is another discussion about this wlan card that suggests turning off the class N. I will check out the discussion link posted on the antenna selection and test that method.
My initial trial with dmesg gave me what looked like the journal lines but without the timestamps. I will check again.

#18 
BSS 06:02:6f:12:34:56(on wlan0)                                              <<<<<=====   The one we want
    TSF: 144963689400 usec (1d, 16:16:03)
    freq: 2412
    beacon interval: 100 TUs
    capability: ESS ShortPreamble ShortSlotTime RadioMeasure (0x1421)
    signal: -82.00 dBm
    last seen: 832 ms ago
    Information elements from Probe Response frame:
    SSID: @Ground Control Free WiFi

That signal level is unusable. I’m not surprised you don’t get associated. Even if you did succeed, it’s bound to drop soon after.

Another possible reason for the weak signal numbers may be that the AP broadcast signal strength may be turned down to a whisper. This is sometimes done to keep the signal within a certain physical space.

No, that is wrong. I do wireless broadband PtP and enterprise wifi services for a living, and I can tell you that you are unlikely to be able connect, let alone have a stable connection with such levels (especially if in a noisy environment).

There is another discussion about this wlan card that suggests turning off the class N.

Yes, I’ve seen similar too

I will check out the discussion link posted on the antenna selection and test that method.

It’s not hard to unload and reload the driver on the fly with the required options, but the goal will be to get a much stronger signal reported. (Ideally -50dBm or better.)

#19

IMO there are some really fundamental errors in analysis here…

You have to start with understanding the 2 stages connecting to an AP, at least when <not> implementing 802.11x, and 802.11x is rarely found outside of Enterprise setups because it’s more expensive… generally requiring a RADIUS server, and Authenticator. Cheap APs typically implement either WPA-PSK or this thing you’re calling a “Captive Portal”

So,

  1. The client connects wireless to the chosen AP typically by SSD. Unlike 802.11, at this point the AP <will> issue an IP address. The User must provide a WPA password if required (generally not for public WiFi) to continue.
  2. In the scenario being described in this Forum thread, the client is <re-directed> and in the case of Windows may support entering credentials by other means to allow the User to either provide credentials or perform an action (eg checkbox) confirming agreement to Terms of Service and whatever else the Provider wants. Upon confirmation, the Client is then re-directed again or is granted authorization to continue with the network settings already provided.

Important takeaways from what I just described…

  • Unless I’m confused(which is possible), I disagree completely about all that stuff analyzing hardware, whether the hardware is working, etc. <The NIC was given a network address> which can’t happen if all that other lower level stuff wasn’t working. And, if this machine has successfully connected to other WiFi before, then hardware is very unlikely to be the issue.
  • The User is issued working enternet network settings immediately on connection, while still not yet authorized for full access.
  • The Client will need to perform at least one and possibly multiple re-directs, but the critical re-direct is the first one to the Confirmation web page with Terms of Service… And, I’ve found that this re-direct is not always supported in Linux.

That is why, if you go back to my post, following it should get you connected.
I’ve used the procedure I described on many networks successfully, of course assuming that you’re connecting to the right AP.
The trick is just to open a web browser (doesn’t matter what browser) to the right IP address and don’t rely on a re-direct that won’t happen.

So, for instance based on what you posted,
You can try opening your web browser to

https://10.128.128.128

It’s just one try.
On a working machine (eg Windows) you can also use tools like nslookup to verify how the confirmation web page name is resolved.

TSU

#20

I think you are mistaken. The connection process never completed. No association, no IP address. (Refer back to the journal output in post #4.) The user later posts more output in post #9 where a wireless connection does complete, but that is not the public wifi AP (with Captive Portal) that they would like to connect to. The scan results show very low received signal levels that could well be contributing with getting connected IMO (and it is a known issue with some Realtek hardware implementations using this particular driver).