Wifi problems connecting to my AP



  • I have since some weeks problems to connect to my own Wifi AP at home. It sometimes works and then fails for may hours. I know that you may think "configuration wrong", but that simple it isn't. All my laptops (some 10) and other devices connect fine and it is not just wrong WPA secrets or something like that (because it associates sometimes without changing anything), but even when it associates it does not get always an IP addr, and when it gets one, routing sometimes does not work. I have here an log from today morning, where it was connected, got an IP addr and minutes later it fails associating:

     Dec 21 08:12:04 ubuntu-phablet NetworkManager[1487]: <info>  [1545376324.5073] device (wlan0): supplicant interface state: disconnected -> scanning
    Dec 21 08:12:10 ubuntu-phablet wpa_supplicant[859]: wlan0: Trying to associate with SSID 'tarara'
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.2025] device (wlan0): supplicant interface state: scanning -> associating
    Dec 21 08:12:10 ubuntu-phablet wpa_supplicant[859]: wlan0: Associated with 00:1c:4a:06:17:f5
    Dec 21 08:12:10 ubuntu-phablet kernel: [ 3512.109361][mtk_net][sched]dev_activate dev = wlan0 
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.3170] device (wlan0): supplicant interface state: associating -> associated
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.3292] device (wlan0): supplicant interface state: associated -> 4-way handshake
    Dec 21 08:12:10 ubuntu-phablet wpa_supplicant[859]: wlan0: WPA: Key negotiation completed with 00:1c:4a:06:17:f5 [PTK=CCMP GTK=TKIP]
    Dec 21 08:12:10 ubuntu-phablet wpa_supplicant[859]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:1c:4a:06:17:f5 completed [id=0 id_str=]
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.4107] device (wlan0): supplicant interface state: 4-way handshake -> completed
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.4109] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'tarara'.
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.4116] device (wlan0): state change: config -> ip-config (reason 'none') [50 70 0]
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.4149] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <info>  [1545376330.4260] dhcp4 (wlan0): dhclient started with pid 7759
    Dec 21 08:12:10 ubuntu-phablet NetworkManager[1487]: <warn>  [1545376330.4288] device (wlan0): The kernel does not support extended IFA_FLAGS needed by NM for IPv6 private addresses. This feature is not available
    Dec 21 08:12:10 ubuntu-phablet dhclient: DHCPREQUEST of 192.168.2.32 on wlan0 to 255.255.255.255 port 67 (xid=0x59b674df)
    Dec 21 08:12:19 ubuntu-phablet dhclient: message repeated 2 times: [ DHCPREQUEST of 192.168.2.32 on wlan0 to 255.255.255.255 port 67 (xid=0x59b674df)]
    Dec 21 08:12:19 ubuntu-phablet NetworkManager[1487]: <info>  [1545376339.6071] dhcp4 (wlan0): state changed unknown -> bound
    Dec 21 08:12:19 ubuntu-phablet NetworkManager[1487]: <info>  [1545376339.6363] device (wlan0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
    Dec 21 08:12:19 ubuntu-phablet NetworkManager[1487]: <info>  [1545376339.6595] device (wlan0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
    Dec 21 08:12:19 ubuntu-phablet NetworkManager[1487]: <info>  [1545376339.6889] device (wlan0): state change: secondaries -> activated (reason 'none') [90 100 0]
    Dec 21 08:12:19 ubuntu-phablet NetworkManager[1487]: <info>  [1545376339.7176] policy: set 'tarara' (wlan0) as default for IPv4 routing and DNS
    Dec 21 08:12:19 ubuntu-phablet NetworkManager[1487]: <info>  [1545376339.7806] device (wlan0): Activation: successful, device activated.
    Dec 21 08:12:19 ubuntu-phablet nm-dispatcher: req:1 'up' [wlan0]: new request (3 scripts)
    Dec 21 08:12:19 ubuntu-phablet nm-dispatcher: req:1 'up' [wlan0]: start running ordered scripts...
    Dec 21 08:12:20 ubuntu-phablet logger: 02default_route_workaround: (wlan0): up: flushing routing table (proto boot)
    Dec 21 08:17:03 ubuntu-phablet kernel: [ 3805.492574][mtk_net][sched]dev_deactivate dev = wlan0 
    Dec 21 08:17:03 ubuntu-phablet wpa_supplicant[859]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1c:4a:06:17:f5 reason=0
    Dec 21 08:17:03 ubuntu-phablet NetworkManager[1487]: <info>  [1545376623.7263] device (wlan0): supplicant interface state: completed -> disconnected
    Dec 21 08:17:03 ubuntu-phablet NetworkManager[1487]: <info>  [1545376623.8073] device (wlan0): supplicant interface state: disconnected -> scanning
    Dec 21 08:17:04 ubuntu-phablet wpa_supplicant[859]: wlan0: Trying to associate with SSID 'tarara'
    Dec 21 08:17:04 ubuntu-phablet NetworkManager[1487]: <info>  [1545376624.1755] device (wlan0): supplicant interface state: scanning -> associating
    Dec 21 08:17:04 ubuntu-phablet wpa_supplicant[859]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:1c:4a:06:17:f5 status_code=1
    Dec 21 08:17:04 ubuntu-phablet NetworkManager[1487]: <info>  [1545376624.2842] device (wlan0): supplicant interface state: associating -> disconnected
    

    Any ideas are welcome, because I'm clueless where to look. And as always the AP has no logging features 😞

    The device in question is an BQ E4.5 running 15.04 (r3).



  • @guru maybe it is a radio interfetence problem. Change the channel or set it to auto (router).



  • Thanks for reading and replying. It looks something like that. When I turn off data mobile before turning on Wifi on the device in question, it connects fine to the AP.

    What I do not understand (also on all other UT devices) is, when both, data mobile and Wifi is enabled and connected, there are two default routes visible with netstat -rn. Why? Is this some Linux'sich? Never saw this before on FreeBSD or any other UNIX.



  • Here is an update of the problem and what I did so far. The BQ E4.5 in question now runs 16.04 OTA-7. The problem remains: only one of my four devices show this problem:

    Here is my list of test, outstanding tests and the workaround I have actually:

    
    [v] option checked
    [ ] option unchecked until now
    
    [v] check all channels, one by one, at the moment the router is using CH=4;
        only with CH=6 an IP addr gets assigned, but IP isn't working;
    
    [v] check my old SMC router SMC-WBR14-G2;
        works fine, see below
    
    [ ] check 7430 in a place without any other AP (where?)
    
    [ ] check other AP to find one with the same problem, actually checked,
        all are fine:
          OCLCvisitor ok
              Zinners ok
          Uli         ok
        BQ as hotspot ok
          Kammerloher ok
        ....
    
    [ ] how to debug from inside the AVM router via SSH or TELNET, see:
        https://www.ip-phone-forum.de/threads/fritz-box-7580-firmware-153-06-90-telnet-service-freischalten-geht-auch-f%C3%BCr-7560-und-7590.296678/
    
    [ ] contact AVM:
        https://avm.de/service/supportanfrage/support/FRITZ-Box-7430/de/
    
    
    current workaround:
    
    
    
                                   DSL
                                    ^
                                    |
                          +--------------------+
                          | AVM FIRTZ!Box xxxx |----(Wifi SSID tarara)
                          +--------------------+
                                    |
                                    | 192.168.2.1
    LAN --------+-------------------+--------------------- LAN
                | 192.168.2.222
                |
         +--------------+
         | SMC-WBR14-G2 |----(Wifi SSID smctara)
         +--------------+
    
    The SMC router does not have the DHCP server enabled; all IP (also for the
    SSID smctara) is assigned by the AVM FIRTZ!Box router.
    

    As always, comments are welcome.


Log in to reply