(this item also posted on PPCGeeks)
I'd like to start by thanking arrrghhh and BoominSVX for running thru some tests to see whether or not I had actually found a working solution.
NOTE: This solution requires altering a configuration file. How you alter the file is entirely up to you (vi, desktop utilizing adb, telekinesis, etc.).
I recommend backing up any file that you plan to edit or replace prior to mucking about with it.
WARNING: Instructions will tell you to turn off or restart Wi-Fi.
This is to ensure that the changes you have made to your configuration files are reloaded by wpa_supplicant.
Simply changing the configuration file is not sufficient!
In addition, I am not responsible for any damage that these instructions may cause to your device, your data, and/or your well-being.
PERFORM THESE ACTIONS AT YOUR RISK
The following instructions will take you through the 'long' method:
Connecting to WEP-enabled Wi-Fi (Easy/Standard)
Go to Settings->Wireless & Networks -> Wi-Fi settings
Turn on Wi-Fi if it is not enabled
Setup your Wi-Fi connection
If your AP shows up in the list, select it and type in your WEP key
If your AP does not show up, use the Add Wi-Fi network. On the popup, type your SSID, select 'WEP' for Security, and type your WEP key in the Password.
NOTE: At this point, the Wi-Fi status will go from "Scanning..." to "Connecting..." to "Disconnected"
Turn Off Wi-Fi
Backup the following file: /data/misc/wifi/wpa_supplicant.conf
The file contents should be similar to this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
The priority=1 may or may not be present, based on whether you selected from the scan list, or added it manually.
Edit /data/misc/wifi/wpa_supplicant.conf and remove either OPEN or SHARED from the auth_alg line. Which one depends on whether the access point is using OPEN, SHARED (if it's using both you can choose which one you prefer to use)
After editing, OPEN will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN
wep_key0=YOURWEPKEYHERE
priority=1
}
After editing, SHARED will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
Go to Settings->Wireless & Networks and turn on Wi-Fi.
Your Wi-Fi status should now show the following values:
"Scanning..."
"Connecting..."
"Obtaining an IP address YOURSSIDHERE..."
"Connected to YOURSSIDHERE"
NOTE: If you fail to connect, return to step 4 and try using the other auth_alg value.
Some routers may be configured to only support one authentication mode.
That's the long method - for people who have never connected to a Wi-Fi connection, or don't mind losing saved APs can do the following
Connecting to WEP-enabled Wi-Fi (Advanced)
Create your own wpa_supplicant.conf file, either by hand, using the above code snippets, or one of the template files in the zip
Replace YOURSSIDHERE with the value of your ssid.
Replace YOURWEPKEYHERE with the value of your WEP key.
Place your edited wpa_supplicant.conf file in the /data/misc/wifi directory on your device
Restart/Turn on Wi-Fi
This method has been tested using FRX04 system image, with both Stock and F22's updated rootfs.img file, and against both FRX04 shipped and WisTilt2's debug kernels.
Feel free to share your success and/or failure stories in this thread.
lol, thanks for this. Now I just need to figure out how to communicate with my device using telekinesis....
I don't use WEP, but the masses that seemingly need it will love you for this. Still not sure how we're going to commit it .
Great work, thanks a lot!
So if I'm understanding this right, this modification is specific to an individual WEP access point, and has to be made once for each new WEP access point you come across? I wonder where we could make a change so that XDAndroid will make this change automatically.
I was trying to get WEP working earlier too, and I noticed that by using a different wpa_supplicant (not conf) file, I was able to connect to WEP access point and send and receive data, but for some reason DNS just wouldn't work.
manekineko said:
Great work, thanks a lot!
So if I'm understanding this right, this modification is specific to an individual WEP access point, and has to be made once for each new WEP access point you come across? I wonder where we could make a change so that XDAndroid will make this change automatically.
I was trying to get WEP working earlier too, and I noticed that by using a different wpa_supplicant (not conf) file, I was able to connect to WEP access point and send and receive data, but for some reason DNS just wouldn't work.
Click to expand...
Click to collapse
You are correct - the configuration is handled on a per-network basis. Remembered networks will be stored in that file, so a wpa_supplicant.conf can contain multiple network={ ... } structures, and each structure could contain an auth_alg line.
I don't know the status of other devices, and forcing it to write a specific value might break ones that are currently working.
There is speculation that a newer version of wpa_supplicant (we're running 0.5.x as is my understanding) may be able to handle the conf file the way it is currently written. The fact that a you used a different version and were able to connect would tend to confirm that.
Do you happen to know what version of wpa_supplicant you were using when it did connect?
Pohket said:
You are correct - the configuration is handled on a per-network basis. Remembered networks will be stored in that file, so a wpa_supplicant.conf can contain multiple network={ ... } structures, and each structure could contain an auth_alg line.
I don't know the status of other devices, and forcing it to write a specific value might break ones that are currently working.
There is speculation that a newer version of wpa_supplicant (we're running 0.5.x as is my understanding) may be able to handle the conf file the way it is currently written. The fact that a you used a different version and were able to connect would tend to confirm that.
Do you happen to know what version of wpa_supplicant you were using when it did connect?
Click to expand...
Click to collapse
Here's my post on it:
http://forum.xda-developers.com/showthread.php?p=11016773
I believe this was using wpa_supplicant v0.5.11.
Hehehehe, WEP works. Thanks for the tip.
this is bigger for me than gettin the cam working.
thx
its great but sorry i dont know how to mount it and where plz help ?? thanks in advance
wifi-ace
I'm using wifi-ace (android market or here: code.google.com/p/android-wifi-ace/) and wep is working fine.
Found it during my search for the hidden network problem.
You are able to adjust everything with this app.
So you don't need to change the "wpa_supplicant.conf", the app
does it for you.
My hidden network at home is working fine now
ohh i dont know how to use this program plzz anyone tell me how to mount this ???
ammmma2 said:
ohh i dont know how to use this program plzz anyone tell me how to mount this ???
Click to expand...
Click to collapse
Download it from the Market.
NO WIFI
Pohket said:
(this item also posted on PPCGeeks)
I'd like to start by thanking arrrghhh and BoominSVX for running thru some tests to see whether or not I had actually found a working solution.
NOTE: This solution requires altering a configuration file. How you alter the file is entirely up to you (vi, desktop utilizing adb, telekinesis, etc.).
I recommend backing up any file that you plan to edit or replace prior to mucking about with it.
WARNING: Instructions will tell you to turn off or restart Wi-Fi.
This is to ensure that the changes you have made to your configuration files are reloaded by wpa_supplicant.
Simply changing the configuration file is not sufficient!
In addition, I am not responsible for any damage that these instructions may cause to your device, your data, and/or your well-being.
PERFORM THESE ACTIONS AT YOUR RISK
The following instructions will take you through the 'long' method:
Connecting to WEP-enabled Wi-Fi (Easy/Standard)
Go to Settings->Wireless & Networks -> Wi-Fi settings
Turn on Wi-Fi if it is not enabled
Setup your Wi-Fi connection
If your AP shows up in the list, select it and type in your WEP key
If your AP does not show up, use the Add Wi-Fi network. On the popup, type your SSID, select 'WEP' for Security, and type your WEP key in the Password.
NOTE: At this point, the Wi-Fi status will go from "Scanning..." to "Connecting..." to "Disconnected"
Turn Off Wi-Fi
Backup the following file: /data/misc/wifi/wpa_supplicant.conf
The file contents should be similar to this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
The priority=1 may or may not be present, based on whether you selected from the scan list, or added it manually.
Edit /data/misc/wifi/wpa_supplicant.conf and remove either OPEN or SHARED from the auth_alg line. Which one depends on whether the access point is using OPEN, SHARED (if it's using both you can choose which one you prefer to use)
After editing, OPEN will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN
wep_key0=YOURWEPKEYHERE
priority=1
}
After editing, SHARED will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
Go to Settings->Wireless & Networks and turn on Wi-Fi.
Your Wi-Fi status should now show the following values:
"Scanning..."
"Connecting..."
"Obtaining an IP address YOURSSIDHERE..."
"Connected to YOURSSIDHERE"
NOTE: If you fail to connect, return to step 4 and try using the other auth_alg value.
Some routers may be configured to only support one authentication mode.
That's the long method - for people who have never connected to a Wi-Fi connection, or don't mind losing saved APs can do the following
Connecting to WEP-enabled Wi-Fi (Advanced)
Create your own wpa_supplicant.conf file, either by hand, using the above code snippets, or one of the template files in the zip
Replace YOURSSIDHERE with the value of your ssid.
Replace YOURWEPKEYHERE with the value of your WEP key.
Place your edited wpa_supplicant.conf file in the /data/misc/wifi directory on your device
Restart/Turn on Wi-Fi
This method has been tested using FRX04 system image, with both Stock and F22's updated rootfs.img file, and against both FRX04 shipped and WisTilt2's debug kernels.
Feel free to share your success and/or failure stories in this thread.
Click to expand...
Click to collapse
I do not understand how do I get to this file? I tried to use wifiace and terminal emulator but still no connection only scan, connect, and disconnect. I put my ssid and password in correctly but it still shows the lock symbol and also I can put any number in and it doesn't change just remembered, secured with wep! Any help and I really don't understand the Android SDK usage! thanks again!
SteelLife said:
I do not understand how do I get to this file? I tried to use wifiace and terminal emulator but still no connection only scan, connect, and disconnect. I put my ssid and password in correctly but it still shows the lock symbol and also I can put any number in and it doesn't change just remembered, secured with wep! Any help and I really don't understand the Android SDK usage! thanks again!
Click to expand...
Click to collapse
If you have any choice in the matter, please, please use WPA, or better yet WPA2 with AES.
WEP is ridiculously insecure, and only slightly better than running a completely open network.
If it's not your AP, and you have no choice... wifi-ace works great. Much easier than this method, although this method does work.
With previous experience in network security, a WEP key can be broken in as little as 2-5 Minutes. 30 Minutes with no prior knowledge and just following a guide.
For security sake, use WPA or WPA2 with either encryption, they are equally difficult to break the key.
Cracking a WEP key is as simple as collecting enough unique IVs and running it against a cracking tool.
Cracking a WPA/WPA2 key is not so simple, you need a handshake packet, then you need to run the handshake packet against a dictionary attack (that can last 30 minutes with a big dictionary on a good computer) until you find the word, if it is not in the dictionary it will have to be brute-forced requiring 7392 days on a very very good computer for a key that is 8 random characters. Hackers purely wont waste their time.
WPA/WPA2 is safe, for now. Use that.
arrrghhh said:
If you have any choice in the matter, please, please use WPA, or better yet WPA2 with AES.
WEP is ridiculously insecure, and only slightly better than running a completely open network.
If it's not your AP, and you have no choice... wifi-ace works great. Much easier than this method, although this method does work.
Click to expand...
Click to collapse
I have no choice! I tried the wifi-ace but it only scan connect disconnect. I don't know! Is there away to erased my SSID so I can start over!
Finallly online!
Ok, Im online had to put password in one of the key management thru wifi-ace!
thanks all!
SteelLife said:
I have no choice! I tried the wifi-ace but it only scan connect disconnect. I don't know! Is there away to erased my SSID so I can start over!
Click to expand...
Click to collapse
Do you not own the WAP? You should get rid of WEP at all costs.
arrrghhh said:
Do you not own the WAP? You should get rid of WEP at all costs.
Click to expand...
Click to collapse
Building share and want to stay on wep for whatever reason I don't know!
SteelLife said:
Building share and want to stay on wep for whatever reason I don't know!
Click to expand...
Click to collapse
Tell them anybody with a laptop and basic knowledge can hack into it no prob. Then not only could they potentially steal your internets, they could also easily get into your machines, as the intruder is now on your LAN.
Meh, do what you gotta do. Just be wary of the consequences for choosing poor security methods.
arrrghhh said:
Tell them anybody with a laptop and basic knowledge can hack into it no prob. Then not only could they potentially steal your internets, they could also easily get into your machines, as the intruder is now on your LAN.
Meh, do what you gotta do. Just be wary of the consequences for choosing poor security methods.
Click to expand...
Click to collapse
I know have been telling them for 6 months to change too no prevail!
First of all, i would like to say hello guys and thanks to every developer in here.
I'm trying to change my x10 (FreeX10 from here) mac address, but i've tried a lot of commands like:
ip link wlan0 set address xx:xx:...
most of them just returns me invalid operation or siocsifhwaddr error
i've tried the app Set Mac Address with no luck.
Tried to find the /etc/wl/nvram.txt there is no file in there.
Tried to look for a file with any WL inside, most of them seems code not configuration.
Have someone already been able to change this?
I need this because in my work everyone can have only on mac address signed to, so if i want to use wifi i need to set every thing to the same mac address.
Sorry my bad english.
Thanks in advance
Ruan
Maybe you will find something useful here!
G-FACE said:
Maybe you will find something useful (Couldn't post the link because of forum rules blocking me)
Click to expand...
Click to collapse
It may be because of my lack of knowledge on linux system, but i couldn't understand most of the commands in there, tried to reproduce but i got nothing.
Does anyone knows any step by step for x10 using terminal commands if possible to do this?
hi to all, i'm a newbie on this forum, and i know this may not be the right place for this 3d, but i don't have enogh messages to write on developer topic.
I've a strange behaviour on my galaxy S advance.
I've installed Harhjely 3.2 with cocore 8.2 and CWM, with HJ 3.0 all works fine, i've upgraded to 3.2 but tethering is not more working.
Doesn't work neither wi-fi and bluetooth tethering.
I found the problem but i don't know how to fix it.
essentially the problem is on the dhcp server,
I'm able to see wi-fi connection from different devices to my phone, i can see on the tethering table the mac address of my pc and the ip address reserved to it, but the pc doesn't acquire the address and after a lttle it assigns itself an ip from PIPA netwoek (169.254.0.0/16 ) and so is not able to use the phone to go to internet.
I tried different devices (many laptop with different OS, tablet and others phones), but no luck, dhcp server is not working properly.
Any idea how to fix it ?
still not working
i tried to update to 4.0 version of harshjelly, but no luck, tethering is still not working.
i put here a log taken with logextreme during tethering process (device is able to connect, phone seems able to give it an ip address, but no one ip address is released), so please if any of you is able to give me an hand i'll be extremely gratefull.
Tethering is crucial for me, if i'm not able to make it working, i need to revert to stock image that i hate, but tethering works...
Please help me:
many thanks
kasparh said:
i tried to update to 4.0 version of harshjelly, but no luck, tethering is still not working.
i put here a log taken with logextreme during tethering process (device is able to connect, phone seems able to give it an ip address, but no one ip address is released), so please if any of you is able to give me an hand i'll be extremely gratefull.
Tethering is crucial for me, if i'm not able to make it working, i need to revert to stock image that i hate, but tethering works...
Please help me:
many thanks
Click to expand...
Click to collapse
ok, i solved the issue, i flashed from scratch and re-installed, now all works like a charm.
thanks for the help
Before I upgraded to Android 8 or 9 I was able to edit a file
p2p_suplicant.conf to change Wifi Direct name and passwords.
That's not the case on Android 9.
Where can I change these values?
I am running Android 10 on GP 3aXL. I have two Devices A and B connected via Wi-Fi direct. On device A, i have a proxy server running. I want to share my internet connection with device B. When i scan wifi on device B, I see SSID with the name of the remembered group on device A. I try to connect and it is asking me for the password. Where is this password info located? Tx.
m4f1050 said:
Before I upgraded to Android 8 or 9 I was able to edit a file
p2p_suplicant.conf to change Wifi Direct name and passwords.
That's not the case on Android 9.
Where can I change these values?
Click to expand...
Click to collapse
How?? What do you have to change in p2p_supplicant.conf to change Wifi direct username and password?
I'm trying to tether wifi using wifi direct, I looked into this 2 yrs back, did everything I could to change pass so that, I get a fixed pass everytime, not a randomly generated one, but I couldn't get anything to work, I thought it's not possible and gave up
You're saying you've done that, I really want to know