Database Users

WIFI DHCP problem?

device: 32A Sapphire
rom: xrom-eclair-1.0
i CAN connect to a open ap
i CAN'T connect to a WPA-PSK protected ap
here's the logcat output
part 1:
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 102): Changing supplicant state: SCANNING ==> SCANNING
V/WifiMonitor( 102): Event [Trying to associate with 00:0f:e2:0f:ea:41 (SSID='Aolynk' freq=2437 MHz)]
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]
V/WifiStateTracker( 102): Changing supplicant state: SCANNING ==> ASSOCIATING
D/NetworkStateTracker( 102): setDetailed state, old =SCANNING and new state=CONNECTING
D/ConnectivityService( 102): ConnectivityChange for WIFI: CONNECTING/CONNECTING
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4]
V/WifiStateTracker( 102): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
D/NetworkStateTracker( 102): setDetailed state, old =CONNECTING and new state=CONNECTING
V/WifiMonitor( 102): Event [Associated with 00:0f:e2:0f:ea:41]
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=5]
V/WifiStateTracker( 102): Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE
D/NetworkStateTracker( 102): setDetailed state, old =CONNECTING and new state=AUTHENTICATING
D/ConnectivityService( 102): ConnectivityChange for WIFI: CONNECTING/AUTHENTICATING
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=5]
V/WifiStateTracker( 102): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=6]
V/WifiStateTracker( 102): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=6]
D/NetworkStateTracker( 102): setDetailed state, old =AUTHENTICATING and new state=AUTHENTICATING
V/WifiStateTracker( 102): Changing supplicant state: GROUP_HANDSHAKE ==> GROUP_HANDSHAKE
V/WifiMonitor( 102): Event [WPA: Key negotiation completed with 00:0f:e2:0f:ea:41 [PTK=TKIP GTK=TKIP]]
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7]
V/WifiStateTracker( 102): Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
V/WifiMonitor( 102): Event [CTRL-EVENT-CONNECTED - Connection to 00:0f:e2:0f:ea:41 completed (reauth) [id=2 id_str=]]
V/WifiStateTracker( 102): New network state is CONNECTED
D/WifiStateTracker( 102): DhcpHandler: DHCP request started
D/NetworkStateTracker( 102): setDetailed state, old =AUTHENTICATING and new state=OBTAINING_IPADDR
D/ConnectivityService( 102): ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR
D/SettingsWifiEnabler( 171): Received network state changed to NetworkInfo: type: WIFI[], state: CONNECTING/OBTAINING_IPADDR, reason: (unsp
ecified), extra: (none), roaming: false, failover: false, isAvailable: true
Click to expand...
Click to collapse
obviously no problem with authentication
but, here comes the part 2:
I/WifiStateTracker( 102): DhcpHandler: DHCP request failed: Timed out waiting for DHCP to finish
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=2 state=8]
V/WifiStateTracker( 102): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 102): Deconfiguring interface and stopping DHCP
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
E/wpa_supplicant( 1090): Set_key: Wrong Key
V/WifiMonitor( 102): Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8]
D/NetworkStateTracker( 102): setDetailed state, old =OBTAINING_IPADDR and new state=FAILED
V/WifiStateTracker( 102): New network state is DISCONNECTED
V/WifiStateTracker( 102): Changing supplicant state: DORMANT ==> DORMANT
D/ConnectivityService( 102): ConnectivityChange for WIFI: DISCONNECTED/FAILED
V/ConnectivityService( 102): Attempt to connect to WIFI failed.
D/SettingsWifiEnabler( 171): Received network state changed to NetworkInfo: type: WIFI[], state: DISCONNECTED/FAILED, reason: (unspecified)
, extra: (none), roaming: false, failover: false, isAvailable: true
D/GpsLocationProvider( 102): updateNetworkState unavailable info: NetworkInfo: type: WIFI[], state: DISCONNECTED/FAILED, reason: (unspecifi
ed), extra: (none), roaming: false, failover: false, isAvailable: true
V/WifiMonitor( 102): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 102): Changing supplicant state: DORMANT ==> SCANNING
D/NetworkStateTracker( 102): setDetailed state, old =FAILED and new state=SCANNING
Click to expand...
Click to collapse
what's wrong here?
it's trying to obtain ip address indefinitely

Does the router by chance have MAC address filtering enabled?

no, the router is absolutely clean of any filtering

Well, I figured I'd start by asking the obvious.
A few more questions to clarify things.
Can you connect to this particular router when you disable WPA?
What is the manufacturer and model of the router?
Have you tried connecting to a number of both WPA protected and open routers, or just this one?
Does google tell you that others are having similar problems with this particular router?
I have run into several routers that just didn't like my phone, but with these routers, it doesn't matter if encryption is turned on or off, the phone never connects. I've also noticed that older b and g routers that had some type of "turbo" speed boosting technology would also present a problem. But again, I can't connect to these routers at all, regardless of encryption.

Flaky WiFi. Any solutions?

