Related
How can help with this problem?
Code:
Sending a DHCP renewal
D/WifiStateTracker( 2717): Disable Bluetooth co-ex mode
V/WifiStateTracker( 2717): AutoIP is disabled
D/WifiStateTracker( 2717): DhcpHandler: DHCP request started
E/wpa_supplicant(11431): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000305, drv->errors = 1, errno = 95 - Operation not supported on transport endpoint)
E/wpa_supplicant(11431): ERROR - Failed to handle rx data filter command!
D/WifiStateTracker( 2717): DHCP renewal started
- wifi disconnect on some router every 5-8 min.
- no problem with the same router on Android 2.3.4
- kernel problem?
Solution for this problem
- it is a problem with android >2.3.6
- there is no fix from google
- Change lease time for IP adress at your router from unlimited to 2 weeks or 2 year or 2 month ....
Code:
--------- beginning of /dev/log/main
D/alogcat (12049): stopped
D/alogcat (12049): starting ...
--------- beginning of /dev/log/system
W/InputManagerService( 2717): Window already focused, ignoring focus gain of: [email protected]
D/RadioSignalLevel( 3382): Gsm Radio Signal level: 4
D/RadioSignalLevel( 3382): Gsm Radio Signal level: 4
W/InputManagerService( 2717): Window already focused, ignoring focus gain of: [email protected]
D/WifiStateTracker( 2717): Sending a DHCP renewal
D/WifiStateTracker( 2717): Disable Bluetooth co-ex mode
V/WifiStateTracker( 2717): AutoIP is disabled
D/WifiStateTracker( 2717): DhcpHandler: DHCP request started
E/wpa_supplicant(11431): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000305, drv->errors = 1, errno = 95 - Operation not supported on transport endpoint)
E/wpa_supplicant(11431): ERROR - Failed to handle rx data filter command!
D/WifiStateTracker( 2717): DHCP renewal started
I/ActivityManager( 2717): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.motorola.blur.home/.HomeActivity } from pid 2717
V/alogcat (12049): save instance
V/alogcat (12049): paused
I/ActivityManager( 2717): No longer want com.android.settings (pid 10969): hidden #21
D/battery_widget_monitor(10800): onReceive:Intent { act=android.appwidget.action.APPWIDGET_UPDATE cmp=ccc71.bmw/.lib.bmw_widget (has extras) }
W/battery_widget_monitor(10800): total active Widgets:4
I/ActivityManager( 2717): Resumed Activity: org.jtb.alogcat/.LogActivity totalTime: 182 ms
D/alogcat (12049): stopping ...
W/InputManagerService( 2717): Starting input on non-focused client [email protected] (uid=10099 pid=12049)
D/alogcat (12049): stopped
I/EventLogService( 3514): Aggregate from 1329512002062 (log), 1329512002062 (data)
I/ActivityManager( 2717): Starting: Intent { act=com.motorola.blur.apps.ACTION_APPS flg=0x10200000 cmp=com.motorola.blur.home/com.motorola.blur.apps.AppsActivity (has extras) } from pid 3414
I/ActivityManager( 2717): Displayed com.motorola.blur.home/com.motorola.blur.apps.AppsActivity: +621ms
D/dalvikvm(12049): GC_EXPLICIT freed 902K, 64% free 3238K/8967K, external 2939K/3671K, paused 70ms
I/ActivityManager( 2717): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.jtb.alogcat/.LogActivity } from pid 3414
V/alogcat (12049): started
I/alogcat (12049): new intent: android.intent.action.MAIN
D/alogcat (12049): stopping ...
D/alogcat (12049): canceling periodic saves
V/alogcat (12049): resumed
D/alogcat (12049): starting ...
I/ActivityManager( 2717): Resumed Activity: org.jtb.alogcat/.LogActivity totalTime: 217 ms
W/InputManagerService( 2717): Starting input on non-focused client [email protected] (uid=10141 pid=3414)
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Error loading keycharmap file '/data/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
Hi,
I found this with TPLINK routers (firewalls, etc.). I think the problem is about TPLINK's DHCP server implementation. I have a TPLINK firewall since 6 month ago, and I have this bug too.
TPLINK's DHCP server deamon (and sometimes their client) has some known incompatbility with ISP's DHCP solutions.
Of course, something is changed in 2.3.6 compared to 2.3.4, because same router is perfectly work with older version.
My workaround about this is disabling DHCP: I use manual IP, or use a "wifi profiler", which turns on/off predefined Fix IP on specified WIFI SSID.
I know it is not a perfect solution in foreign places.
I tried to replace dhcp deamon, wifi drivers, wifi configuration files from 2.3.4, but no success. (I am not a linux expert, so maybe I didn't change every dependent modules, etc.)
DHCP bug is allways present, whenever I'am using open, wep and wpa/wpa2 wireless link - if same DHCP server used.
(OFF: However I have another Wifi bug on CM7/MIUI ROMs with WPA2: after some minutes or transferring a few megabytes, the connection will "stuck" - no more dataflow, I have to reconnect.)
walter79 said:
How can help with this problem?
- wifi disconnect on some router every 5-8 min.
- no problem with the same router on Android 2.3.4
- kernel problem?
Click to expand...
Click to collapse
As a Defy+ user, I'd like to report this bug to official Motorola forum. I've already reported the search bug FC in app drawer. Please tell me how to report.
LeopardSurd said:
As a Defy+ user, I'd like to report this bug to official Motorola forum. I've already reported the search bug FC in app drawer. Please tell me how to report.
Click to expand...
Click to collapse
Copy the Logfile. For me the problem can find on router from Vodafon. (Vodafon Easybox 803 and 903) This router can only buy with a DSL-contract from Vodafon in germany. Maybe it is a kernel problem. I can`t test v3 kernel from motorola. I use a Android 2.3.4 kernel. I tried all v2 gingerbread kernels.
walter79 said:
Copy the Logfile. For me the problem can find on router from Vodafon. (Vodafon Easybox 803 and 903) This router can only buy with a DSL-contract from Vodafon in germany. Maybe it is a kernel problem. I can`t test v3 kernel from motorola. I use a Android 2.3.4 kernel. I tried all v2 gingerbread kernels.
Click to expand...
Click to collapse
ok, thanks!
There is a bug report on Motorola forum:
https://forums.motorola.com/posts/6c79bca040
Any way of using CM's WiFi driver on stock ROM?
Cm7 wifi is way faster than stock!
Can someone test to change ip adress lease time from unlimited to 2 weeks. You have to change this in your router
I found this in the Motorola forums, might help.
https://forums.motorola.com/posts/6808fc89ae
cdlq456 said:
I found this in the Motorola forums, might help.
https://forums.motorola.com/posts/6808fc89ae
Click to expand...
Click to collapse
This a different problem. I think only changing router DHCP settings will work.
I have no problems w Netgear WNR1000 ( this is my router model I think) , my rom is GGL ROM - Defy Green Lens [Android 2.3.6] . WIFI is working as a charm ,it is fast (faster than on CM72 roms) and energy efficient . I used to have problems with roms 2.1 , 2.2 - never with gingerbread roms . But those problems was connected with security settings .
This wifi bug is present in all Android 2.3.6 or 3.2 builds. Samsung has this bug too.
http://code.google.com/p/android/issues/detail?id=20461
There is no fix. You can only change the ip lease time of your router from unlimited to anything else.
I will check that in my router setup .
Solution for this problem
- it is a problem with android >2.3.6
- there is no fix from google
- Change lease time for IP adress at your router from unlimited to 2 weeks or 2 year or 2 month ....
http://review.cyanogenmod.com/#change,6098
Wifi problem is a framework problem. It is fixable by edit framework.jar on each >= android 2.3.6 rom.
I will test the fix on my MS2Ginger rom.
Thanks to quarx he found the fix on cm7 review page.
I know this is an oold thread, but I think that it's importannt that there's a fix that doesn't include changing settings in any rooter:
http://chromloop.com/2011/09/how-to...roblem-wifi-connected-but-no-internet-access/
My friend just bought the Defy+ from a store, new and quite expensive and was REALLY dissapointed to find out that it crashes most(all?) wireless N routers, cause he travels a lot and connects from a lot of random rooters. Applied this easy mod(after Framaroot-ing) and all seems ok after being connected for about 30 minutes now . Hurray!!:victory:
Have faced a problem that my HTC One S don't connect to wi-fi N access point. It stucks at authentication. If I disable N-mode at AP - the phone connects normally. Does anybody have such problem? In both cases WPA2 is used.
bump.... so no one have such problems? or no one is using wifi-n?
have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?
igooor87 said:
have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?
Click to expand...
Click to collapse
Yes, I have tried but no luck. Here is logcat:
I/wpa_supplicant( 4356): wlan0: Trying to associate with yy:yy:yy:yy:yy:yy (SSID='MY-WLAN' freq=2472 MHz)
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): WEXT: Custom wireless event: 'BEACONIEs='
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): wlan0: Associated with yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_roaming is 0
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_disconnect_state is 0
I/wpa_supplicant( 4356): [SeamLess] Flag roam state is mlme_event_disconnect:1514
I/wpa_supplicant( 4356): [SeamLess] We are in roaming_scan_handler to register to timeout handlers
I/wpa_supplicant( 4356): [SeamLess] We requested scan to connect
I/wpa_supplicant( 4356): Setting scan request: 0 sec 0 usec
I/wpa_supplicant( 4356): wpa_supplicant_trigger_scan +
W/wpa_supplicant( 4356): [EAP-MSG] EAP [email protected]: eap_methods not available
I/wpa_supplicant( 4356): [SeamLess] This is already connected so rejected to yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): [SeamLess] flag_disconnect is set i.e., Seamless is give it up
I/wpa_supplicant( 4356): [SeamLess] Event DISASSOC is Generated seamless_roaming_disconnect:438
I/wpa_supplicant( 4356): wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
I/wpa_supplicant( 4356): WPA: Auto connect enabled: try to reconnect (wps=0)
I/wpa_supplicant( 4356): Setting scan request: 0 sec 500000 usec
I/wpa_supplicant( 4356): Setting scan request: 0 sec 100000 usec
I/wpa_supplicant( 4356): wlan0: CTRL-EVENT-DISCONNECTED bssid=yy:yy:yy:yy:yy:yy reason=0
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
BUT, the passphase is correct. If I just turn off N-mode in access point it connects normally.
Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium
doktortaru said:
Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Currently I configure it to use only WPA2 (CCMP/AES cipher) but also tryed with WPA (TKIP cipher) and already tryed to use both WPA+WPA2 - no luck.
P.S.
I'm also have HTC Incredible S and it connects to AP normally in all possible modes while One S won't.
WLAN
Working fine on my Phone.. Problems with your Rom?
Andy2502 said:
Working fine on my Phone.. Problems with your Rom?
Click to expand...
Click to collapse
Have checked with 3 different roms including official. What AP do you have and which speed it suppors (150/300mbps)?
i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.
suhailtheboss said:
i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.
Click to expand...
Click to collapse
radio is 0.16.31501S.17_2_10.23.31501S.10L and the rom is 1.78.401.2, previously was on official T-Mobile DE rom, but currently on LeeDroid. With both roms wifi won't auth with AP in N-mode
Solved by compiling latest compat-wireless for AP.
darkside_ua said:
Solved by compiling latest compat-wireless for AP.
Click to expand...
Click to collapse
Hi, i have the same issue with the original ROM 1.78.401.2.
Could you please explain me how to solve this? My HTC is already rooted...
Thanks
With all of the confusion regarding Miracast adapters (especially the Netgear PTV3000) I thought I'd try to point people in the right direction.
First thing's first, the Netgear PTV3000 does NOT work. It is not certified and has absolutely no connectivity out of the box. It can be flashed
with an experimental firmware to gain crappy functionality but will not work properly until an official update is released.
Edit: The Netgear PTV3000 IS now certified and works great! It's also cheaper than most and is the only stand alone Miracast adapter that can be purchased at Best Buy (or any other offline store for that matter).
So rather than waste your money on a Netgear adapter (like I did) you could buy yourself an Actiontec ScreenBeam which I have confirmed
not only works with the N4 but works great! And if you're not a big fan of Actiontec devices, here is a direct link to the Wi-Fi Alliances list of
Official Miracast Certified Recievers
which are certified (imagine that) to work with the Nexus 4.
Happy screen beaming :laugh:
Not that I don't believe you, but who/how did you confirm the ActionTec works?
I'm looking for some anecdotal reviews and opinions of it. Thanks.
narcopolypse said:
With all of the confusion regarding Miracast adapters (especially the Netgear PTV3000) I thought I'd try to point people in the right direction.
First thing's first, the Netgear PTV3000 does NOT work. It is not certified and has absolutely no connectivity out of the box. It can be flashed
with an experimental firmware to gain crappy functionality but will not work properly until an official update is released.
So rather than waste your money on a Netgear adapter (like I did) you could buy yourself an Actiontec ScreenBeam which I have confirmed
not only works with the N4 but works great! And if you're not a big fan of Actiontec devices, here is a direct link to the Wi-Fi Alliances list of
Official Miracast Certified Recievers
which are certified (imagine that) to work with the Nexus 4.
Happy screen beaming :laugh:
Click to expand...
Click to collapse
Where did you buy it?
Sent from my Galaxy Nexus using Tapatalk 2
plasticdarlow said:
Where did you buy it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First link on Google:
http://www.amazon.com/ACTIONTEC-SBWD100KIT01-ScreenBeam-Universal-Wireless/dp/B009Z8T3K6
Looks like it's not out yet. So the OP is either 1. speculating based on the certification (from just 9 days ago). Or 2. Has some sort of inside connection to get one before they have even gone up for sale.
Guessing it's 1.
Please post a YouTube video!
---------- Post added at 04:32 AM ---------- Previous post was at 04:30 AM ----------
Never mind I found one and it looks like the same adapter from far away....
https://www.youtube.com/watch?v=qjtSzfNVq5E&feature=youtube_gdata_player
---------- Post added at 04:52 AM ---------- Previous post was at 04:32 AM ----------
Aaaand furthermore if you can wait they are sitting in best buy stores according to their website...
http://m.bestbuy.com/m/e/product/detail.jsp?skuId=3179075&pid=1218382979736
I bought ACTIONTEC SBWD100KIT01 ScreenBeam, it should be shipped next week, i will post the results with Nexus 4.
rican408 said:
Aaaand furthermore if you can wait they are sitting in best buy stores according to their website...
http://m.bestbuy.com/m/e/product/detail.jsp?skuId=3179075&pid=1218382979736
Click to expand...
Click to collapse
This isn't the same product that's Miracast certified... Looks the same, but different model numbers.
Sent from my Nexus 4 using xda premium
freesoul27 said:
I bought ACTIONTEC SBWD100KIT01 ScreenBeam, it should be shipped next week, i will post the results with Nexus 4.
Click to expand...
Click to collapse
Where did you order from?
ericshmerick said:
First link on Google:
http://www.amazon.com/ACTIONTEC-SBWD100KIT01-ScreenBeam-Universal-Wireless/dp/B009Z8T3K6
Looks like it's not out yet. So the OP is either 1. speculating based on the certification (from just 9 days ago). Or 2. Has some sort of inside connection to get one before they have even gone up for sale.
Guessing it's 1.
Click to expand...
Click to collapse
Or 3, they have been up for sale on Amazon for a week now but are currently sold out. (seems par for the course with anything related to the N4) Fortunately a friend of mine got one before they sold out. Tested and confirmed working with his Nexus 4.
And FYI this also comes with a little USB dongle that you can plug into any computer to make it Miracast enabled. We tried it with an AMD computer running a Nvidia GPU and it works great!
plasticdarlow said:
Where did you buy it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Amazon
rican408 said:
Where did you order from?
Click to expand...
Click to collapse
Amazon
Sent from my Nexus 4 using Tapatalk 2
narcopolypse said:
We tried it with an AMD computer running a Nvidia GPU and it works great!
Amazon
Click to expand...
Click to collapse
2 things (doubt you can help with the 2nd, but who knows).
1. when you use the USB dongle on the PC, does it mirror the laptop display, or can you configure it as a second screen?
2. Have you tested it with a Galaxy S3 (miracast certified)?
Nothing in the UK though
Sent from my Nexus 4 using xda app-developers app
I received my Actiontec adapter yesterday (bought through Amazon) and it does NOT work with both my nexus 4 devices.
It will try to pair and will fail after 20sec.
One N4 is unlocked and rooted running stock. The other N4 is not rooted and not unlocked fully stock with nothing installed on it.
Both will NOT connect with this adapter.
If anyone was able to get this to work please specify how you did it.
Both my N4's can connect to the Netgear PTV3000 with the beta firmware that was floating around.
Also, the Actiontec comes with a USB dongle that you can use on any PC to mirror its screen. Even that will only connect to the adapter two times in 20 tries...the rest will simply time out.
c4v3man said:
2 things (doubt you can help with the 2nd, but who knows).
1. when you use the USB dongle on the PC, does it mirror the laptop display, or can you configure it as a second screen?
2. Have you tested it with a Galaxy S3 (miracast certified)?
Click to expand...
Click to collapse
1. Didn't try but it did show up as an additional video card in device manager so I assume you could use it as a second screen.
Also, the Miracast standard (and pre release demos) say it should.
2. I couldn't get it to work but that doesn't surprise me.
clubtech said:
I received my Actiontec adapter yesterday (bought through Amazon) and it does NOT work with both my nexus 4 devices.
It will try to pair and will fail after 20sec.
One N4 is unlocked and rooted running stock. The other N4 is not rooted and not unlocked fully stock with nothing installed on it.
Both will NOT connect with this adapter.
If anyone was able to get this to work please specify how you did it.
Both my N4's can connect to the Netgear PTV3000 with the beta firmware that was floating around.
Also, the Actiontec comes with a USB dongle that you can use on any PC to mirror its screen. Even that will only connect to the adapter two times in 20 tries...the rest will simply time out.
Click to expand...
Click to collapse
It will not work on the Nexus 4 if it is rooted. As for not working with on your unrooted one, I don't know what to tell you. We got it to work. (after we figured out it has to be unrooted)
Also, it will only work if you've updated to JOP40D.
screenbeam
narcopolypse said:
Or 3, they have been up for sale on Amazon for a week now but are currently sold out. (seems par for the course with anything related to the N4) Fortunately a friend of mine got one before they sold out. Tested and confirmed working with his Nexus 4.
And FYI this also comes with a little USB dongle that you can plug into any computer to make it Miracast enabled. We tried it with an AMD computer running a Nvidia GPU and it works great!
Amazon
Click to expand...
Click to collapse
Could you do a video for me please? I'm really interested as to how miracast is implemented with the Nexus 4... does it just mirror everything on your screen no matter what app youre using, does it continue working when you turn the screen on the phone off, whats the latency like?
Really interested,
Thanks
narcopolypse said:
1. Didn't try but it did show up as an additional video card in device manager so I assume you could use it as a second screen.
Also, the Miracast standard (and pre release demos) say it should.
2. I couldn't get it to work but that doesn't surprise me.
It will not work on the Nexus 4 if it is rooted. As for not working with on your unrooted one, I don't know what to tell you. We got it to work. (after we figured out it has to be unrooted)
Click to expand...
Click to collapse
That is not accurate. I don't think it has anyhting to do with being rooted or not.
I contacted Actiontec and they responded saying that the shipping firmware will not work with the N4 and that they are working on a beta firmware that will fix the problem.
Since you got it to work, what firmware version is your adapter running?
I got mine today (Actiontec ScreenBeem SBWD100A v1.0.21). It does not work out of the box. (for me anyway)
Logcat is saying something about hdcp failing. apparently qseecom is looking in the wrong directory so i copied the discretix files from /vendor/firmware/discretix to /system/etc/firmware/ but it still wouldnt connect. Interestingly i can connect to it as a wifi-direct device it then disconnects saying the app wasnt found (on the tv). so after that i tried reconnecting the wfd, it connects but looks like hdcp still has issues and actually locks up the device every time. Anyway thats my story.
log snipped
Code:
I/ActivityManager( 544): Displayed com.android.settings/.Settings$WifiDisplaySettingsActivity: +527ms
W/System.err( 1987): Removed 2131231194
W/System.err( 1987): Removed 2131231203
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
I/wpa_supplicant( 699): p2p0: P2P-DEVICE-FOUND 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62 pri_dev_type=8-0050F204-5 name='SBWD-DCA162' config_methods=0x88 dev_capab=0x25 group_capab=0xa wfd_dev_info=0x0000060051022a012c
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/wpa_supplicant( 699): p2p0: P2P-FIND-STOPPED
I/WifiDisplayController( 544): Connecting to Wifi display: SBWD-DCA162
I/wpa_supplicant( 699): p2p0: P2P-INVITATION-RESULT status=0
I/WifiDisplayController( 544): Initiated connection to Wifi display: SBWD-DCA162
E/wpa_supplicant( 699): Using interface p2p0 with hwaddr ea:92:a4:93:6a:82 and ssid "DIRECT-Am-Android_5132"
W/wpa_supplicant( 699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant( 699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant( 699): p2p0: CTRL-EVENT-CONNECTED - Connection to ea:92:a4:93:6a:82 completed (auth) [id=1 id_str=]
I/wpa_supplicant( 699): p2p0: P2P-GROUP-STARTED p2p0 GO ssid="DIRECT-Am-Android_5132" freq=2462 passphrase="GM1GC0rd" go_dev_addr=ea:92:a4:93:6a:82 [PERSISTENT]
D/CommandListener( 160): Setting iface cfg
D/CommandListener( 160): Trying to bring up p2p0
D/TetherController( 160): Starting tethering services
D/TetherController( 160): Tethering services running
D/WifiP2pService( 544): Started Dhcp server on p2p0
I/dnsmasq ( 2012): started, version 2.51 cachesize 150
I/dnsmasq ( 2012): compile time options: no-IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP
W/dnsmasq ( 2012): warning: no upstream servers configured
I/dnsmasq ( 2012): DHCP, IP range 192.168.49.2 -- 192.168.49.254, lease time 1h
I/dnsmasq ( 2012): read /etc/hosts - 1 addresses
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/ThrottleService( 544): unable to find stats for iface rmnet_usb0
D/alsa_ucm( 166): snd_use_case_set(): uc_mgr 0x40bf82a0 identifier _verb value Inactive
D/alsa_ucm( 166): Set mixer controls for HiFi Lowlatency enable 0
D/alsa_ucm( 166): snd_use_case_set(): uc_mgr 0x40bf82a0 identifier _disdev value Speaker
D/alsa_ucm( 166): Set mixer controls for Speaker enable 0
W/wpa_supplicant( 699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant( 699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant( 699): p2p0: AP-STA-CONNECTED 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62
I/wpa_supplicant( 698): Could not set station 10:9f:a9:dc:a1:62 flags for kernel driver (errno=11).
I/WifiDisplayController( 544): Connected to Wifi display: SBWD-DCA162
E/MonoPipe( 166): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
I/AudioFlinger( 166): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer( 166): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger( 166): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer( 166): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/WifiDisplayController( 544): Listening for RTSP connection on 192.168.49.1:7236 from Wifi display: SBWD-DCA162
D/ALSAStreamOps( 166): setParameters(): keyRouting with device 0x0
D/ALSAStreamOps( 166): setParameters(): keyRouting with device 0x0
I/AudioFlinger( 166): AudioFlinger's thread 0x40daf008 ready to run
I/AudioFlinger( 166): AudioFlinger's thread 0x41125008 ready to run
I/r_submix( 166): out_standby()
D/ALSAStreamOps( 166): setParameters(): keyRouting with device 0x0
I/dnsmasq ( 2012): DHCPDISCOVER(p2p0) 10:9f:a9:dc:a1:62
I/dnsmasq ( 2012): DHCPOFFER(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62
I/dnsmasq ( 2012): DHCPREQUEST(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62
I/dnsmasq ( 2012): DHCPACK(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62
I/NetworkSession( 166): incoming connection from 192.168.49.75:44435 (socket 35)
I/NetworkSession( 166): added clientSession 2
I/WifiDisplaySource( 166): We now have a client (2) connected.
I/WifiDisplaySource( 166): Using AAC audio.
I/WifiDisplaySource( 166): Initiating HDCP negotiation w/ host 192.168.49.75:25030
D/QSEECOMAPI: ( 166): QSEECom_start_app sb_length = 0x480
D/QSEECOMAPI: ( 166): App is not loaded in QSEE
W/WifiDisplaySource( 166): Response handler for session 2, cseq 3 returned err -1010 (Unknown error 1010)
I/WifiDisplayController( 544): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController( 544): Wifi display connection failed!
D/QSEECOMAPI: ( 166): Loaded image: APP id = 1
D/DxHDCP ( 166): AKE_SEND_CERT received
D/DxHDCP ( 166): AKE_RECEIVER_INFO received
D/DxHDCP ( 166): AKE_SEND_RRX received
D/DxHDCP ( 166): AKE_SEND_H_PRIME received
D/DxHDCP ( 166): AKE_PAIRING_INFO received
D/DxHDCP ( 166): LC_L_PRIME received
D/DxHDCP ( 166): REPEATERAUTH_SEND_RECEIVERID_LIST received
I/DxHDCPModule( 166): Got callback from DX: 7, 0x43b24874, 0x0
I/DxHDCPModule( 166): Got callback from DX: 9, 0x43b24ea8, 0x0
I/WifiDisplaySource( 166): Saw HDCP notification code 8, ext1 1135759016, ext2 0
E/WifiDisplaySource( 166): HDCP failure, shutting down.
I/WifiDisplayController( 544): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController( 544): Wifi display connection failed!
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/WifiDisplaySource( 166): Initiating HDCP shutdown.
I/WifiDisplayController( 544): Retrying Wifi display connection. Retries left: 2
I/WifiDisplayController( 544): Stopped listening for RTSP connection on 192.168.49.1:7236 from Wifi display: SBWD-DCA162
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
I/wpa_supplicant( 699): p2p0: AP-STA-DISCONNECTED 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62
W/wpa_supplicant( 699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant( 699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant( 699): p2p0: P2P-GROUP-REMOVED p2p0 GO reason=REQUESTED
D/WifiP2pService( 544): Client list empty, remove non-persistent p2p group
D/TetherController( 160): Stopping tethering services
I/dnsmasq ( 2012): exiting on receipt of SIGTERM
D/TetherController( 160): Tethering services stopped
D/WifiP2pService( 544): Stopped Dhcp server
D/CommandListener( 160): Clearing all IP addresses on p2p0
D/NetUtils( 544): android_net_utils_resetConnections in env=0x72438730 clazz=0x33d00001 iface=p2p0 mask=0x3
I/wpa_supplicant( 699): wpa_s->ifname p2p0 cmd SET p2p_group_idle 0
I/wpa_supplicant( 699): p2p0: P2P-DEVICE-LOST p2p_dev_addr=10:9f:a9:dc:a1:62
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/EventLogService( 984): Aggregate from 1355272073669 (log), 1355271525913 (data)
D/dalvikvm( 984): GC_CONCURRENT freed 232K, 3% free 9401K/9660K, paused 3ms+3ms, total 22ms
I/ServiceDumpSys( 984): dumping service [account]
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/dalvikvm( 1987): GC_CONCURRENT freed 131K, 2% free 9378K/9536K, paused 3ms+3ms, total 20ms
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/AudioTrack( 544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
W/AudioTrack( 544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/AudioTrack( 544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
EDIT:
so after reflashing the factory image and relocking the bootloader it is still failing on hdcp
Code:
I/WifiDisplaySource( 164): Initiating HDCP negotiation w/ host 192.168.49.75:25030
W/WifiDisplaySource( 164): Response handler for session 2, cseq 3 returned err -1010 (Unknown error 1010)
I/WifiDisplayController( 595): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
D/QSEECOMAPI: ( 164): QSEECom_start_app sb_length = 0x480
D/QSEECOMAPI: ( 164): App is not loaded in QSEE
E/QSEECOMAPI: ( 164): Error::Cannot open the file /system/etc/firmware/dxhdcp2.mdt
E/QSEECOMAPI: ( 164): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 164): QSEECom_start_app sb_length = 0x480
I/WifiDisplayController( 595): Wifi display connection failed!
D/QSEECOMAPI: ( 164): App is not loaded in QSEE
D/QSEECOMAPI: ( 164): Loaded image: APP id = 1
D/DxHDCP ( 164): AKE_SEND_CERT received
D/DxHDCP ( 164): AKE_RECEIVER_INFO received
D/DxHDCP ( 164): AKE_SEND_RRX received
D/DxHDCP ( 164): AKE_SEND_H_PRIME received
D/DxHDCP ( 164): AKE_PAIRING_INFO received
D/DxHDCP ( 164): LC_L_PRIME received
D/DxHDCP ( 164): REPEATERAUTH_SEND_RECEIVERID_LIST received
I/DxHDCPModule( 164): Got callback from DX: 7, 0x43316874, 0x0
I/DxHDCPModule( 164): Got callback from DX: 9, 0x43316ea8, 0x0
I/WifiDisplaySource( 164): Saw HDCP notification code 8, ext1 1127313064, ext2 0
E/WifiDisplaySource( 164): HDCP failure, shutting down.
I/WifiDisplayController( 595): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController( 595): Wifi display connection failed!
@texasice, it is interesting to see that you are running V1.0.24 while mine is running 1.0.21. Did you get yours from Amazon?
clubtech said:
@texasice, it is interesting to see that you are running V1.0.24 while mine is running 1.0.21. Did you get yours from Amazon?
Click to expand...
Click to collapse
oops sorry typo its v1.0.21 from amazon
I own a few Android devices (an Android 2.3 mobile, an Android 4.0.4 tablet, and an Android 4.1.1 tablet). All of them cannot connect to a PPTP VPN server (it's Windows Server 2008 based, using MS CHAP2 for authentication) with MPPE (PPP encryption) option selected in the client side. Even that a device was rooted and VPNroot (the latest version) is used, the connection still fails. From the log of VPNroot, the error log is "MPPE required but peer negotiation failed". However, if the MPPE option is deselected, devices can connect the PPTP VPN server. Besides, the same can be connected from Windows XP & Windows 7 (with MPPE option enabled).
Due to security issue, I have to connect the PPTP VPN service with MPPE. It makes me unhappy as I cannot use a new tablet due to VPN connection problem. What can I do?
daemongmong said:
I own a few Android devices (an Android 2.3 mobile, an Android 4.0.4 tablet, and an Android 4.1.1 tablet). All of them cannot connect to a PPTP VPN server (it's Windows Server 2008 based, using MS CHAP2 for authentication) with MPPE (PPP encryption) option selected in the client side. Even that a device was rooted and VPNroot (the latest version) is used, the connection still fails. From the log of VPNroot, the error log is "MPPE required but peer negotiation failed". However, if the MPPE option is deselected, devices can connect the PPTP VPN server. Besides, the same can be connected from Windows XP & Windows 7 (with MPPE option enabled).
Due to security issue, I have to connect the PPTP VPN service with MPPE. It makes me unhappy as I cannot use a new tablet due to VPN connection problem. What can I do?
Click to expand...
Click to collapse
VPNroot log attached:
Code:
Connecting to xxxxx port 1723 via wlan0
Connection established (socket = 14)
Sending SCCRQ
Received SCCRP -> Sending OCRQ (local = xxxxx)
Tunnel established
Received OCRQ (remote = xxxxx)
Session established
Creating PPPoX socket
Starting pppd (pppox = 15)
Pppd started (pid = xxxxx)
Using PPPoX (socket = 15)
using channel 3
Using interface ppp100
Connect: ppp100 <-->
Received SLI
MPPE required but peer negotiation failed
Discard non-LCP packet when LCP not open
Discard non-LCP packet when LCP not open
Received SLI
Connection terminated
Received signal 17
Pppd is terminated (status = 10)
Mtpd is terminated (status = 42)
Have you tried open vpn? Cheap vpn service ive been using is http://xtreamvpnworld.blogspot.com
Sent from my WT19i using xda premium
Hey guys,
I was just wondering if anyone else has had issues with VPNs on their Nexus 5? I should add that every one of these settings works flawlessly on my Nexus 7. So anyway, here's my situation:
L2TP/IPSec PSK
Works fine for a while but will eventually time out, anywhere from a few minutes to over an hour after connecting (yet still remains "connected" according to the phone - have to reboot to fix it).
L2TP/IPSec PSK "Always-on"
I get "connected" yet no data is transmitted, at all. Could this have something to do with it (can't post links - code dot google dot com/p/android/issues/detail?id=61948)?
OpenVPN (same result with various clients)
Connects fine for a while - anywhere from a few minutes to over an hour, just as with L2TP - but eventually times out. Here is part of a recent log file from when it starts to go wrong (looks like it gets an 'inactivity timeout'). The red text is where the problem begins. Note that the same thing happens even when plugged in & with the 'always-on screen' developer setting enabled so my phone isn't going to sleep.
Code:
Running on Nexus 5 (hammerhead) google, Android API 19, version 0.5.46, official build
Building configuration…
started Socket Thread
P:Initializing Google Breakpad!
P:eek:penVPN 2.3.2+dspatch4 android-14-armeabi-v7a [SSL (OpenSSL)] [LZO] [SNAPPY] [EPOLL] [MH] [IPv6] built on Sep 12 2013
P:MANAGEMENT: Connected to management server at /data/data/de.blinkt.openvpn/cache/mgmtsocket
P:MANAGEMENT: CMD 'hold release'
P:MANAGEMENT: CMD 'bytecount 2'
P:MANAGEMENT: CMD 'state on'
Network Status: CONNECTED to WIFI "redacted"
P:MANAGEMENT: CMD 'username 'Auth' redacted'
P:MANAGEMENT: CMD 'password [...]'
P:MANAGEMENT: CMD 'proxy NONE'
P:Deprecated TLS cipher name 'DHE-RSA-AES256-SHA', please use IANA name 'TLS-DHE-RSA-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'DHE-DSS-AES256-SHA', please use IANA name 'TLS-DHE-DSS-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'AES256-SHA', please use IANA name 'TLS-RSA-WITH-AES-256-CBC-SHA'
P:MANAGEMENT: >STATE:1383797854,RESOLVE,,,
P:Socket Buffers: R=[163840->131072] S=[163840->131072]
P:Protecting socket fd 4
P:MANAGEMENT: CMD 'needok 'PROTECTFD' ok'
P:UDP link local: (not bound)
P:UDP link remote: [AF_INET]173.245.209.2:443
P:MANAGEMENT: >STATE:1383797854,WAIT,,,
P:MANAGEMENT: >STATE:1383797854,AUTH,,,
P:TLS: Initial packet from [AF_INET]173.245.209.2:443, sid=5baec2e6 9c0dfbdd
P:WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
P:VERIFY OK: depth=1, C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=IPVanish CA, [email protected]
P:VERIFY X509NAME OK: C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=syd-a01.ipvanish.com, [email protected]
P:VERIFY OK: depth=0, C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=syd-a01.ipvanish.com, [email protected]
P:Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
P:Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
P:Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
P:Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
P:Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
P:[syd-a01.ipvanish.com] Peer Connection Initiated with [AF_INET]173.245.209.2:443
P:MANAGEMENT: >STATE:1383797857,GET_CONFIG,,,
P:SENT CONTROL [syd-a01.ipvanish.com]: 'PUSH_REQUEST' (status=1)
P:PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 262144,explicit-exit-notify 5,route-gateway 172.20.32.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.20.32.206 255.255.248.0'
P:eek:PTIONS IMPORT: timers and/or timeouts modified
P:eek:PTIONS IMPORT: explicit notify parm(s) modified
P:eek:PTIONS IMPORT: --sndbuf/--rcvbuf options modified
P:Socket Buffers: R=[131072->524288] S=[131072->131072]
P:eek:PTIONS IMPORT: --ifconfig/up options modified
P:eek:PTIONS IMPORT: route options modified
P:eek:PTIONS IMPORT: route-related options modified
P:eek:PTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
P:ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=wlan0 HWADDR=bc:f5:ac:f2:a5:c2
P:ROUTE6: default_gateway=UNDEF
P:eek:penVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
P:eek:penVPN ROUTE: failed to parse/resolve route for host/network: ::/0
P:do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
P:MANAGEMENT: >STATE:1383797858,ASSIGN_IP,,172.20.32.206,
P:MANAGEMENT: CMD 'needok 'IFCONFIG' ok'
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: >STATE:1383797858,ADD_ROUTES,,,
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: CMD 'needok 'DNSSERVER' ok'
P:MANAGEMENT: CMD 'needok 'DNSSERVER' ok'
Opening tun interface:
Local IPv4: 172.20.32.206/21 IPv6: null MTU: 1500
DNS Server: 198.18.0.1, 198.18.0.2, Domain: null
Routes: 173.245.209.2/32, 0.0.0.0/1, 128.0.0.0/1, 0.0.0.0/0
Routes IPv6:
P:MANAGEMENT: CMD 'needok 'OPENTUN' ok'
P:Initialization Sequence Completed
P:MANAGEMENT: >STATE:1383797859,CONNECTED,SUCCESS,172.20.32.206,173.245.209.2
[COLOR="Red"]P:[syd-a01.ipvanish.com] Inactivity timeout (--ping-restart), restarting[/COLOR]
P:SIGUSR1[soft,ping-restart] received, process restarting
P:MANAGEMENT: >STATE:1383799065,RECONNECTING,ping-restart,,
P:MANAGEMENT: CMD 'hold release'
P:MANAGEMENT: CMD 'bytecount 2'
P:MANAGEMENT: CMD 'state on'
P:MANAGEMENT: CMD 'proxy NONE'
P:Deprecated TLS cipher name 'DHE-RSA-AES256-SHA', please use IANA name 'TLS-DHE-RSA-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'DHE-DSS-AES256-SHA', please use IANA name 'TLS-DHE-DSS-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'AES256-SHA', please use IANA name 'TLS-RSA-WITH-AES-256-CBC-SHA'
P:TCP/UDP: Preserving recently used remote address: [AF_INET]173.245.209.2:443
P:Socket Buffers: R=[163840->524288] S=[163840->131072]
P:Protecting socket fd 4
P:MANAGEMENT: CMD 'needok 'PROTECTFD' ok'
P:UDP link local: (not bound)
P:UDP link remote: [AF_INET]173.245.209.2:443
P:MANAGEMENT: >STATE:1383799081,WAIT,,,
P:[UNDEF] Inactivity timeout (--ping-restart), restarting
P:SIGUSR1[soft,ping-restart] received, process restarting
P:MANAGEMENT: >STATE:1383799152,RECONNECTING,ping-restart,,
P:MANAGEMENT: CMD 'hold release'
P:MANAGEMENT: CMD 'bytecount 2'
P:MANAGEMENT: CMD 'state on'
P:MANAGEMENT: CMD 'proxy NONE'
P:Deprecated TLS cipher name 'DHE-RSA-AES256-SHA', please use IANA name 'TLS-DHE-RSA-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'DHE-DSS-AES256-SHA', please use IANA name 'TLS-DHE-DSS-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'AES256-SHA', please use IANA name 'TLS-RSA-WITH-AES-256-CBC-SHA'
P:TCP/UDP: Preserving recently used remote address: [AF_INET]173.245.209.2:443
P:Socket Buffers: R=[163840->524288] S=[163840->131072]
P:Protecting socket fd 4
P:MANAGEMENT: CMD 'needok 'PROTECTFD' ok'
P:UDP link local: (not bound)
P:UDP link remote: [AF_INET]173.245.209.2:443
P:MANAGEMENT: >STATE:1383799153,WAIT,,,
P:[UNDEF] Inactivity timeout (--ping-restart), restarting
P:SIGUSR1[soft,ping-restart] received, process restarting
P:MANAGEMENT: >STATE:1383799213,RECONNECTING,ping-restart,,
P:MANAGEMENT: CMD 'hold release'
P:MANAGEMENT: CMD 'bytecount 2'
P:MANAGEMENT: CMD 'state on'
P:MANAGEMENT: CMD 'proxy NONE'
P:Deprecated TLS cipher name 'DHE-RSA-AES256-SHA', please use IANA name 'TLS-DHE-RSA-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'DHE-DSS-AES256-SHA', please use IANA name 'TLS-DHE-DSS-WITH-AES-256-CBC-SHA'
P:Deprecated TLS cipher name 'AES256-SHA', please use IANA name 'TLS-RSA-WITH-AES-256-CBC-SHA'
P:TCP/UDP: Preserving recently used remote address: [AF_INET]173.245.209.2:443
P:Socket Buffers: R=[163840->524288] S=[163840->131072]
P:Protecting socket fd 4
P:MANAGEMENT: CMD 'needok 'PROTECTFD' ok'
P:UDP link local: (not bound)
P:UDP link remote: [AF_INET]173.245.209.2:443
P:MANAGEMENT: >STATE:1383799214,WAIT,,,
P:MANAGEMENT: >STATE:1383799230,AUTH,,,
P:TLS: Initial packet from [AF_INET]173.245.209.2:443, sid=a3743100 cabdef57
P:VERIFY OK: depth=1, C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=IPVanish CA, [email protected]
P:VERIFY X509NAME OK: C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=syd-a01.ipvanish.com, [email protected]
P:VERIFY OK: depth=0, C=US, ST=FL, L=Winter Park, O=IPVanish, OU=IPVanish VPN, CN=syd-a01.ipvanish.com, [email protected]
P:Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
P:Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
P:Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
P:Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
P:Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
P:[syd-a01.ipvanish.com] Peer Connection Initiated with [AF_INET]173.245.209.2:443
P:MANAGEMENT: >STATE:1383799243,GET_CONFIG,,,
P:SENT CONTROL [syd-a01.ipvanish.com]: 'PUSH_REQUEST' (status=1)
P:PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 262144,explicit-exit-notify 5,route-gateway 172.20.32.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.20.32.206 255.255.248.0'
P:eek:PTIONS IMPORT: timers and/or timeouts modified
P:eek:PTIONS IMPORT: explicit notify parm(s) modified
P:eek:PTIONS IMPORT: --sndbuf/--rcvbuf options modified
P:Socket Buffers: R=[524288->524288] S=[131072->131072]
P:eek:PTIONS IMPORT: --ifconfig/up options modified
P:eek:PTIONS IMPORT: route options modified
P:eek:PTIONS IMPORT: route-related options modified
P:eek:PTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
P:ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=wlan0 HWADDR=bc:f5:ac:f2:a5:c2
P:ROUTE6: default_gateway=UNDEF
P:eek:penVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
P:eek:penVPN ROUTE: failed to parse/resolve route for host/network: ::/0
P:do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
P:MANAGEMENT: >STATE:1383799244,ASSIGN_IP,,172.20.32.206,
P:MANAGEMENT: CMD 'needok 'IFCONFIG' ok'
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: >STATE:1383799244,ADD_ROUTES,,,
P:MANAGEMENT: CMD 'needok 'ROUTE' ok'
P:MANAGEMENT: CMD 'needok 'DNSSERVER' ok'
P:MANAGEMENT: CMD 'needok 'DNSSERVER' ok'
Opening tun interface:
Local IPv4: 172.20.32.206/21 IPv6: null MTU: 1500
DNS Server: 198.18.0.1, 198.18.0.2, Domain: null
Routes: 173.245.209.2/32, 0.0.0.0/1, 128.0.0.0/1, 0.0.0.0/0
Routes IPv6:
Failed to open the tun interface
Error: command '86 interface fwmark uid add tun1 0 99999' failed with '400 86 Failed to add uid rule (Invalid argument)'
On some custom ICS images the permission on /dev/tun might be wrong, or the tun module might be missing completely. For CM9 images try the fix ownership option under general settings
P:MANAGEMENT: CMD 'needok 'OPENTUN' cancel'
P:MANAGEMENT: Client disconnected
P:ERROR: Cannot open TUN
P:Exiting due to fatal error
P:Sorry, deleting routes on Android is not possible. The VpnService API allows routes to be set on connect only.
P:Sorry, deleting routes on Android is not possible. The VpnService API allows routes to be set on connect only.
P:Sorry, deleting routes on Android is not possible. The VpnService API allows routes to be set on connect only.
P:Closing TUN/TAP interface
MGMT:Got unrecognized command>FATAL:ERROR: Cannot open TUN
Process exited with exit value 1
Any help would be greatly appreciated. Cheers.
Not sure exactly what you are looking for. But here is my thought.
1. It's quite impractical to do an always on VPN for mobile device because aa you move around, you switch from tower to tower and you IP address change, or at least the route established from one tower need to change. So, it would be more like redialing VPN every time you switch tower.
2. if you meant the VPN get time out, you could just go on the terminal amd do a continuous ping to an address on the VPN network.
someone0 said:
Not sure exactly what you are looking for. But here is my thought.
1. It's quite impractical to do an always on VPN for mobile device because aa you move around, you switch from tower to tower and you IP address change, or at least the route established from one tower need to change. So, it would be more like redialing VPN every time you switch tower.
Click to expand...
Click to collapse
That's true; I was just hoping for a VPN connection that would not time out while on the same WiFi connection. Seems to work fine on my older Android devices, just not the Nexus 5 which cannot hold a persistent connection.
someone0 said:
2. if you meant the VPN get time out, you could just go on the terminal amd do a continuous ping to an address on the VPN network.
Click to expand...
Click to collapse
Thanks but I just don't see why this should be necessary. It should work 'out of the box'. Also even if that did work that still wouldn't fix the "Always-on" feature of the phone that never allows a data connection to begin with even when connected, a feature that works on my other (non-4.4) Android devices. support[dot]google[dot]com/nexus/answer/2819573
Looks like it's certainly an issue for others too. I'm just surprised it's not more prevalent; I guess not many people use a VPN on their phone?
Due to a bug in Android 4.4 (KitKat) reported to Google under Issue #61948, AnyConnect users will experience High Packet Loss over their VPN connection (users will experience timeouts when attempting to access certain network resources). In the ASA logs, a syslog message will appear with text similar to "Transmitting large packet 1420 (threshold 1405)."
This has been reported to Google under Issue #61948
Android 4.4 TCP advertises incorrect MSS over VPN (using VpnService)
https://code.google.com/p/android/issues/detail?id=61948
End users may log in with their Google ID and flag the importance of the request as well as enter comments at the link above.
Conditions:
Android 4.4 (KitKat) including the Google Nexus 5
AnyConnect ICS+
Workaround:
Until Google produces a fix for Android 4.4, VPN administrators may temporarily reduce the maximum segment size for TCP connections on the ASA with the configuration command "sysopt connection tcpmss <mss size>". The default for this parameter is 1380 bytes. Reduce this value by the difference between the values seen in the ASA logs. In the above example, the difference is 15 bytes; the value should thus be no more than 1365. Reducing this value will negatively impact performance for connected VPN users where large packets are transmitted.
Click to expand...
Click to collapse
supportforums.cisco.com/thread/2250185
Thank you posting this, I thought I was the only one with this problem judging from Google results.
This really sucks, it breaks openvpn completely. How did Google screw up this bad? I hope they fix it soon.
SHAWDAH said:
Thank you posting this, I thought I was the only one with this problem judging from Google results.
This really sucks, it breaks openvpn completely. How did Google screw up this bad? I hope they fix it soon.
Click to expand...
Click to collapse
Encountered the same issue on Omni's 4.4 build on Nexus 4, hopefully, they will fix that soon enough, as this is a major issue for corporate work.
I usually avoid using proprietary VPN anyway. I'm still trying to get OpenVPN working back up again in my house, but it was always a mess getting OVPN to work with many mobile devices due to tunnel drivers. Atleast I still have L2TP and it always work solidly.
someone0 said:
I usually avoid using proprietary VPN anyway. I'm still trying to get OpenVPN working back up again in my house, but it was always a mess getting OVPN to work with many mobile devices due to tunnel drivers. Atleast I still have L2TP and it always work solidly.
Click to expand...
Click to collapse
What do you mean proprietary VPN? The official OpenVPN android client is proprietary (which is a joke) but OpenVPN for Android is open source.
I was referring to the AnyConnect which is Cisco proprietary VPN. But as far as OpenVPN on Android goes, it is kinda hit and miss. But I know I can always count on L2TP which is build into just almost all Android and iOS. I would still build OpenVPN as you can just route it through any port you want, including TCP port 80 and 443. Which I don't think any wifi hotspot will block those two ports.
bruceau said:
Looks like it's certainly an issue for others too. I'm just surprised it's not more prevalent; I guess not many people use a VPN on their phone?
Click to expand...
Click to collapse
I use VPN all time on my Android phone.I sold all of my Nexus devices so i think im safe for now.
I know this thread's been inactive for a few months now but I'm still having this problem. Manually connecting my VPN through the android settings wLvorks but does eventually drop connections sometimes.
I know of the issues on the AOSP tracker and have them starred.
A comment on one of the issues lists what claims to be working iptables that fix the bug with the VPN.
https://code.google.com/p/android/issues/detail?id=63450#c4
Code:
Chain fw_FORWARD (1 references) target prot opt source destination Chain fw_INPUT (1 references) target prot opt source destination Chain fw_OUTPUT (1 references) target prot opt source destination ============================================================================================================ Always-on VPN iptables: Chain fw_FORWARD (1 references) target prot opt source destination REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain fw_INPUT (1 references) target prot opt source destination RETURN all -- anywhere 192.168.2.11 RETURN all -- anywhere anywhere RETURN udp -- VPN-SERVERS anywhere udp spt:l2f RETURN tcp -- VPN-SERVERS anywhere tcp spt:l2f RETURN udp -- VPN-SERVERS anywhere udp spt:4500 RETURN tcp -- VPN-SERVERS anywhere tcp spt:4500 RETURN udp -- VPN-SERVERS anywhere udp spt:isakmp RETURN tcp -- VPN-SERVERS anywhere tcp spt:isakmp RETURN all -- anywhere anywhere DROP all -- anywhere anywhere Chain fw_OUTPUT (1 references) target prot opt source destination RETURN all -- 192.168.2.11 anywhere RETURN all -- anywhere anywhere RETURN udp -- anywhere VPN-SERVERS udp dpt:l2f RETURN tcp -- anywhere VPN-SERVERS tcp dpt:l2f RETURN udp -- anywhere VPN-SERVERS udp dpt:4500 RETURN tcp -- anywhere VPN-SERVERS tcp dpt:4500 RETURN udp -- anywhere VPN-SERVERS udp dpt:isakmp RETURN tcp -- anywhere VPN-SERVERS tcp dpt:isakmp RETURN all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
I pasted the iptables and they're also at the link but I don't know how to apply them since I don't know the syntax.
VPN Root connects every time, and stays connected.
PhilipTD said:
VPN Root connects every time, and stays connected.
Click to expand...
Click to collapse
Except my connection uses L2TP and there's no apps for that.
Sent from my Nexus 5 using Tapatalk
Hopefully will be fixed on 4.4.3...
The guys at Google are surely taking their time to roll out this fix...
Why couldn't they simply re-issue a patch based on the working code from 4.3?
Right? What the heck....It just baffles me.
eKeith said:
The guys at Google are surely taking their time to roll out this fix...
Why couldn't they simply re-issue a patch based on the working code from 4.3?
Click to expand...
Click to collapse