Wireless not connecting...

Robert Heller heller at deepsoft.com
Wed May 29 19:34:23 UTC 2019


At Wed, 29 May 2019 20:32:18 +0200 "Ubuntu user technical support,  not for general discussions" <ubuntu-users at lists.ubuntu.com> wrote:

> 
> 
> 
> hi,
> Am Mittwoch, den 29.05.2019, 13:26 -0400 schrieb Robert Heller:
> > OK, before I totally trown in the towel on this NIC, I just tried
> > connecting 
> > while having a terminal window open.  Here is what iwconfig is
> > telling me 
> > while it is trying to connect:
> 
> and if you check with "ifconfig" at the same time, do you see an ip at
> any point ?

I didn't, but that would only happen if the DHCP server gave out an IP, and 
the DHCP server is never seeing the MAC address.  I espect I would not have 
seen an IP, but I check that at some point (I've shutdown the machine for 
today, maybe I'll look at it on Sat.).

> 
> > 
>> > heller at laptop3: iwconfig wlo1
> > wlo1      IEEE 802.11  ESSID:"wendelllibrary"  
> >           Mode:Managed  Frequency:2.437 GHz  Access Point:
> > DC:9F:DB:3E:F2:9E   
> >           Bit Rate=7.2 Mb/s   Tx-Power=20 dBm   
> >           Retry short limit:7   RTS thr=2347 B   Fragment thr:off
> >           Power Management:off
> >           Link Quality=70/70  Signal level=-35 dBm  
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>> > 
> > So it looks like it is trying to connect, but is failing for some
> > reason.  The 
> > behavior *looks* like a weak signal issue, even though the signal is
> > good.
> 
> what do the logs syslog/journalctl on the machine say while it tries to
> connect ?
> 
> > 
> > And here is what is being logged by the AP (I have the AP direct its
> > log 
> > messages to the server, where the DHCP server is running):
> > 
> > May 28 15:10:49 wirelessap wireless: ath0     Registered
> > node:C8:FF:28:C5:D2:58
> > May 28 15:11:33 wirelessap wireless: ath0     Received deauth from
> > c8:ff:28:c5:d2:58. Reason: Deauthenticated because sending STA is
> > leaving (or has left) the basic service area (3).
> ...
> > 
> > The AP appliance is seeing the connection attempts, but for some
> > reason is not 
> > passing things on to the server for a dhcp address assignment.  The
> > "Reason: 
> > Deauthenticated because sending STA is leaving (or has left) the
> > basic service 
> > area (3). suggests somebody is getting a weak signal...
> 
> are you sure "C8:FF:28:C5:D2:58" is the device you are wanting to
> connect (and not some random dude walking around in the library with a
> WLAN enabled mobile phone) ?
> 
> also, does your AP perhaps have a MAC address filter that blocks DHCP
> requests for non enabled MAC adresses (so you would have to add the
> device to this list) ?
> 
> ciao
> 	oliContent-Description: This is a digitally signed message part
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> 
> iEYEABEKAAYFAlzu0DIACgkQSsOT+6LQaTa6wACeME897ZQDoo4mO7utZ37+Jek+
> mZwAoL1Vkl3NTVkpqhMNeo00NiHicsZj
> =TLri
> -----END PGP SIGNATURE-----
> 
> MIME-Version: 1.0
> 

-- 
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller at deepsoft.com       -- Webhosting Services
                                                                       




More information about the ubuntu-users mailing list