I can't seem to keep either of our Heros connected to WiFi reliably. It works fine when first turned on, then after 10 or 15 minutes I can't connect to anything. The Hero still shows itself as connected, excellent signal strength, and a valid IP config for my network. All other devices on my network continue to work just fine. Rebooting the phone usually, but not always, gets me another 10 minutes of WiFi connectivity.
I'm running DamageControl with the 2.41.04.02.02 radio. My wife's Hero is, aside from installing Handcent, exactly as it came out of the box. Both display the same symptoms. The problem is also the same regardless of which of my 3 access points I use.
I've spent 2 solid days googling this problem and come up empty handed. Does anybody know of a good solution to this?

Have you tried setting up Static IPs for your phones? To do this, hold down on the WiFi connection and select Advanced Settings.

Yep. I've been building and maintaining corporate networks for over 20 years. The very first thing I did was make sure the phone had valid IP configuration.
I also have the WiFi set to never sleep, per a suggestion I stumbled across on another board. Seems to make no difference.
This is extremely frustrating since both my wife and I rely heavily on data connectivity for our jobs. Living in an area where we're roaming and have 1x data *at best*, WiFi is completely non-optional for us.
Can you recommend a good ssh server for the phone? I'd like to log in and see what it's doing. From the symptoms I've observed it seems like either the DNS config or the routing tables are flaking out.

subliminalurge said:
…Can you recommend a good ssh server for the phone? I'd like to log in and see what it's doing. From the symptoms I've observed it seems like either the DNS config or the routing tables are flaking out.
Click to expand...
Click to collapse
I don't mean to dis your experience. It's always been my practice to answer in forums assuming novice status unless otherwise apparent.
I normally set DNS1 to the router address and let the router handle the job. Can't you SSH locally to test the local WiFi network?
Edit: Sorry... I see you meant an SSH Server for the phone. It should be built into the ROM isn't it?

There is a setting that some how gets set to turn wifi off when it goes to sleep.
Go to Menu > Settings > Wireless and Networks > WiFi Settings > Menu > Advanced > WiFi Sleep Policy > Change from After 15 minutes to Never or Never when plugged in.
Edit:
Disregard just saw your other post saying you have done this.

No worries. I also find it's usually better to oversimplify than to be overly technical when you're unsure of the audience.
What do you mean by "ssh locally"? The local WiFi network is working just fine. I have 3 laptops, 2 iPhones, an iPod touch, and a PS3 connected to it right now, all accessing the Internet just fine. I also have 2 Heros that have no access through the same network.
What I want to do is log in to a command prompt on the phone itself (which is essentially just a small Linux computer) and troubleshoot the network configuration from there. I've pretty much exhausted what can be done through the gui utilities on the phone.

I'm not sure if the 2.1 builds have dropbear installed. If so, it shouldn't be too difficult to enable the built-in ssh server. MoDaCo ROMs not only had it built-in, but enabled out of the box.

Cool. I'll look into getting that up and going.
Logged in through adb, here's where it's at.
Code:
# busybox ifconfig
busybox ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1097 errors:0 dropped:0 overruns:0 frame:0
TX packets:1097 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:101782 (99.3 KiB) TX bytes:101782 (99.3 KiB)
tiwlan0 Link encap:Ethernet HWaddr 00:23:76:BF:F2:A0
inet addr:192.168.5.229 Bcast:192.168.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1090 (1.0 KiB) TX bytes:2000 (1.9 KiB)
This is valid for my lan.
Code:
# busybox route
busybox route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.5.0 * 255.255.255.0 U 0 0 0 tiwlan0
default 192.168.5.1 0.0.0.0 UG 0 0 0 tiwlan0
#
This is also valid.
Let's take DNS out of the equation and ping an IP address. (OpenDNS server. It is up and responding to pings from my laptop at the same time I execute this command.)
Code:
# ping -c 3 208.67.222.222
ping -c 3 208.67.222.222
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
From 192.168.5.229 icmp_seq=2 Destination Host Unreachable
From 192.168.5.229 icmp_seq=3 Destination Host Unreachable
--- 208.67.222.222 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2002ms
#
Not good. The packet isn't even leaving the phone.
Let's just try the router itself.
Code:
# ping -c 3 192.168.5.1
ping -c 3 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
From 192.168.5.229 icmp_seq=1 Destination Host Unreachable
From 192.168.5.229 icmp_seq=3 Destination Host Unreachable
--- 192.168.5.1 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2000ms
#
And finally....
Code:
# ping -c 3 192.168.5.229
ping -c 3 192.168.5.229
PING 192.168.5.229 (192.168.5.229) 56(84) bytes of data.
64 bytes from 192.168.5.229: icmp_seq=1 ttl=64 time=0.427 ms
64 bytes from 192.168.5.229: icmp_seq=2 ttl=64 time=0.428 ms
64 bytes from 192.168.5.229: icmp_seq=3 ttl=64 time=0.427 ms
--- 192.168.5.229 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.427/0.427/0.428/0.016 ms
#
Well, at least the phone can ping itself...
I'll dig in deeper later, but I can now say for certain that this is NOT an IP configuration issue. The phone and access point aren't communicating on the hardware level (although according to the settings screen, the phone thinks it is).
Off the top of my head my best guess right now is that it's going to take some kernel level tweaking to get this resolved.

[Q] PPP suddenly absolutely unusable.

