Unable to get working AP + STA with last firmware

avigeilpro
 
Posts: 20
Joined: Wed Mar 22, 2017 5:29 pm

Unable to get working AP + STA with last firmware

Thu Jun 08, 2017 4:22 am

Hi,
All is in the title, with last firmware (2017.05.27) i'm unable to get working AP + STA in same time, if STA is enable (uci set wireless.sta.disabled=0) the Vocore connect to my network, but i don't have the SSID Vocore2, if i disable STA in /etc/config/wireless and reboot i have the Vocore2 SSID, but the Vocore2 doesn't connect to my network. I've all tried, firstboot to reset, flash firmware and uncheck "keep settings", nothing works. Finally i've flashed the old firmware (20161224.bin) and all works perfectly.

Mikchel
 
Posts: 6
Joined: Thu May 18, 2017 6:22 pm

Re: Unable to get working AP + STA with last firmware

Mon Jul 17, 2017 6:47 pm

Hello.
Same problem with 20170527.bin firmware. Can not make connection in sta mode with Zyxel Keenetic DSL router. The difference is that i can connect without (!!!) encryption to AP and can not connect with WPA2 encryption. Here is AP log about wireless connection:
Jul 17 23:41:02wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) had associated successfully.
Jul 17 23:41:03ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:03wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) authentication failed: incorrect PSK.
Jul 17 23:41:05wmond Syslog: last message repeated 2 times.
Jul 17 23:41:05ndm Syslog: last message repeated 2 times.
Jul 17 23:41:07ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:08ndm Syslog: last message repeated 2 times.
Jul 17 23:41:09wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) pairwise key handshaking timeout.
Jul 17 23:41:09wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) had deauthenticated.
Jul 17 23:41:09ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:11wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) authentication failed: incorrect PSK.
Jul 17 23:41:11ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:13wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) authentication failed: incorrect PSK.
Jul 17 23:41:13ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:15ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:16ndm Syslog: last message repeated 2 times.
Jul 17 23:41:17wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) pairwise key handshaking timeout.
Jul 17 23:41:17wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) had deauthenticated.

So physically sta mode is working but it has problems with encryption.
I used psk2, psk-mixed, psk-mixed+tkip+aes and other encryption modes but no luck.
Could someone tell what is the problem? Is is wireless driver problem or may be config files problem or something different?
WBR,

Mikchel
 
Posts: 6
Joined: Thu May 18, 2017 6:22 pm

Re: Unable to get working AP + STA with last firmware

Mon Jul 17, 2017 6:50 pm

Hello.
Same problem with 20170527.bin firmware. Can not make connection in sta mode with Zyxel Keenetic DSL router. The difference is that i can connect without (!!!) encryption to AP and can not connect with WPA2 encryption. Here is AP log about wireless connection:
Jul 17 23:41:02wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) had associated successfully.
Jul 17 23:41:03ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:03wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) authentication failed: incorrect PSK.
Jul 17 23:41:05wmond Syslog: last message repeated 2 times.
Jul 17 23:41:05ndm Syslog: last message repeated 2 times.
Jul 17 23:41:07ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:08ndm Syslog: last message repeated 2 times.
Jul 17 23:41:09wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) pairwise key handshaking timeout.
Jul 17 23:41:09wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) had deauthenticated.
Jul 17 23:41:09ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:11wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) authentication failed: incorrect PSK.
Jul 17 23:41:11ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:13wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) authentication failed: incorrect PSK.
Jul 17 23:41:13ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:15ndm kernel: probe request: SSID=Mandeshevan, BSSID=00:00:00:00:00:00
Jul 17 23:41:16ndm Syslog: last message repeated 2 times.
Jul 17 23:41:17wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) pairwise key handshaking timeout.
Jul 17 23:41:17wmond WifiMaster0/AccessPoint0: (RT2860) STA(ba:d8:12:07:22:6b) had deauthenticated.

So physically sta mode is working but it has problems with encryption.
I used psk2, psk-mixed, psk-mixed+tkip+aes and other encryption modes but no luck.
Could someone tell what is the problem? Is is wireless driver problem or may be config files problem or something different?
WBR,

