NC wont connect to WPA-PEAP - Nook Color General

I saw on NookDevs.com about the original nook needing to use ADB to change some files to allow for WPA-PEAP Wifi connections. Would that work the same for the Nook Color?

cventurini said:
I saw on NookDevs.com about the original nook needing to use ADB to change some files to allow for WPA-PEAP Wifi connections. Would that work the same for the Nook Color?
Click to expand...
Click to collapse
So you need 802.1x? Have you tried configuring it as much as you can in the wifi settings, then running this and configuring it the "rest of the way"? I haven't tried it on the NC yet, but it worked on my Nexus One to connect to my work wifi.
http://www.appbrain.com/app/wifi-advanced-config-editor/org.marcus905.wifi.ace

i will download it when i get home im getting blocked at work then i will try it tomorrow

Related

[Q] Tethering and the Droid 1 (using ad_hoc enable wpa supplicant)

So, I've tried using the ad-hoc enabled wpa_supplicant file to allow my NC to see my Droid as a hotspot. My NC can now see my Droid and can attempt to access it (even asking for password), but it fails to connect everytime.
Anyone else successfully tether their NC to a Droid 1?
I use the motorola droid 1 and I connect it using Wireless Tether App. Works fine. Other than the annoying problem that when the nook sleeps it drops the wifi. But that is a known issue.
Hmm, not sure what I've done wrong. I can see the Droid SSID in my list of wireless networks. I can try to connect and get "Obtaining IP address" for about 30 seconds, then see a connect failed message. The logs in Wireless Tether on the Droid indicate successful communication with no indication of failure.
Question to you Lyam23
Hi there. So you successfully added your supplicant file. Did you follow Root Explorer as the way to accomplish this?
I tried it and now there's no Wifi at all. I'm awaiting a reply on the thread for performing the ad-hoc, but replacing and renaming the WPA files did something to mess me up. (I did something to mess me up) ( ;
Resolved : the folder was my fail. Had to rename the wpa folder, then move the adhoc fix version of the file outside of it....direct into bin.
lyam23 said:
So, I've tried using the ad-hoc enabled wpa_supplicant file to allow my NC to see my Droid as a hotspot. My NC can now see my Droid and can attempt to access it (even asking for password), but it fails to connect everytime.
Anyone else successfully tether their NC to a Droid 1?
Click to expand...
Click to collapse
Are you able to tether to a PC? That way we rule out that you can or cannot tether.
Did you set the permissions in the new file correctly?
I successfully tethered a Samsung Fascinate to the NC, two different NC's by the way. Process works.
vlucchetti said:
Are you able to tether to a PC? That way we rule out that you can or cannot tether.
Did you set the permissions in the new file correctly?
I successfully tethered a Samsung Fascinate to the NC, two different NC's by the way. Process works.
Click to expand...
Click to collapse
I was able to tether to a laptop a couple of months ago. I'll try again later today. I've probably changed ROMs on my Droid 1 since then.
Permissions are correct.
I'm sure it does work for everyone except me. That's why I'm frustrated!
EDIT: Must be my Droid. I can no longer connect via laptop.
EIDT2: switched to CM7 and all works now!
Is there a good tutorial for the Root Explorer way of doing this?
I've followed the directions on http://forum.xda-developers.com/showthread.php?t=868354 but for whatever reason, even though I can visually see the files in the right spots, and the commands all run properly, I can't see the Ad Hoc connection from my Droid 1.
mg00000 said:
Hi there. So you successfully added your supplicant file. Did you follow Root Explorer as the way to accomplish this?
I tried it and now there's no Wifi at all. I'm awaiting a reply on the thread for performing the ad-hoc, but replacing and renaming the WPA files did something to mess me up. (I did something to mess me up) ( ;
Resolved : the folder was my fail. Had to rename the wpa folder, then move the adhoc fix version of the file outside of it....direct into bin.
Click to expand...
Click to collapse
I know the OP said their problem was fixed, but I thought I'd still post this.
I found out that some ROM's and/or kernals broke Access Control and disabling it on your droid will allow you to tether again. You can still use security, just not access control.

NC radio card is not working

My Nook color was fine before It was ran out of battery couple days ago. BTW, I'm running CM7.0.3 on my nook color. the problem is, it cant connect with any wifi, it cant scan anything. when i use my phone the connections were all there but apparently my nook color can't recognized them it is just said connecting then after a while disconnecting. The bluetooth also not working. has anyone meet the same issue?
Delete ["forget"] all the saved wifi access points, reboot, and scan again for the access point you're trying to connect to.
Sweet! It is working now.. thanks.

[Q] CM7/Nightly 177 not able to hold EAP WiFi?

Have a unique issue that I wanted to see if anyone else has come across.
I'm running CM7 7.1RC w/ nightly 177 via a SD card. The setup runs fine at home with my WiFi/ WPA-PSK, yet at work I sign in with a 802.1x EAP. I can connect once or twice (once I enter the settings), but after about half a day, it fails to connect and I have to "forget" the network and start over.
So, is there a setting that I'm missing somewhere that will retain a EAP-coded network across a large facility without resetting the security settings every 3-4 hours?
I'm running CM7 7.1RC w/ nightly 177 via a SD card.
Click to expand...
Click to collapse
Can be only one, either 7.1RC or nb177
votinh said:
Can be only one, either 7.1RC or nb177
Click to expand...
Click to collapse
Started with 7.1, then did nb177 via ROM update.
Same problem here. Can't get EAP Wifi to work. It works after setting it up once, but later on, it'll fail to work and requires a reconfiguration to get it working again.
Can you tell me how you did the key management and setup?
I tried to import my desktop cert (wired is EAP, too) but I suspect that I'm not putting it in the right place.
A snapshot from wpa_supplicant.conf (anonymized is fine) and if or how you loaded the cert would be most welcome.
Thanks!
Sent from my NookColor using xda premium
traumadog said:
Have a unique issue that I wanted to see if anyone else has come across.
I'm running CM7 7.1RC w/ nightly 177 via a SD card. The setup runs fine at home with my WiFi/ WPA-PSK, yet at work I sign in with a 802.1x EAP. I can connect once or twice (once I enter the settings), but after about half a day, it fails to connect and I have to "forget" the network and start over.
So, is there a setting that I'm missing somewhere that will retain a EAP-coded network across a large facility without resetting the security settings every 3-4 hours?
Click to expand...
Click to collapse
Did it work before you updated the ROM?
patruns said:
Did it work before you updated the ROM?
Click to expand...
Click to collapse
Sorry for being unclear. No, it has never worked. Corporate doesn't support Android devices, so they won't help. I'm trying use the cert from my Linux desktop setup on my NC. I can generate a different one if that's part of the problem.
On linux, wpa_supplicant.conf has the cert filenames, but that didn't work here. I haven't tried to import it via Settings/Security, I just copied it onto the same directory I store my SSH keys in.
Sent from my NookColor using xda premium
Incidentally, this is a problem for my phone as well. I have to repeatedly reconfigure the wifi to make it work.
hi
had same problem with 177 changed to 176 and had no problems since
Still have yet to get it to work ... though I "borrowed" settings from my phone's WinMo setup (needed phase2 auth setting of MSCHAPV2, plus adding my domain on the "anonymous" ID.)
Updating now to nightly 197... I'll see how it works.
I'm using 197 as of the moment. EAP is not perfect, but it's tolerable. I need to turn WiFi off and on before it'd pick up an IP. Occasionally, not even that works; then I just use Titanium Backup to restore my [working] WiFi configuration, cycle the WiFi, and it would work again.
Having same problem in nigjtly 200 and 202
FWIW - the issue is still hit-or-miss with the newer nightlies. I'm now on 213, and it's not holding a connection consistently.

[Q] nook hd doesnt recognize adhoc network

I have a nook hd 2.0,5 stock rooted with leapinlars method. thanks leapinlar. What my problem is i am creating a adhoc network with my computer since thats all its capable of and want to connect my hd to it but it doesnt recognize it. Theres a thread somewhere on here on how to make nook color work but cant find anything anywhere for the hd. Anyone have any suggestions?

[Q] ad-hoc hack for NOOK HD/HD+ . When ?

Hi everybody.
I would like to know if someone is working on a hack for our NOOKs tablet to access ad-hoc networks. I saw there is some movement on other devices, as android, at least the latest version, does not include support to ad-hoc network. The reasons are obvious, Google team will not implement this in the next version as they are going further to offer mobile services an they would you require that you purchase a new data plan.
So, it is time to have a hack for our android(ed) NOOK devices in order to access ad-hoc networks from our mobile phones.
Does anyone know about a similar movement on NOOK community ?
Regards.
Angelo
I'm not sure what you are trying to accomplish here based on your statement. Ad-hoc networks only allow two individual computers to connect without one being configured as an access point, sort of like bluetooth in terms of functionality. The reason it is unavailable is probably more to do with security as it is a dangerous connection to use or enable. If you are talking about tethering to for instance your phone, that works fine, use it all the time. This doesn't require ad hoc, only a tethering app (e.g. pdanet) or it is built in for many phones.
If you have an old Nokia device, I've noticed that when they tether via JoikuSpot, they create ad-hoc networks. If this is the reason you want ad-hoc networks enabled (to tether), I guess this is a valid reason. To pair two devices together, that may become troublesome (I doubt it'll be working any time soon).
Tethering via ad-hoc is perfectly fine, I'll take a quick look at it for the Nook HD+, and I'll reply back with what I find; hopefully a solution. I'll try and take a look some time this Wednesday or weekend.
I've not fully tested it, but doesn't Cyanogenmod enable ad-hoc networks by default? So, I guess you could go down that route (of course, I do accept that CM10 isn't for everyone).
P.S. If I do, or anyone else enables ad-hoc networks on the Stock ROM, you'll need to be rooted, and with CWM (since you'll need to apply a .zip) to hopefully enable ad-hoc networks.
All the best.
HiddenG said:
If you have an old Nokia device, I've noticed that when they tether via c, they create ad-hoc networks. If this is the reason you want ad-hoc networks enabled (to tether), I guess this is a valid reason. To pair two devices together, that may become troublesome (I doubt it'll be working any time soon).
Tethering via ad-hoc is perfectly fine, I'll take a quick look at it for the Nook HD+, and I'll reply back with what I find; hopefully a solution. I'll try and take a look some time this Wednesday or weekend.
I've not fully tested it, but doesn't Cyanogenmod enable ad-hoc networks by default? So, I guess you could go down that route (of course, I do accept that CM10 isn't for everyone).
P.S. If I do, or anyone else enables ad-hoc networks on the Stock ROM, you'll need to be rooted, and with CWM (since you'll need to apply a .zip) to hopefully enable ad-hoc networks.
All the best.
Click to expand...
Click to collapse
Yes, you are 100% correct. I do have a Nokia and Joikuspot.
The other problem is that I am a complete newbie to android, cyanogenmod etc.
I have rooted my Nook HD, but I dont know if it is using cyanogenmod. I just purchased a microSD card that rooted and installed gapps..
Thank you for your help....
Rooting stock does not add CyanogenMod. You must install that separately by installing it to a bootable SD.
Sent from my Nook HD+ running CM10 on Hybrid SD
I looked around and didn't see ad hoc in my CM10, and there's this: http://forum.cyanogenmod.org/topic/62183-ad-hoc-was-disabled-in-cyanogenmod-10/ Apparently CM has followed google here.
Maybe this can help:
http://forum.xda-developers.com/showthread.php?t=872521
It seems that for NooK Color, this is already done.
AngeloGomes said:
Maybe this can help:
http://forum.xda-developers.com/showthread.php?t=872521
It seems that for NooK Color, this is already done.
Click to expand...
Click to collapse
It does not help on HD+ (included wpa_supplicant binary complains in logs that it does not support wi-fi n spec).So wi-fi does not work at all on Nook HD+ with this hack.
We need a newer patched wpa_supplicant (that supports ad hoc and wifi mode n). Hacked version for any recent android device should go. I'm going to try that http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/ once have a spare time.
I was talking about the idea of that topic.
But I think you got it.
About to have support to wifi n: I suppose that wifi g support is enough, right ?
AngeloGomes said:
I was talking about the idea of that topic.
But I think you got it.
About to have support to wifi n: I suppose that wifi g support is enough, right ?
Click to expand...
Click to collapse
It would be enough, but supplicant fails to start
I've dedicated some time to study this problem. Here is the result:
Dmitriusan said:
Is there any chance the rom will include the ad-hoc patch? Or maybe there is anybody with configured build environment who can recompile wpa_supplicant binary?
The most recent patch version I've found is http://www.verydemo.com/demo_c131_i18097.html
Old patch discussion http://forum.xda-developers.com/showthread.php?t=754961 and the old patch itself http://szym.net/android/wpa_supplicant-ibss.patch
I've tried downloading few patched wpa_supplicant binaries for another devices, but they all use another wi-fi drivers. Nook HD+ has wl1271l chip and uses wl12xx driver.
Many people seem to use Joikuspot to share GPRS/EDGE/3G to another devices via wifi (mobile ad-hoc spot), but Android does not see any adhoc network and it's really annoying...
EDIT:
Or at least maybe anybody has compiled tun.ko module for the latest kernel? I'm trying to get BlueVPN working (to connect my N78 phone as Dial-up Networking device via bluetooth)
UPD
Finally got Internet tethering working with N78. The tun module is present, but for some reason not autoloaded at startup. So, I performed
$ su
# modprobe tun
and managed to connect via BlueVPN to N78 (EDGE). The name of program is a bit misleading, it just connects to phone with BlueDUN installed or to any (?) cell phone that can work as bluetooth modem. I'm using the second option.
Click to expand...
Click to collapse
Joikuspot is told to discharge Nokia device in ~40 minutes of active usage. So tethering over bluetooth seems to me not only the only available, but also the prefered solution. Almost any phone with bluetooth should feet this purpose.
So, here is the final procedure:
- You need the rooted firmware with any terminal emulator (I use CM10 and build-in Terminal Emulator)
- Install BlueVPN
- pair your devices over bluetooth (may need to repeat pairing from scratch after installing BlueVPN)
- Start terminal emulator and type
su
- type
modprobe tun
- no output is okey. If you get the module not found error, I have bad news to you You need the tun.ko kernel module built exactly for your ROM. But at verygreen CM10 firmware tun.ko is present.
- disable wifi
- Start BlueVPN. Go to the settings and configure you connection options (I've enabled auto-resume and lcp compatibility, yo may need to play with another options to may things work) and GPRS settings (may be found at mobile provider web-site. At least Phone number, Access point need to be configured, in my case I've also set an Authentification to none)
- press back. On your screen you should see the paired device name. Click on it (probably at the button on the right)
- If confirmation appears, say "trust"
- If the text "BluVPN is connected with ..." is displayed on the bottom of your screen, congratulations: you are connected. Otherwise wait for some time and try selecting your device in a list again. Maybe you will have to play with settings / reboot and repeat the whole procedure/reboot your cell phone.
In my case, it takes 1-2 tries to connect, but connection seems to be stable. Don't forget that bluetooth distance is limited
Few notes: you have to run commands su/modprobe tun after every reboot.

Categories

Resources