Nie je mozne sa pripojit na AP

Sekcia: Konfigurácia 05.07 | 12:21
Avatar orwill   Používateľ

Dobry den,

vytvoril som si s pomocou raspberry pi W a Arduino mega 2560 maly "growserver" = monitoring rastu chilli papriky. Growserver funguje ako ma, pomocou cidiel zistuje vlhkost pody, polieva, zistene hodnoty zapisuje do suboru. Subor som schopny zobrazit na webstranke webservera (apache) Server je pripojeny pomocou wlan na router, ktory mu dava IP adresu a ja som schopny monitorovat hodnoty a pomocou VNC aj konfigurovat ak nieco treba. Growserver mam vytvoreny pretoze sa casto nenachadzam doma aj niekolko dni a paprika potrebuje polievat. Napadlo ma, ze by som samotny growserver pouzil aj ako AP. Eliminoval by som tym nutnost mat ho napojeny na router. Po case by som to cele mohol prestahovat na zahradu, kde internet nemam. (pripojenie by fungovalo iba na growserver) Na stranke learn.pi-supply.com som nasiel celkom dobry postup na vytvorenie AP za pomoci RPi.

OS pouzivam Raspberry PI OS stiahnuty odtialto Celkovo nastavovanie slo hladko, avsak neviem sa na moj novy AP vobec pripojit. Skusal som pripojenie z Windows laptopu, Apple telefonu, android tabletu a linux laptopu. Vo vsetkych pripadoch sa zariadenia iba snazia pripojit, ale k pripojeniu neprichadza. Nazov AP sa ukazuje na vsetkych zariadeniach. Ikona AP (dve protichodne sipky) je viditelna namiesto wifi client icon na desktope growservera Hostapd a dnsmasq services hlasia Active running.