Here's the problem and before you ask I am fully aware that there are problems with pppd at the moment.
Recently, I've been using m-deejay's Froyo Clean Sense build.
Everything was great, PPP was stable enough and when it did drop out the wrapper quickly resolved the issue.
However, after about 3 days of having the build installed, PPP because unusable. I couldn't even open the browser without it dropping out, the upload arrow was just stuck. I tried replacing the wrapper but that didn't help.
Finally, I decided to move onto another build. In this case, I chose HD2ONE 0.3.1a, now the strange thing is that the PPP instability continued with this build, except it was so bad I couldn't even finish the initial setup. The 0.3 wrapper didn't seem to do anything to fix this.
I tried switching kernels from hastarin r8.2 to m-deejay's S2 and S3.1 kernels but the problem persisted.
Currently on the 2.15.50.14 radio with Miri's Titanium Lite Windows Mobile build.
Can anyone help me out here?
Here's a logcat using HD2ONE when the PPP dropped and returned.
Code:
11-14 09:11:14.653: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:14.683: DEBUG/NetworkLocationProvider(2683): updateNetworkState(): Updating network state to 1
11-14 09:11:14.683: DEBUG/GpsLocationProvider(2683): updateNetworkState unavailable info: NetworkInfo: type: mobile[HSDPA], state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: general.t-mobile.uk, roaming: false, failover: false, isAvailable: true
11-14 09:11:14.763: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:14.843: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:14.843: DEBUG/Smack(2828): [XMPPConn] close connection, notifyClosed=false
11-14 09:11:15.003: WARN/Smack/Packet(2828): notify conn break (IOEx), close connection
11-14 09:11:15.003: DEBUG/Smack(2828): [XMPPConn] close: socket already closed, bail
11-14 09:11:19.416: INFO/pppd(3177): Connection terminated.
11-14 09:11:19.416: ERROR/Tethering(2683): attempting to remove unknown iface (ppp0), ignoring
11-14 09:11:19.673: INFO/pppd(3177): Modem hangup
11-14 09:11:19.743: DEBUG/dalvikvm(2828): GC_EXPLICIT freed 1780 objects / 650560 bytes in 81ms
11-14 09:11:19.743: DEBUG/NativeCrypto(2828): Freeing OpenSSL session
11-14 09:11:19.743: DEBUG/NativeCrypto(2828): Freeing OpenSSL session
11-14 09:11:25.623: DEBUG/pppd(3275): using channel 9
11-14 09:11:25.633: DEBUG/Tethering(2683): ppp0 is not a tetherable iface, ignoring
11-14 09:11:25.633: INFO/pppd(3275): Using interface ppp0
11-14 09:11:25.633: INFO/pppd(3275): Connect: ppp0 <--> /dev/smd1
11-14 09:11:25.633: WARN/pppd(3275): Warning - secret file /etc/ppp/pap-secrets has world and/or group access
11-14 09:11:25.633: WARN/pppd(3275): Warning - secret file /etc/ppp/chap-secrets has world and/or group access
11-14 09:11:25.633: INFO/pppd(3275): CHAP authentication succeeded
11-14 09:11:29.553: WARN/pppd(3275): Could not determine remote IP address: defaulting to 10.64.64.64
11-14 09:11:29.553: INFO/pppd(3275): local IP address 178.103.26.198
11-14 09:11:29.553: INFO/pppd(3275): remote IP address 10.64.64.64
11-14 09:11:30.643: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for hipri
11-14 09:11:30.663: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for supl
11-14 09:11:30.663: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for mms
11-14 09:11:30.663: DEBUG/MobileDataStateTracker(2683): default Received state= CONNECTED, old= CONNECTING, reason= (unspecified), apnTypeList= default,supl,mms
11-14 09:11:30.663: DEBUG/NetworkStateTracker(2683): setDetailed state, old =CONNECTING and new state=CONNECTED
11-14 09:11:30.663: DEBUG/ConnectivityService(2683): ConnectivityChange for mobile: CONNECTED/CONNECTED
11-14 09:11:30.673: VERBOSE/NetworkStateTracker(2683): Setting TCP values: [4094,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.umts]
11-14 09:11:30.683: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:30.683: DEBUG/ConnectivityService(2683): adding dns 8.8.8.8 for mobile
11-14 09:11:30.683: DEBUG/ConnectivityService(2683): adding dns 8.8.4.4 for mobile
11-14 09:11:30.683: DEBUG/ConnectivityService(2683): adding dns 8.8.8.8 for mobile
11-14 09:11:30.693: DEBUG/Tethering(2683): Tethering got CONNECTIVITY_ACTION
11-14 09:11:30.693: DEBUG/ConnectivityService(2683): adding dns 8.8.4.4 for mobile
11-14 09:11:30.703: DEBUG/Tethering(2683): MasterInitialState.processMessage what=3
11-14 09:11:30.703: ERROR/HierarchicalStateMachine(2683): TetherMaster - unhandledMessage: msg.what=3
11-14 09:11:30.713: INFO/MediaUploader(3033): No need to wake up
11-14 09:11:30.813: DEBUG/dalvikvm(2683): GC_FOR_MALLOC freed 16383 objects / 966976 bytes in 88ms
11-14 09:11:30.833: DEBUG/NetworkLocationProvider(2683): updateNetworkState(): Updating network state to 2
11-14 09:11:30.843: INFO/GTalkService(2828): [ServiceAutoStarter] --- connectivity changed
11-14 09:11:30.843: INFO/GTalkService(2828): [ServiceAutoStarter] --- start GTalk service ---
11-14 09:11:30.883: DEBUG/GpsLocationProvider(2683): updateNetworkState available info: NetworkInfo: type: mobile[UMTS], state: CONNECTED/CONNECTED, reason: (unspecified), extra: general.t-mobile.uk, roaming: false, failover: false, isAvailable: true
11-14 09:11:46.903: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for hipri
11-14 09:11:46.903: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for supl
11-14 09:11:46.903: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for mms
11-14 09:11:46.903: DEBUG/MobileDataStateTracker(2683): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default,supl,mms
11-14 09:11:46.913: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:51.923: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for hipri
11-14 09:11:51.923: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for supl
11-14 09:11:51.933: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for mms
11-14 09:11:51.933: DEBUG/MobileDataStateTracker(2683): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default,supl,mms
11-14 09:11:51.943: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:55.173: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for hipri
11-14 09:11:55.173: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for supl
11-14 09:11:55.173: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for mms
11-14 09:11:55.173: DEBUG/MobileDataStateTracker(2683): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default,supl,mms
11-14 09:11:55.183: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:11:58.413: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for hipri
11-14 09:11:58.413: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for supl
11-14 09:11:58.413: DEBUG/MobileDataStateTracker(2683): replacing old mInterfaceName (ppp0) with ppp0 for mms
11-14 09:11:58.413: DEBUG/MobileDataStateTracker(2683): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default,supl,mms
11-14 09:11:58.413: DEBUG/NetworkLocationProvider(2683): onDataConnectionStateChanged 3
11-14 09:12:08.198: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.213: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.233: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.243: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.263: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.273: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.293: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.313: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.323: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.343: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.353: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.373: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.393: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.413: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.423: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.443: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.453: DEBUG/lights(2683): set_light_backlight
11-14 09:12:08.473: DEBUG/lights(2683): set_light_backlight

