hfam Posted May 26, 2014 Share Posted May 26, 2014 (edited) (updates at bottom of page, the summary is that 1.4.1 broke Client Mode for me using the native radios of the MKV, read on...) Alright, I need some assistance please.......losing....mind....rapidly... I have 2 MKV's, just updated them to 1.4.1 (from 1.3.0), and use them both in Client Mode often without connecting to a laptop (though I only updated to 1.3.0, didn't have a chance to actually use 1.3.0). It's always been a matter of simply connecting to Wlan0 with android/tablet/etc, opening admin page, enabling Wlan1 from the Network GUI, then going into the Network tile/Client Mode, and connecting it to the Internet-enabled WiFi of my choosing by selecting the AP and providing creds. When I'd do this, the Red LED would come on once connected in Client Mode, and things would work fine..Administratively connect to (or Karma hooks 'em) on Wlan0, connects them to the Internet on Wlan1 when needed. For the life of me i can't get client mode to work anymore and I'm out of gas. I have tried this both connected to the laptop via eth, and from an android with same luck. - I can enable/disable Wlan1 from the Network Tile - Network Info/ifconfig shows both interfaces are UP. When I disable Wlan1, it reflects that in ifconfig - There is NO Red LED. Never comes on or off. - When I select Wlan1 (only selection available) in Client Mode and scan for available APs, Wlan1 is always available, whether or not it's enabled, and it will always perform a scan and return available APs. - I get the connecting graphic, then get green text "connection initiated", but again, no Red LED, no connectivity, etc. - When it is making the connection in Client Mode, the Blue LED goes out for ~2 seconds, then returns. This is the point when the Red LED used to come on. - This is happening on both my 1.4.1 MKVs, same behavior on both of them after 1.4.1 Since the 1.4.1 update it now behaves as if Wlan0 and Wlan1 are the same radio, HOWEVER, in ifconfig, it shows that Wlan0 and Wlan1 have different MAC addrs, so that doesn't make sense either, can't be both ways. Please tell me, what the hell am I missing here? Thanks for any help gang, I'm !#%#%@ stumped! hfam *** Update 1: Performed an unbricking on one of my MKVs to bring it back to 1.2.0. Client Mode is working as it should be, exactly as I described it to work above. I also formatted the SD card, though prior to the "unbricking" I swapped the SD cards in each MKV and confirmed both are good. I formatted it anyhow to ensure it was a brand new clean install. There are currently no infusions installed, it's fresh and clean 1.2.0, Client Mode works perfect. About to update to 1.4.1, fingers crossed... *** Update 2: successful update to 1.4.1 aaaaand it's broken in exactly the same way. Either there is something additional that must be done, that wasn't required prior, for Client Mode to work with the built-in radios of the MKV, or 1.4.1 appears to have broken Client Mode with the built-in radio that normally is Wlan1. Any help would be greatly appreciated!! Edited May 26, 2014 by hfam Quote Link to comment Share on other sites More sharing options...
hfam Posted May 27, 2014 Author Share Posted May 27, 2014 Anyone? Can someone confirm/deny my findings above using 1.4.1 and the stock MKV radios? I'm stuck. Flash the device back to 1.2.0 and Client Mode works fine, I can connect WLAN1 to my WiFi, red LED lights up, traffic is passed via BRLAN between WLAN0 and WLAN1. Update it to 1.4.1 and it will simply not connect WLAN1 to WiFi. Won't even light it up. I've confirmed this on both my MKVs now. It's not hardware, and to be sure it's nothing else I've formatted the SD cards with no infusions. Everything is "factory clean". Flashed back to 1.2.0 = Client Mode works perfect Update that to 1.4.1 = Client mode is broken and will not connect or even light up WLAN1 Can someone please lend a hand? I'm truly stuck. Quote Link to comment Share on other sites More sharing options...
Oli Posted May 27, 2014 Share Posted May 27, 2014 Since the web interface is (ostensibly) open source, we could really do with it under source control so that we can easily see changes between versions and track down the cause of bugs like these... Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted May 27, 2014 Share Posted May 27, 2014 What's the security type of the AP you're testing with? Is it the only AP you've tested? Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted May 27, 2014 Share Posted May 27, 2014 Anyone? Can someone confirm/deny my findings above using 1.4.1 and the stock MKV radios? I'm stuck. Flash the device back to 1.2.0 and Client Mode works fine, I can connect WLAN1 to my WiFi, red LED lights up, traffic is passed via BRLAN between WLAN0 and WLAN1. Update it to 1.4.1 and it will simply not connect WLAN1 to WiFi. Won't even light it up. I've confirmed this on both my MKVs now. It's not hardware, and to be sure it's nothing else I've formatted the SD cards with no infusions. Everything is "factory clean". Flashed back to 1.2.0 = Client Mode works perfect Update that to 1.4.1 = Client mode is broken and will not connect or even light up WLAN1 Can someone please lend a hand? I'm truly stuck. Come by IRC and we'll figure this out. Best Regards, Sebkinne Quote Link to comment Share on other sites More sharing options...
hfam Posted May 27, 2014 Author Share Posted May 27, 2014 Thanks fellas! Hi Darren, It is indeed the only AP I've tested with and it is secured with WPA2. Unfortunately I've been down with a back injury for a few months and will be down for a while longer so I haven't been to work where I have a number of other APs I could test with. However, this AP is always my first stop when testing any of the Pineapples, it's functioning fine, and I have all sorts of devices connecting to it just fine. I'm able to replicate this issue on two MKVs now...reflashed both of 'em to 1.2.0 and they both connect like they should. I left one of the SD cards loaded with the boatload of previous infusions, and I formatted the other, just to see if there would be any differences. Unfortunately that 1.4.1 upgrade blows up Client Mode on both of them regardless. I'd be happy to provide anything you ask for (within reason...the gold coins and swiss bank account aren't happening! :) ) that could help sort this out, but it appears that hardware-wise, 1.4.1 recognizes both radios, I can enable/disable both of them according to ifconfig, and ifconfig reports correctly whether they're up or not. Thanks again for any assistance, I think we've got a bug here based on the process of elimination, but again, anything within my power to help get to the bottom of it I'd be happy to provide. Quote Link to comment Share on other sites More sharing options...
hfam Posted May 27, 2014 Author Share Posted May 27, 2014 Come by IRC and we'll figure this out. Best Regards, Sebkinne Thanks Seb, give me 15 and I'll be right over! hfam Quote Link to comment Share on other sites More sharing options...
hfam Posted May 27, 2014 Author Share Posted May 27, 2014 (edited) Problem SOLVED! God i love you guys so damn much!!! Huge props to seb, and a hearty thanks to all who helped. So, the issue came down to two issues: - the updated realtek drivers as of v. 1.3.0 - My AP and the firmware So, the resolution initially was to just throw an Alfa on it and use Wlan2 for Client Mode, as for whatever reason, the realtek drivers were throwing an error when connecting to my AP (an older WAG 102) using Wlan1. The AP was otherwise working for any and all devices, and would work fine with MKV v.1.2.0 and prior. However, I went further. Initially when you look at the page to download an update firmware for my WAG 102, it shows the version I had installed. But, buried in "more" there were some other very minor updates. I grabbed the latest, and flashed my AP in desperation. And it WORKED!! Suddenly, Client Mode was working like a boss!! So, I guess the takeaway on this (aside from Seb being super helpful!!) is that, in the field, there may be some APs out there that you may not be able to use Client Mode on. Rare it would seem, but who knows as we move forward how many APs are out there that may not be compatible, so be sure to pack an external radio (I used the Alfa 036NHA) to use as Wlan2 if you're going to need to connect to an unknown AP in the field, just in case! Seb also shared with me that Wlan1 wasn't really intended for Client Mode, and more for deauth, etc, but it was included since it worked and got pretty popular (me included!). Based on the data today, i don't expect many instances of failure as mine was, but again, working in the field, it's always good to be prepared, and there are certainly plenty of APs in the field that don't have their firmware updated regularly, so it's a good lesson and reminder anyhow! Man, I love this community so much! Thanks again to Seb and Darren for making all this possible, and to Foxtrot et al for all their help and suggestions! Case closed!! Positive energy to you all! hfam Edited May 27, 2014 by hfam Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.