Netusite kde moze byt problem? Prikladam conf subory a vypisy z services hostapd a dnsmasq v zip subore. V pripade potreby som schopny dodat dalsie subory. Budem rad, ked spolocne chybu najdeme.

    • RE: Nie je mozne sa pripojit na AP 05.07 | 13:45
      Avatar Branislav Poldauf Manjaro, Debian stable  Používateľ

      ja sa tomu prd rozumiem ale nesnazis sa pouzit jednu sietovu wifi kartu aj na to aby bola AP aj aby sa pripajala k wifi z routra ako klient ?

      lebo to ti asi nebude fungovat a budes potrebovaz druhu wifinku alebo pripojenie kablom

      Linux: the operating system with a CLUE... Command Line User Environment
      • RE: Nie je mozne sa pripojit na AP 05.07 | 15:11
        Avatar orwill   Používateľ

        Nie. To co chcem dosiahnut je mat Raspberry PI Zero W ako AP bez pripojenia do internetu. Chcem sa pripojit na RPi ako na AP a nie na wifi router. Growserver chcem mat portabilny a nie zavisly na dosahu routera.

    • RE: Nie je mozne sa pripojit na AP 05.07 | 15:28
      Avatar Miroslav Bendík Gentoo  Administrátor

      Z linuxového notebooku by som sa rád pozrel na výpis z wpa-supplicant-u. Vo výpise z hostapd vidím, že po pripojení sa okamžite odpojí. Rád by som videl dôvod, prečo sa klient odpája.

      • RE: Nie je mozne sa pripojit na AP 05.07 | 18:01
        Avatar orwill   Používateľ

        Vypis z wpa_supplicantu. Hmm. akosi to v mojom systeme neviem najst. Je mozne, ze wpa_supplicant logy nie su vytvarane. Pridavam ale dmesg vypis od zaciatku pripajania.

        [  121.583703] wlp2s0: deauthenticating from 84:ad:58:f3:64:b4 by local choice (Reason: 3=DEAUTH_LEAVING)
        [  121.698650] wlp2s0: authenticate with b8:27:eb:f9:f0:29
        [  121.706717] wlp2s0: send auth to b8:27:eb:f9:f0:29 (try 1/3)
        [  121.709627] wlp2s0: authenticated
        [  121.710410] iwlwifi 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
        [  121.710412] iwlwifi 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
        [  121.712154] wlp2s0: associate with b8:27:eb:f9:f0:29 (try 1/3)
        [  121.726207] wlp2s0: RX AssocResp from b8:27:eb:f9:f0:29 (capab=0x411 status=0 aid=1)
        [  121.735833] wlp2s0: associated
        [  121.738287] wlp2s0: deauthenticated from b8:27:eb:f9:f0:29 (Reason: 1=UNSPECIFIED)
        [  125.366137] wlp2s0: authenticate with b8:27:eb:f9:f0:29
        [  125.372912] wlp2s0: send auth to b8:27:eb:f9:f0:29 (try 1/3)
        [  125.376892] wlp2s0: authenticated
        [  125.377095] iwlwifi 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
        [  125.377097] iwlwifi 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
        [  125.380189] wlp2s0: associate with b8:27:eb:f9:f0:29 (try 1/3)
        [  125.394471] wlp2s0: RX AssocResp from b8:27:eb:f9:f0:29 (capab=0x411 status=0 aid=1)
        [  125.396227] wlp2s0: associated
        [  125.400883] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by b8:27:eb:f9:f0:29
        [  125.402746] wlp2s0: deauthenticated from b8:27:eb:f9:f0:29 (Reason: 1=UNSPECIFIED)
        [  126.392768] wlp2s0: authenticate with b8:27:eb:f9:f0:29
        [  126.400126] wlp2s0: send auth to b8:27:eb:f9:f0:29 (try 1/3)
        [  126.403969] wlp2s0: authenticated
        [  126.404141] iwlwifi 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
        [  126.404143] iwlwifi 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
        [  126.408121] wlp2s0: associate with b8:27:eb:f9:f0:29 (try 1/3)
        [  126.422291] wlp2s0: RX AssocResp from b8:27:eb:f9:f0:29 (capab=0x411 status=0 aid=1)
        [  126.425369] wlp2s0: associated
        [  126.432452] wlp2s0: deauthenticated from b8:27:eb:f9:f0:29 (Reason: 1=UNSPECIFIED)
        [  127.420569] wlp2s0: authenticate with b8:27:eb:f9:f0:29
        [  127.429295] wlp2s0: send auth to b8:27:eb:f9:f0:29 (try 1/3)
        [  127.432288] wlp2s0: authenticated
        [  127.433448] iwlwifi 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
        [  127.433450] iwlwifi 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
        [  127.436168] wlp2s0: associate with b8:27:eb:f9:f0:29 (try 1/3)
        [  127.450224] wlp2s0: RX AssocResp from b8:27:eb:f9:f0:29 (capab=0x411 status=0 aid=1)
        [  127.452160] wlp2s0: associated
        [  127.461319] wlp2s0: deauthenticated from b8:27:eb:f9:f0:29 (Reason: 1=UNSPECIFIED)
        [  138.283620] wlp2s0: authenticate with b8:27:eb:f9:f0:29
        [  138.292386] wlp2s0: send auth to b8:27:eb:f9:f0:29 (try 1/3)
        [  138.295606] wlp2s0: authenticated
        [  138.295760] iwlwifi 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
        [  138.295762] iwlwifi 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
        [  138.296095] wlp2s0: associate with b8:27:eb:f9:f0:29 (try 1/3)
        [  138.310267] wlp2s0: RX AssocResp from b8:27:eb:f9:f0:29 (capab=0x411 status=0 aid=1)
        [  138.312560] wlp2s0: associated
        [  138.320292] wlp2s0: deauthenticated from b8:27:eb:f9:f0:29 (Reason: 1=UNSPECIFIED)
        
        • RE: Nie je mozne sa pripojit na AP 05.07 | 19:39
          Avatar orwill   Používateľ

          Podarilo sa mi predsalen nieco najst z wpa_supplicantu (po jeho instalacii a manualnom pokuse o pripojenie cez konzolu >>

          sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp2s0
          
          viliam@Latitude-E7250:~$ sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp2s0
          [sudo] heslo pre používateľa viliam: 
          Successfully initialized wpa_supplicant
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="igrowsystem" auth_failures=1 duration=10 reason=CONN_FAILED
          wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="igrowsystem"
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="igrowsystem" auth_failures=2 duration=23 reason=CONN_FAILED
          wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="igrowsystem"
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="igrowsystem" auth_failures=3 duration=46 reason=CONN_FAILED
          wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="igrowsystem"
          wlp2s0: SME: Trying to authenticate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Trying to associate with b8:27:eb:f9:f0:29 (SSID='igrowsystem' freq=2412 MHz)
          wlp2s0: Associated with b8:27:eb:f9:f0:29
          wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
          wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b8:27:eb:f9:f0:29 reason=1
          wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="igrowsystem" auth_failures=4 duration=77 reason=CONN_FAILED
          
          • RE: Nie je mozne sa pripojit na AP 06.07 | 06:06
            Avatar Miroslav Bendík Gentoo  Administrátor

            Takže z toho výpisu som sa dozvedel zhruba to, čo z predchádzajúceho, takže reason=1 je neznáma príčina. Ešte by som skúsil wpa_supplicant spustiť s parametrom -dd nech vieme z výpisu určiť čo posledné wpa_supplicant posielal.

            • RE: Nie je mozne sa pripojit na AP 06.07 | 20:27
              Avatar orwill   Používateľ

              Problem vyrieseny. Je to divne, ale NetworkManager v Raspberry PI neustale startoval wpa_supplicant. disabloval som Network managera a restartoval dhcpcd.

              Pomohli mi napady odtialto: Server fault teraz dostavam IP adresu a pripajam sa so vestkymi zariadeniami. A chilli? tie zatial musim polievat rucne.