PPTP VPN Problem

Has anyone else had trouble with the VPN on the Atrix?
The issue I have is that, my VPN connects, and indicates it is connected, however once connected I cannot ping any computers on the other side of the VPN. (I can however ping the VPN gateway) And I cannot get my company email.
I have encryption enabled, without it enabled it will not connect. I searched around and people had similar problems with the droid X, but the only solution I found was to install pppd from the SDK over the one on the phone. I tried this but got the exact same results.
My phone is rooted, and I can ssh into it, I also have the SDK and can get an adb shell. I will happily upload any logs or iptables that will aid someone in helping me solve this. Just give me the commands and I'll show you what it outputs.
Thanks

Sounds like a DNS issue, try pinging the computers by their IP address.

joemommasfat said:
Has anyone else had trouble with the VPN on the Atrix?
The issue I have is that, my VPN connects, and indicates it is connected, however once connected I cannot ping any computers on the other side of the VPN. (I can however ping the VPN gateway) And I cannot get my company email.
I have encryption enabled, without it enabled it will not connect. I searched around and people had similar problems with the droid X, but the only solution I found was to install pppd from the SDK over the one on the phone. I tried this but got the exact same results.
My phone is rooted, and I can ssh into it, I also have the SDK and can get an adb shell. I will happily upload any logs or iptables that will aid someone in helping me solve this. Just give me the commands and I'll show you what it outputs.
Thanks
Click to expand...
Click to collapse
Same problem here. This is the first GSM Android phone that I have ever tested that has this problem and I have tested nearly all of the good ones.