Vonger
 
Posts: 560
Joined: Sun Oct 19, 2014 6:00 am

Re: Unable to get working AP + STA with last firmware

Tue Jul 18, 2017 11:31 am

I guess there might be broken somewhere, I will check and fix soon.

Mikchel
 
Posts: 6
Joined: Thu May 18, 2017 6:22 pm

Re: Unable to get working AP + STA with last firmware

Tue Jul 18, 2017 5:52 pm

I traced ap_client app which is using for connection in sta mode (i suspect). Generally all parameters looks correct.
Sat May 27 10:09:43 2017 kern.info ap_client: Scanning for networks...
Sat May 27 10:09:48 2017 kern.info ap_client: Found network - 1 is-30 fc:8b:97:56:f1:e3 WPA2PSK
Sat May 27 10:09:48 2017 kern.info ap_client: Found network - 1 molod276 64:70:02:56:4c:a6 WPA1PSKWPA2PSK
Sat May 27 10:09:48 2017 kern.info ap_client: Found network - 2 Keenetic-5298 90:ef:68:fc:5e:a8 WPA2PSK
Sat May 27 10:09:48 2017 kern.info ap_client: Found network - 6 HomeAMack bc:ae:c5:c7:96:15 WPA2PSK
Sat May 27 10:09:48 2017 kern.info ap_client: Found network - 8 Mandeshevan 28:28:5d:a3:a0:28 WPA2PSK
Sat May 27 10:09:48 2017 kern.info ap_client: Found network - 11 NichtFunktioniert c8:6c:87:41:7d:5d WPA2PSK
Sat May 27 10:09:48 2017 kern.info ap_client: Found network, trying to associate (essid: Mandeshevan, bssid: Mandeshevan, channel: 8, enc: WPA2PSK, crypto: AES)
Sat May 27 10:09:58 2017 kern.info ap_client: apcli0 is associated
Sat May 27 10:12:38 2017 kern.info ap_client: apcli0 is not associated

So i can see that network parameters for essid: Mandeshevan detected correctly and next step is wireless driver with private ioctl's. Is it correct?
Does it help if i will recompile other mtk_wifi driver for example from there:
https://github.com/i80s/mtk-sources.git

WBR,

kosmonaut pirx
 
Posts: 17
Joined: Mon Jan 02, 2017 11:35 pm

Re: Unable to get working AP + STA with last firmware

Wed Jul 19, 2017 9:28 pm

hello,
works here.
You may try a simple psk, e.g. 012356789 and check.
regards

Mikchel
 
Posts: 6
Joined: Thu May 18, 2017 6:22 pm

Re: Unable to get working AP + STA with last firmware

Thu Jul 20, 2017 5:39 pm

Damn!!!
You was right. Simple password is working fine.
Actually my password has comma symbol inside: pf,d*****. But previously i used Vocore1 board and it connected fine, also TP-Link routers don't have such issue.
option device 'radio0'
option mode 'sta'
option network 'wwan'
option ifname 'apcli0'
option led 'mediatek:orange:wifi'
option ssid 'Mandeshevan'
option disabled '0'
option encryption 'psk-mixed+tkip+aes'
option key 'pf,d****'

Generally config file looks good....so where can be problem with comma symbol?

WBR,

kosmonaut pirx
 
Posts: 17
Joined: Mon Jan 02, 2017 11:35 pm

Re: Unable to get working AP + STA with last firmware

Fri Jul 21, 2017 9:52 pm

Used mediatek soft seems to have some issues here. Already had this documented here, psk of mine is a 64 char with lots of special chars and did not work either. Additional steps necessary.


But don't know about the comma. Don't get a clue why that should be a problem.


You may try running

iwpriv apcli0 set ApCliWPAPSK=<your psk>

at shell command line. Assuming aplci0 is your interface. It helps putting the psk in double or even single quotes. Don't forget escaping too, in case necessary.

Return to VoCore2

Who is online

Users browsing this forum: No registered users and 2 guests