Now, I am no network admin, so first off, if I am posting any sensitive info, or anything that may open me up to hacks, please inform me. Second, I don't entirely understand these numbers, but here is the output of my 'route -n', and below that, my 'ifconfig'
192.168.59.68 is my phone on my home wifi. 192.168.59.128 should no be anything. I believe 192.168.101.50 is the local address of the VPN on the remote network (since 101 is not defined in my home network). The ifconfig makes me think 192.168.101.50 patches me through to a local ip of 192.168.101.52 on the remote network. I can ping 192.168.101.52, but not 192.168.101.50.
On the remote network I should also be able to ping subdomain 192.168.155.*, and reach the mail server there, but I cannot.
Now if this helps with any debugging, the same thing happens over 3g and wireless, but if I put the same sim card in my old iphone, I can ping 192.168.155.* and get my company email just fine when connected to the same vpn.
I have also posted the same output from my dd-wrt router, which I have configured to connect to the VPN. The routes look a little different there, and I'm hoping someone with a little more networking knowledge can help me understand/fix my problem.
Thank you.
Code:
$ route -n
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.101.50 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.59.128 192.168.101.50 255.255.255.128 UG 0 0 0 ppp0
192.168.59.0 192.168.101.50 255.255.255.128 UG 0 0 0 ppp0
192.168.59.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.101.50 128.0.0.0 UG 0 0 0 ppp0
128.0.0.0 192.168.101.50 128.0.0.0 UG 0 0 0 ppp0
0.0.0.0 192.168.59.1 0.0.0.0 UG 0 0 0 eth0
below is my ifconfig
Code:
$ ifconfig
ifconfig
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.59.68 Bcast:192.168.59.255 Mask:255.255.255.0
inet6 addr: fe80::42fc:89ff:fe15:39fa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:97 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20724 (20.7 KB) TX bytes:7897 (7.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:839 errors:0 dropped:0 overruns:0 frame:0
TX packets:839 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45205 (45.2 KB) TX bytes:45205 (45.2 KB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:192.168.101.52 P-t-P:192.168.101.50 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1396 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:98 (98.0 B) TX bytes:1592 (1.5 KB)
On my dd-wrt router, which connects and passes data:
Code:
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.101.50 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.155.0 0.0.0.0 255.255.255.0 U 0 0 0 ppp0
192.168.59.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth1
Code:
eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16749239 errors:0 dropped:0 overruns:0 frame:11718459
TX packets:12308018 errors:2 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:187162042 (178.4 MiB) TX bytes:1249060681 (1.1 GiB)
Interrupt:2 Base address:0x5000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:98 errors:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9479 (9.2 KiB) TX bytes:9479 (9.2 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:192.168.101.51 P-t-P:192.168.101.50 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1392 Metric:1
RX packets:828 errors:0 dropped:0 overruns:0 frame:0
TX packets:1123 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:304252 (297.1 KiB) TX bytes:79111 (77.2 KiB)

I'm thinking on moving from my blackberry (which has served me well, but just isn't as dynamic as i need it to be) to an ATRIX.
I had a Samsung Captivate for about 3 days, and returned it because I couldn't get VPN to work.
During my research, I came across this on the web...
code.google.com/p/android/issues/detail?id=4706
(Can't link, too new here just put http in front)
It looks like PPTP VPN Is BROKEN in Android and Google refuses to do a thing about it.
I have a PPTP VPN Server setup on Windows 2003, A separate one on 2008, one on Ubuntu Linux, and also one on a m0n0wall router. NOT A SINGLE ONE WORKS with Android, but has no issues with any other platform.
I hope they get their act together. I need to find someone with Gingerbread out there who can see if maybe they fixed it on 2.3.

jpasint said:
Same problem here. This is the first GSM Android phone that I have ever tested that has this problem and I have tested nearly all of the good ones.
Click to expand...
Click to collapse
I have this also, and have worked my way up past AT&T 2nd & 3rd level support, was passed to Motorola support, worked up through 2nd and 3rd level, and currently have an assigned "support engineer."
He confirmed they have a known bug in their VPN stack filed in their bug tracking system, but no fix release date listed yet.
In reading through a logcat from a failed VPN session I found one of the services crashed with a dump when I disconnected, and that got their attention - I couldn't tell what it meant, but the engineer was impressed with whatever it said, and sounded a bit miffed they hadn't caught the bug before release.
I tried this on the display model in an AT&T store, and got the same result, proving it wasn't just my phone or a side effect of rooting.

Man, thanks gwoozy! Somebody with some free time I guess. Hopefully they'll fix this ASAP.
I never had any success with PPTP with any CDMA droids but every GSM droid I've ever tried worked flawless except sadly the Atrix.
Thanks again for doing the leg work bro.
Joe

I haven't had much luck in the past with PPTP on android while using wap.cingular APN. It worked just fine though when I used isp.cingular via my BB SIM. YMMV

agentdr8 said:
I haven't had much luck in the past with
PPTP on android while using wap.cingular APN. It worked just fine though when I used isp.cingular via my BB SIM. YMMV
Click to expand...
Click to collapse
But if you're on WiFi then the APN doesn't matter so I don't think the wap.cingular could be an issue.
I do remember those days when the isp.cingular and wap.cingular did make the difference for VPN to work or not.
Joe

To follow up, as I see several other people have this same problem - Motorola support does not have a fix, and has no idea if they will EVER have a fix. They are mystified as to what the problem is, and could only point to a Google/Android bug:
code.google.com android project issue 4706
(I can't post external links yet)
which isn't what we are reporting. However, I could see this kind of behavior once I did this:
Root the phone (I know, but the Motorola Level 3 support person working my case suggested it)
Modify the routing tables after connecting to VPN (via an adb shell, su to root)
I had to add a route for the ppp gateway interface - Moto's kernel/Android code didn't make that one
Delete spurious routes for the VPN interface
Add a specific route for the network behind the VPN
Then I could ping an IP address behind the VPN connection and see a response, and even resolve names via the DNS server behind the VPN.
HOWEVER - as soon as I tried to do anything from Android, instead of the command line, such as open a web page in the browser hosted on the server I was currently pinging, everything stopped working - no packet traffic any more.
DNS - fail. PING - suddenly stopped reporting received packets, when it had been chugging along just fine.
That may be the Android bug above, I don't know. But I had to modify the IP routing tables to even see that.
So I will have to trade the Atrix in tomorrow for an HTC. Not worth any more of my time.
I miss Cyanogenmod 6 (which I have on my old G1), running Android 2.2.1 with kernel 2.6.35. Never any problems with that. interesting that free/open has been more stable and error-free for me than a company with a 30-year history with mobile phones.

I can't get PPTP or L2TP VPN work on Atrix 4G, that's strange.

I can't get PPTP VPN to work on the Dell Streak running Froyo. It connects to the host but no data flow. L2TP works fine.

VPN working for me after the new update.
Anyone else?

Yes, I can confirm it is working now

Interesting. I have the update and PPTP vpn still doesn't work for me. Granted it stays connected and works for about 20-30 seconds, but then all traffic fails.
I'm trying to connect to a m0n0wall, and a Windows Server 2003 RAS.
Either way, same result on both. What are you connecting to?

Pptp VPN works for me now too on 1.57

Are either of you rooted?

I am rooted and on 1.57 and PPTP VPN works for me too. I doubt rooted has anything to do with it though.

Yea, I doubt that rooting has anything to do with it as well. Guess I'll keep looking into it.

jsylvia007 said:
Are either of you rooted?
Click to expand...
Click to collapse
I am not rooted.
Joe

Can't connect to wifi

I tried my 2012 Nexus7 grouper after about year or two and it did not connect to my wifi. So reinstalled it - put on latest twrp, and then latest AOSP build (https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514) with google play and it still does not connect - it just quickly goes over save - connecting - authenticating - saved.
It is old device, so it can be hardware failure, but why would it be able to scan networks and not to connect.
I tried upc wifree from neighbors that use different router and it is same.
Code:
05-13 23:02:28.239 514 585 D WifiService: Connect with configID: 0 SSID: "blah" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 1 HIDDEN: false
05-13 23:02:28.239 514 585 D WifiService: NetworkSelectionStatus NETWORK_SELECTION_ENABLED
05-13 23:02:28.239 514 585 D WifiService: hasEverConnected: false
05-13 23:02:28.239 514 585 D WifiService: KeyMgmt: WPA_PSK Protocols: WPA RSN
05-13 23:02:28.239 514 585 D WifiService: AuthAlgorithms:
05-13 23:02:28.239 514 585 D WifiService: PairwiseCiphers: TKIP CCMP
05-13 23:02:28.239 514 585 D WifiService: GroupCiphers: TKIP CCMP
05-13 23:02:28.239 514 585 D WifiService: PSK: *
05-13 23:02:28.239 514 585 D WifiService: Enterprise config:
05-13 23:02:28.239 514 585 D WifiService: altsubject_match NULL
05-13 23:02:28.239 514 585 D WifiService: password <removed>
05-13 23:02:28.239 514 585 D WifiService: ca_path NULL
05-13 23:02:28.239 514 585 D WifiService: subject_match NULL
05-13 23:02:28.239 514 585 D WifiService: engine 0
05-13 23:02:28.239 514 585 D WifiService: client_cert NULL
05-13 23:02:28.239 514 585 D WifiService: ca_cert NULL
05-13 23:02:28.239 514 585 D WifiService: anonymous_identity NULL
05-13 23:02:28.239 514 585 D WifiService: identity NULL
05-13 23:02:28.239 514 585 D WifiService: key_id NULL
05-13 23:02:28.239 514 585 D WifiService: domain_suffix_match NULL
05-13 23:02:28.239 514 585 D WifiService: engine_id NULL
05-13 23:02:28.239 514 585 D WifiService: IP config:
05-13 23:02:28.239 514 585 D WifiService: IP assignment: DHCP
05-13 23:02:28.239 514 585 D WifiService: Proxy settings: NONE
05-13 23:02:28.239 514 585 D WifiService: networkSelectionBSSID=any cuid=1000 cname=android.uid.system:1000 luid=1000 lname=android.uid.system:1000 lcuid=-1 userApproved=USER_APPROVED noInternetAccessExpected=false isCarrierNetwork=false roamingFailureBlackListTimeMilli: 1000
05-13 23:02:28.239 514 585 D WifiService: triggeredLow: 0 triggeredBad: 0 triggeredNotHigh: 0
05-13 23:02:28.239 514 585 D WifiService: ticksLow: 0 ticksBad: 0 ticksNotHigh: 0
05-13 23:02:28.239 514 585 D WifiService: triggeredJoin: 0
05-13 23:02:28.240 514 586 D WifiStateMachine: CONNECT_NETWORK updating existing config with id=0 configKey="v"WPA_PSK
05-13 23:02:28.305 514 1608 D WifiNetworkHistory: saving network history: "v"WPA_PSK gw: null Network Selection-status: NETWORK_SELECTION_ENABLED ephemeral=false choice:null link:0 status:2 nid:0 hasEverConnected: false
05-13 23:02:28.305 514 1608 V WifiNetworkHistory: writeKnownNetworkHistory write config "v"WPA_PSK
05-13 23:02:28.334 514 586 I WifiConnectivityManager: connectToUserSelectNetwork: netId=0 persist=true
05-13 23:02:28.359 514 1610 D WifiNetworkHistory: saving network history: "v"WPA_PSK gw: null Network Selection-status: NETWORK_SELECTION_ENABLED ephemeral=false choice:null link:0 status:2 nid:0 hasEverConnected: false
05-13 23:02:28.359 514 1610 V WifiNetworkHistory: writeKnownNetworkHistory write config "v"WPA_PSK
05-13 23:02:28.362 514 586 I WifiConnectivityManager: scheduleWatchdogTimer
05-13 23:02:28.804 514 586 D WifiStateMachine: CMD_AUTO_CONNECT sup state DisconnectedState my state DisconnectedState nid=0 roam=false
05-13 23:02:28.807 514 586 D WifiStateMachine: CMD_AUTO_CONNECT will save config -> "v" nid=0
05-13 23:02:28.864 514 1616 D WifiNetworkHistory: saving network history: "v"WPA_PSK gw: null Network Selection-status: NETWORK_SELECTION_ENABLED ephemeral=false choice:null link:0 status:2 nid:0 hasEverConnected: false
05-13 23:02:28.864 514 1616 V WifiNetworkHistory: writeKnownNetworkHistory write config "v"WPA_PSK
05-13 23:02:28.889 514 586 D WifiStateMachine: CMD_AUTO_CONNECT did save config -> nid=0
05-13 23:02:28.892 514 1617 D WifiNetworkHistory: saving network history: "v"WPA_PSK gw: null Network Selection-status: NETWORK_SELECTION_ENABLED ephemeral=false choice:null link:0 status:2 nid:0 hasEverConnected: false
05-13 23:02:28.892 514 1617 V WifiNetworkHistory: writeKnownNetworkHistory write config "v"WPA_PSK
05-13 23:02:28.893 710 710 I wpa_supplicant: wlan0: Trying to associate with 2c:56:dc:d0:c2:d8 (SSID='blah' freq=2427 MHz)
05-13 23:02:29.195 710 710 I wpa_supplicant: wlan0: Associated with 2c:56:dc:d0:c2:d8
05-13 23:02:29.195 710 710 I wpa_supplicant: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
05-13 23:02:29.225 710 710 I wpa_supplicant: wlan0: WPA: Key negotiation completed with 2c:56:dc:d0:c2:d8 [PTK=CCMP GTK=CCMP]
05-13 23:02:29.225 710 710 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to 2c:56:dc:d0:c2:d8 completed [id=0 id_str=%7B%22creatorUid%22%3A%221000%22%2C%22configKey%22%3A%22%5C%22v%5C%22WPA_PSK%22%7D]
05-13 23:02:29.233 710 710 W wpa_supplicant: wlan0: WPA: Failed to configure IGTK to the driver
05-13 23:02:29.233 710 710 I wpa_supplicant: wlan0: RSN: Failed to configure IGTK
05-13 23:02:29.241 710 710 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:56:dc:d0:c2:d8 reason=1 locally_generated=1
05-13 23:02:29.248 514 586 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{ ni{[type: WIFI[], state: CONNECTING/CONNECTING, reason: (unspecified), extra: "v", failover: false, available: true, roaming: false, metered: false]} network{103} nethandle{442398067422} lp{{InterfaceName: wlan0 LinkAddresses: [fe80::3285:a9ff:fe5f:e317/64,] Routes: [fe80::/64 -> :: wlan0,] DnsAddresses: [] Domains: null MTU: 0 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576}} nc{[ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps]} Score{20} everValidated{false} lastValidated{false} created{false} lingering{false} explicitlySelected{false} acceptUnvalidated{false} everCaptivePortalDetected{false} lastCaptivePortalDetected{false} }
05-13 23:02:29.249 514 590 D ConnectivityService: NetworkAgentInfo [WIFI () - 103] EVENT_NETWORK_INFO_CHANGED, going from null to CONNECTING
05-13 23:02:29.264 514 586 D WifiHAL : Getting APF capabilities, halHandle = 0x56c6f1e0
05-13 23:02:29.264 514 586 I WifiHAL :
05-13 23:02:29.264 514 586 I WifiHAL : createRequest: APF get capabilities request
05-13 23:02:29.265 514 586 I WifiHAL : Request Response failed for APF, result = -95
05-13 23:02:29.271 514 586 D WifiStateMachine: Start Dhcp Watchdog 4
05-13 23:02:29.275 514 586 D WifiStateMachine: updateCapabilities for config:vfalse,false
05-13 23:02:29.278 514 586 D WifiHAL : Start get packet fate command
05-13 23:02:29.278 514 586 D WifiHAL : createRequest Get Tx packet fate request
05-13 23:02:29.278 514 586 E WifiHAL : Failed to register get pkt fate response; result = -95
05-13 23:02:29.278 514 586 E WifiNative-HAL: getTxPktFatesNative returned -95
05-13 23:02:29.279 514 586 D WifiHAL : Start get packet fate command
05-13 23:02:29.279 514 586 D WifiHAL : createRequest Get Rx packet fate request
05-13 23:02:29.279 514 586 E WifiHAL : Failed to register get pkt fate response; result = -95
05-13 23:02:29.279 514 586 E WifiNative-HAL: getRxPktFatesNative returned -95
05-13 23:02:29.279 514 586 D WifiNative-HAL: stopRssiMonitoring, cmdId 0
05-13 23:02:29.289 514 586 I WifiConnectivityManager: scheduleWatchdogTimer
05-13 23:02:29.293 514 586 D WifiNative-wlan0: configureNeighborDiscoveryOffload(true)
05-13 23:02:29.294 514 590 D ConnectivityService: NetworkAgentInfo [WIFI () - 103] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to DISCONNECTED
05-13 23:02:29.294 514 586 D WifiNative-wlan0: configureNeighborDiscoveryOffload(true) returned: -95
05-13 23:02:29.294 514 590 D ConnectivityService: NetworkAgentInfo [WIFI () - 103] got DISCONNECTED, was satisfying 0
05-13 23:02:29.300 514 587 D DhcpClient: doQuit
05-13 23:02:29.304 514 586 D WifiNetworkAgent: NetworkAgent: NetworkAgent channel lost
05-13 23:02:29.335 514 1623 D DhcpClient: Receive thread started
05-13 23:02:29.336 514 1623 D DhcpClient: Receive thread stopped
05-13 23:02:29.379 514 1621 D DhcpClient: onQuitting
05-13 23:02:29.387 211 497 E Netd : Failed to destroy IPv6 sockets on fe80::3285:a9ff:fe5f:e317: No such file or directory
05-13 23:02:29.387 211 497 E Netd : Error destroying sockets: Unknown error -2
05-13 23:02:29.391 211 505 D CommandListener: Clearing all IP addresses on wlan0

Hi evlo,
I just flashed the latest aosp with open gapps an su 2.79. I only have a problem when I take my n7 down stairs. I get a very weak signal. Othwise on the top two floors of my house I get a pretty strong signal. What kind of signal do you get
Sent from my LG-H901 using Tapatalk

Same here. It connects to an extender but always fails to the router.

It is issue with all google devices i think you need to disable 802.11w or something like that.

Try taking the back cover off and putting it back on. The actual wifi antenna is on the back cover, and it's connected to the motherboard by 2 copper leaf springs. Learned this the hard way after I broke the darn things off my 16gb N7 a couple of years ago. It's now a 32gb unit after replacing the motherboard.
Sent from my SM-T820 using Tapatalk

evlo said:
It is issue with all google devices i think you need to disable 802.11w or something like that.
Click to expand...
Click to collapse
Good to hear that I'm not alone and the circle is free from the just-your-fault trolling at the same time. First time experience. Good news for those whose router's settings interface is working properly unlike mine. Thanks!
My own guesswork prior:
wirelessccie.blogspot.com/2016/01/80211w-aka-pmf.html
Management frames sent to groups of 802.11w stations are protected with this IGTK (used to generate a specific MIC).
Click to expand...
Click to collapse
wlan1nde.wordpress.com/2014/10/21/protected-management-frames-802-11w/
The IEEE 802.11w amendment added this functionality to the 802.11 standard and since July 1st 2014, the Wi-Fi Alliance (WFA) made the support of Protected Management Frames (PMF) mandatory to pass 802.11ac or Passpoint aka HotSpot2.0 R2 interoperability certification.
Click to expand...
Click to collapse
Our beloved grouper was about 2 years ahead of this change.
wikidevi.com/wiki/Google_Nexus_7_(Gen_1,_Wi-Fi_only,_16_GB)
cypress.com/file/298676/download
The BCM4330 will support the following future drafts/standards:
[...]
802.11w — Secure Management Frames
Click to expand...
Click to collapse
Documentation on AW-NH665 is not available and it is unclear to me which one does the job, but it seems to be fair to assume that at least the Broadcom's chip doesn't support it.
android.googlesource.com/platform/external/wpa_supplicant_8/+/lollipop-release/wpa_supplicant/android.config#269
Code:
# IEEE 802.11w (management frame protection), also known as PMF
# [b]Driver support is also needed for IEEE 802.11w[/b].
CONFIG_IEEE80211W=y
Is this enabled for nakasi as well?
Seems to be a security feature, but if there is no driver support, disabling it won't hurt!

Some posts: https://forum.xda-developers.com/sitesearch.php?q=wpa_supplicant 802.11w
Some reference: https://android.googlesource.com/pl...elease/wpa_supplicant/wpa_supplicant.conf#361
Some precedents: https://www.google.com/search?q="/data/misc/wifi/wpa_supplicant.conf"
Code:
### Manually disable Wi-Fi from the Settings or System UI beforehand.
toybox ps -A | grep wpa_supplicant # Make sure wpa_supplicant is not running.
ls -l /data/misc/wifi/wpa_supplicant.conf # Remember the user, group and permissions.
toybox sed -i 's/^pmf=1/pmf=0/' /data/misc/wifi/wpa_supplicant.conf # Replacing "pmf=1" with "pmf=0".
chown wifi.wifi /data/misc/wifi/wpa_supplicant.conf # Is this correct?
chmod 660 /data/misc/wifi/wpa_supplicant.conf # Is this correct?
### Re-enable Wi-Fi.
After this operation, both pmf=1 and pmf=0 vanished from the conf altogether, but the glitch also seems to have gone away. 802.11w (PMF) and wpa_supplicant are involved, for sure.
toybox ps -A -o args | grep wpa_supplicant suggests that /etc/wifi/wpa_supplicant_overlay.conf is another way and android.config suggests that replacing the wpa_supplicant binary is yet another way.
PS: version 20170503 of https://forum.xda-developers.com/nexus-7/development/rom-lineageos-14-1-nexus-7-2012-t3530261 was used.