Hi every body
I have rooted my note 3 n900 , but I still can't view the wifi passwords that stored in the device .
This what I have :
ctrl_interface=wlan0
update_config=1
device_name=ha3gxx
manufacturer=samsung
model_name=SM-N900
model_number=SM-N900
serial_number=4d00c01646b88081
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=124
p2p_oper_channel=149
okc=1
ss_enc=1
autoscan=exponential:8:128
cred={
imsi="41503-"
}
network={
ssid="happybirds"
psk=86a7e933f7c97d0f40b9be1ea61432f3
key_mgmt=WPA-PSK
priority=29
frequency=2412
autojoin=1
}
As you notice the psk= numbers and letters
How can I solve this ..??
Thank you in advanced
Hi!
I encountered the same thing. The psk key seems to be encrypted. Interestingly on my note 2 with 4.2.2 the wpa_supplicant.conf is unencrypted. Either this is a "feature" of 4.3 or, what I tend to think, it's samsung specific. The whole thing idea behind Knox is to "increase" security for company usage. So an unencrypted psk might seem to be a bad idea for samsung. I'm gonna flash my note 2 with a modified 4.3 original ROM and gonna take a look into the conf then if it is also encrypted then.
Did you notice the "ss_enc=1" line? Maybe this toggles the encryption. There seem to exist a system function with that name to encrypt addresses with a specified key. Gonna try to switch it off with "ss_enc=0" and see what happens.
Can anyone share some deeper insights in this issue?
---------- Post added at 06:14 PM ---------- Previous post was at 06:02 PM ----------
Ok, no use toggling 0. It was right reactivated after a reboot. Would have been to easy otherwise. Maybe thw behaviour is toggled somewhere in another conf, but my guess it is "hardcoded" somewhere. What a pity.
I don't see how not viewing stored Wi-Fi passwords is an issue. You should know the password already if it's your Wi-Fi. If you forgot it, you can access it via the Wi-Fi router, or reset it. If your companies tech support input it for you, they can input it again. Can you give me some insight as to why you need to retrieve already stored passwords?
440bro said:
I don't see how not viewing stored Wi-Fi passwords is an issue. You should know the password already if it's your Wi-Fi. If you forgot it, you can access it via the Wi-Fi router, or reset it. If your companies tech support input it for you, they can input it again. Can you give me some insight as to why you need to retrieve already stored passwords?
Click to expand...
Click to collapse
There are quite some reasons:
- Not keeping a second list for the passwords of all the networks stored in your device. Am I the only one who has 20+ networks stored?
- Many ppl think there is no way of retrieving the psk from the device once stored, like many years ago in Windows XP
- Because it should pe possible; no other linux distribution of my knowledge does it; so why is it done and how is it done?
- security by obscurity is a bad thing.
Quetsch said:
There are quite some reasons:
- Not keeping a second list for the passwords of all the networks stored in your device. Am I the only one who has 20+ networks stored?
- Many ppl think there is no way of retrieving the psk from the device once stored, like many years ago in Windows XP
- Because it should pe possible; no other linux distribution of my knowledge does it; so why is it done and how is it done?
- security by obscurity is a bad thing.
Click to expand...
Click to collapse
In my opinion "Because I have 20+" isn't a valid reason to retrieve wifi passwords. I still wait for a valid one.
You can obtain stored wifi passwords very easily from a rooted device! The only thing is you need to decode them. So even after you retrieve them it's still a P.I.A.! It would be much easier to create a list of 20+ ssid's and passwords and email them to yourself. Or keep an excel file of them on dropbox. It's a pain because once we enter our password into our phone it's encrypted. Most people use WPA-PSK encryption. I don't have a secret decoder ring for this. Do you? If so tell me what the password to my wifi with an ssid of Not_Yours_5G is. My wifi password will tell you how to retrieve wifi passwords from a rooted note 3. The information I pulled from my note 3 is below.
ctrl_interface=wlan0
update_config=1
device_name=hlteuc
manufacturer=samsung
model_name=SAMSUNG-SM-N900A
model_number=SAMSUNG-SM-N900A
serial_number=████████
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=124
p2p_oper_channel=149
okc=1
ss_enc=1
autoscan=exponential:8:128
cred={
imsi="310410-"
}
network={
ssid="attwifi"
key_mgmt=NONE
priority=3
frequency=2462
autojoin=1
vendor_spec_ssid=1
}
network={
ssid="Not_Yours-5G"
psk=ecf55efba6a17197586f8577509a018dc7bee71883c82fde8b8557038cb1aae6
key_mgmt=WPA-PSK
priority=6
frequency=5805
autojoin=1
I have the same problem..
how do we decrypt the psk ???
e2luispa said:
I have the same problem..
how do we decrypt the psk ???
Click to expand...
Click to collapse
Same here can see the password on my old Note 2 but not on Note 3.
I got same problem also
my note 3 has X-Note 18.0 on it (4.4.2)
Any one managed to decode wifi passwords ???
Hi, still no one knows hot to decrypt this psk passwords ?
Related
Just leaving this question here in the event someone finds a solution some day. I see no way to configure my Android Wear for WiFi sync on a corporate network secured with 802.1x EAP/PEAP. My phone is connected just fine, but the watch can't do it - there's no option for providing an identity and password. Any clues would be welcome.
jimbobtexas said:
Just leaving this question here in the event someone finds a solution some day. I see no way to configure my Android Wear for WiFi sync on a corporate network secured with 802.1x EAP/PEAP. My phone is connected just fine, but the watch can't do it - there's no option for providing an identity and password. Any clues would be welcome.
Click to expand...
Click to collapse
My watch doesn't even show me the EAP/PEAP wifi networks in the list of APs but...
In theory, you might be able to download /system/etc/wifi/wpa_supplicant.conf from your phone and upload it to your watch using adb. You'll need either to have root access on phone and watch or you can boot into TWRP recovery on phone and watch to grab and then upload that file.
You can also sideload ES filemanager and keyboard program into your watch. ES has a wifi gui to manage wifi, so you can enter password from there.
aligatro2010 said:
My watch doesn't even show me the EAP/PEAP wifi networks in the list of APs but...
In theory, you might be able to download /system/etc/wifi/wpa_supplicant.conf from your phone and upload it to your watch using adb. You'll need either to have root access on phone and watch or you can boot into TWRP recovery on phone and watch to grab and then upload that file.
You can also sideload ES filemanager and keyboard program into your watch. ES has a wifi gui to manage wifi, so you can enter password from there.
Click to expand...
Click to collapse
Both good ideas, thanks. My wpa_supplicant on the phone looks like this:
Code:
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
and the watch:
Code:
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
pmf=0
Not too exciting, if you ask me... I guess I could remove the turn off WiFi, remove the PMF line, reboot, and see what happens...
...nothing. I should point out that my phone "knows" the network and is attached. It shows up in the list of Saved Networks on my watch, too. It just won't connect.
jimbobtexas said:
Both good ideas, thanks. My wpa_supplicant on the phone looks like this:
Code:
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
and the watch:
Code:
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
pmf=0
Not too exciting, if you ask me... I guess I could remove the turn off WiFi, remove the PMF line, reboot, and see what happens...
...nothing. I should point out that my phone "knows" the network and is attached. It shows up in the list of Saved Networks on my watch, too. It just won't connect.
Click to expand...
Click to collapse
Sorry that was a wrong path on the wrong partition. Its located here: /data/misc/wifi/wpa_supplicant.conf
aligatro2010 said:
Sorry that was a wrong path on the wrong partition. Its located here: /data/misc/wifi/wpa_supplicant.conf
Click to expand...
Click to collapse
Yeah - that's WAY different. LOL.
I added the network entry for the corp ssid, turned off WiFi on the watch, replaced the .conf file on the watch, and rebooted the watch. That network no longer shows up on the watch as a remembered network, nor does it connect, dagnabbit. Here's an edited version of that entry:
Code:
network={
ssid="XYZ
key_mgmt=FT-EAP
eap=PEAP
identity="me"
password=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
priority=13
frequency=5805
proactive_key_caching=1
autojoin=1
usable_internet=0
skip_internet_check=0
}
This entry works on my phone.
jimbobtexas said:
Yeah - that's WAY different. LOL.
I added the network entry for the corp ssid, turned off WiFi on the watch, replaced the .conf file on the watch, and rebooted the watch. That network no longer shows up on the watch as a remembered network, nor does it connect, dagnabbit. Here's an edited version of that entry:
Code:
network={
ssid="XYZ
key_mgmt=FT-EAP
eap=PEAP
identity="me"
password=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
priority=13
frequency=5805
proactive_key_caching=1
autojoin=1
usable_internet=0
skip_internet_check=0
}
This entry works on my phone.
Click to expand...
Click to collapse
Then it must be hardcoded to ignore PEAP networks. Or maybe there is a config file that has a switch for this. I know the build.prop file has a parameter for unlocking extra wifi channels, but not sure if it has anything else related to wifi though.
Hello dear fellows.
I've updated my S2 LTE today through OTA from version 5.0.2 to version 6.0.1.
While in 5.0.2, I contacted Samsung about a procedure to make the S2 to forget obsolete networks, since the usual method does not work, because networks not in range are not shown!
Except for another guy asking the same question (somewhere), I didn't found anything in the net about this issue, I don't know if people already realized the problem... (seems all people is quite busy getting root and/or the new firmware).
So, Samsung told me the feature is not available, that I should backup with Kies and do a factory reset! UNACCEPTABLE!!!
I wait for the 6.0.1 hopping that the problem was solved in this version, but NOOO, they MEAN it. IT IS NOT available!
So...
- Does anyone one of you manage to find a way to make the S2 to forget / delete old unused networks?
- Does anyone find acceptable the actual status quo of the problem?
- Is there someone with a reasonable explanation for this feature being removed from S2 firmware? (At least some explanation I can swallow)?
Thank you all.
I think it's just sloppy thinking from the developers. Of course one should be able to get a list of known/saved WiFi networks and delete from the list accordingly. I can do it on my Nexus 6P running N preview 3. Maybe this app can be used to achieve this: https://play.google.com/store/apps/details?id=com.mdroidapps.wifimanager
One should also be able to see the password for saved WiFi networks without having to be rooted. Yes, it's a security risk but Windows and Linux let you see the password in clear text.
Android still have a bit of maturing to do.
And while we're at it - what I really want is being able to change DNS servers while on mobile data. When limited to your carriers DNS servers you are unable to connect to DNS blocked sites like in example some torrent sites. I would like to set my DNS to my Raspberry Pi running pi-hole and get DNS adblock even though I'm on mobile data. But this is only possible using a VPN app.
Sendt fra min SM-T815 med Tapatalk
LosserKlosser said:
I think it's just sloppy thinking from the developers. Of course one should be able to get a list of known/saved WiFi networks and delete from the list accordingly. I can do it on my Nexus 6P running N preview 3. Maybe this app can be used to achieve this: https://play.google.com/store/apps/details?id=com.mdroidapps.wifimanager
One should also be able to see the password for saved WiFi networks without having to be rooted. Yes, it's a security risk but Windows and Linux let you see the password in clear text.
Android still have a bit of maturing to do.
And while we're at it - what I really want is being able to change DNS servers while on mobile data. When limited to your carriers DNS servers you are unable to connect to DNS blocked sites like in example some torrent sites. I would like to set my DNS to my Raspberry Pi running pi-hole and get DNS adblock even though I'm on mobile data. But this is only possible using a VPN app.
Sendt fra min SM-T815 med Tapatalk
Click to expand...
Click to collapse
Thank you for the reply.
I've tested the app "wifi manager". It did not work as expected!
- The app indeed show the list of all networks even the ones not in range / obsolete.
- The app indeed allow the 'forget' procedure.
I use then the 'forget' procedure in a old network. The app says "wait....", but after that, the old network is still showing in the list no matter how many times you apply the procedure, no matter if you close and reenter the app. That means, the app is useless for the purpose to delete old networks, at least in the Tab S2 device.
I don't know it this issue is just a developer's sloppy thinking, or if this is Samsung stink over all of us. I think it is the later...
Sorry I do not know any way to change connection DNS the way you need, or any other way for that matter.
Still looking.
LosserKlosser said:
And while we're at it - what I really want is being able to change DNS servers while on mobile data. When limited to your carriers DNS servers you are unable to connect to DNS blocked sites like in example some torrent sites. I would like to set my DNS to my Raspberry Pi running pi-hole and get DNS adblock even though I'm on mobile data. But this is only possible using a VPN app.
Sendt fra min SM-T815 med Tapatalk
Click to expand...
Click to collapse
Touch VPN will bypass those blocks.
Hello everyone! Good day!
Does anyone know if this feature is implemented in the Note 9? I could not find the setting in Developer Options but Android Documentation says its available in Android Pie.
Thanks
Google say it is inbuilt with no need for a on/off switch
https://support.google.com/fi/thread/293417?hl=en
raul6 said:
Google say it is inbuilt with no need for a on/off switch
https://support.google.com/fi/thread/293417?hl=en
Click to expand...
Click to collapse
Thus, it's not, and thankfully because I activated mac filtering on my network and it would have been a pain otherwise.
Then for Android Q
https://www.androidpolice.com/2019/...es-by-default-with-per-network-customization/
I hope it won't be mandatory because it would be a use drawback for home network security.
raul6 said:
Google say it is inbuilt with no need for a on/off switch
Click to expand...
Click to collapse
Hi Raul, I tested this on my home network but the address was not randomizng. Looks like Samsung didn't implement the option.
Nastrahl said:
I hope it won't be mandatory because it would be a use drawback for home network security.
Click to expand...
Click to collapse
Yes, that true. But there times when this is useful too. When using Public WiFi for example.
raul6 said:
Google say it is inbuilt with no need for a on/off switch
https://support.google.com/fi/thread/293417?hl=en
Click to expand...
Click to collapse
It is COMPLETELY INCORRECT. Didn't you see the 11 thumb downs and the link he provided? It's explicitly said "disabled by default". Also, is that answer from google?
The truth is, in Samsung's OS, there are 2 wifi interfaces - wlan0 and swlan0. The former uses a MAC Address initialized from /efs/wifi/.mac.info during boot, and the latter has a randomized address. Only wlan0 will be used by default (without modding the system), so the address will never be randomized.
xdauser'17 said:
It is COMPLETELY INCORRECT. Didn't you see the 11 thumb downs and the link he provided? It's explicitly said "disabled by default". Also, is that answer from google?
The truth is, in Samsung's OS, there are 2 wifi interfaces - wlan0 and swlan0. The former uses a MAC Address initialized from /efs/wifi/.mac.info during boot, and the latter has a randomized address. Only wlan0 will be used by default (without modding the system), so the address will never be randomized.
Click to expand...
Click to collapse
From the same link
"..
Matthew Wolffsohn
5/26/19
It looks like there are two misconceptions here:
To those saying the feature is disabled: No, randomisation when joining a network is disabled. The feature is always active when disconnected from a network.
..."
raul6 said:
From the same link
"..
Matthew Wolffsohn
5/26/19
It looks like there are two misconceptions here:
To those saying the feature is disabled: No, randomisation when joining a network is disabled. The feature is always active when disconnected from a network.
..."
Click to expand...
Click to collapse
It's not available in the Note 9 Exynos regardless of the WiFi connection status.
TalesFromThePlanetEarth said:
It's not available in the Note 9 Exynos regardless of the WiFi connection status.
Click to expand...
Click to collapse
Well, I guess he meant wifi probing
Starting in Android 8.0, Android devices use random MAC addresses when probing for new networks while not currently associated to a network.
Click to expand...
Click to collapse
These are also from the link I mentioned in my previous message. I've seen that before I found this thread, and it's another thing.
Its working on android Q Note 9 exynos
This module *should* hide you data usage while tethering, allowing you to have, in theory, unlimited tethering. I just threw it together and it is NOT fully tested to see if it 100% prevents monitoring of data usage. Let me know you thoughts.
dustintinsley said:
This module *should* hide you data usage while tethering, allowing you to have, in theory, unlimited tethering. I just threw it together and it is NOT fully tested to see if it 100% prevents monitoring of data usage. Let me know you thoughts.
Click to expand...
Click to collapse
Might be a good idea to share the methodology basics you are using instead of folks needing to install and stress test their limited tethering. From what I have seen on my T-Mobile account, creating a noprovisioning custom prop like this https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662 is working and continues to work on Android 10.
sliding_billy said:
Might be a good idea to share the methodology basics you are using instead of folks needing to install and stress test their limited tethering. From what I have seen on my T-Mobile account, creating a noprovisioning custom prop like this https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662 is working and continues to work on Android 10.
Click to expand...
Click to collapse
The method used is my module is exactly the same as your link, with the addition of also editing the T-Mobile APNs to add "dun" to the APN.
dustintinsley said:
The method used is my module is exactly the same as your link, with the addition of also editing the T-Mobile APNs to add "dun" to the APN.
Click to expand...
Click to collapse
Good deal. I have been hesitant to add DUN to the apn type since I am seeing no tethering charges. Mind you, I also use it so infrequently that even if they were to see my usage it wouldn't exceed my cap.
sliding_billy said:
Good deal. I have been hesitant to add DUN to the apn type since I am seeing no tethering charges. Mind you, I also use it so infrequently that even if they were to see my usage it would exceed my cap.
Click to expand...
Click to collapse
it seems to work very well with it added...
dustintinsley said:
it seems to work very well with it added...
Click to expand...
Click to collapse
Since I have everything else done already, can you send me the value string you have saved in the APN type?
Hey @dustintinsley, first I appreciate this little mod. Thank you.
I just flashed via TWRP, I will do some testing to see if it's working, but one thing you mentioned, it also adds dun. Well after I flashed and booted, I went to settings mobile data apn and reset the apn, and I'm not seeing ,dun under apn type. Should it be there? Or no?
Thanks Dustin
EDIT: ok, few hours later, after I flashed your mod in twrp.
I watched YouTube for like an hour straight, and I just got a notification saying I used a certain % of my hotspot data. So unless I did something wrong, it's being reported as hotspot and it's definitely not working for me..
I'm on the OnePlus 7 pro, Android 10 on T-mobile. With TWRP 3.3.1-70 by muaranofrio and magisk canary.
Please advise. Thank you again Dustin
No need to reset your APN after flashing. Can you take a screenshot of your APN settings? DUN should be there but I may have missed some APNs so a screenshot could help
dustintinsley said:
No need to reset your APN after flashing. Can you take a screenshot of your APN settings? DUN should be there but I may have missed some APNs so a screenshot could help
Click to expand...
Click to collapse
No problem, appreciate your time.
Ok I didn't reset. Here is the screens of the apn after I flashed your zip in twrp.
Is the module creating a new APN or attempting to modify the existing (grayed out) one?
Sheetzie03 said:
No problem, appreciate your time.
Ok I didn't reset. Here is the screens of the apn after I flashed your zip in twrp.
Click to expand...
Click to collapse
Odd. I will have a look at it. I am also on a OnePlus 7 Pro, but on Android 9 still. Maybe it is something with Android 10? I will have to install 10 and have a look.
sliding_billy said:
Is the module creating a new APN or attempting to modify the existing (grayed out) one?
Click to expand...
Click to collapse
Neither. Flashing the mod doesn't change anything in settings apns.
It's greyed out b4 I flash the mod, and greyed out after, with no changes either.
Understand?
---------- Post added at 09:35 PM ---------- Previous post was at 09:29 PM ----------
dustintinsley said:
Odd. I will have a look at it. I am also on a OnePlus 7 Pro, but on Android 9 still. Maybe it is something with Android 10? I will have to install 10 and have a look.
Click to expand...
Click to collapse
Thank you , sorry for trouble.
One other thing that I'm thinking might be important to mention, after flashing ur mod, while there are no changes made to the apn in settings, I did notice there are a bunch of different changes in the apns xml file in system-etc
Thanks again, I'll wait to hear from you. Later
Sheetzie03 said:
Neither. Flashing the mod doesn't change anything in settings apns.
It's greyed out b4 I flash the mod, and greyed out after, with no changes either.
Understand?
Click to expand...
Click to collapse
Yeah, that is exactly why I asked. Unless it is editable in the first place, the workaround I thought was always to create a new APN. Your screenshots looked like the module was trying to make in-place edits unsuccessfully.
sliding_billy said:
Yeah, that is exactly why I asked. Unless it is editable in the first place, the workaround I thought was always to create a new APN. Your screenshots looked like the module was trying to make in-place edits unsuccessfully.
Click to expand...
Click to collapse
Yeah I see what you mean.
But this mod is specifically for TMobile and the op has the same device as I do. Maybe it's Android 10. Although didn't you say earlier that on Android 10 there is a way to get it working?
Hope Dustin can work his magic anyway. ?
Sheetzie03 said:
Yeah I see what you mean.
But this mod is specifically for TMobile and the op has the same device as I do. Maybe it's Android 10. Although didn't you say earlier that on Android 10 there is a way to get it working?
Hope Dustin can work his magic anyway. ?
Click to expand...
Click to collapse
Yes, I am also on T-Mobile and Android 10 just with different phones (Pixel 3 and Pixel 3 XL). I guess I will stick with what is working. The link is further up in the thread.
Any update on this? Followed another thread here, but looks like there are known issues. I'm on OP6T Android 10 TMobile. Thanks!
SavakSYN said:
Any update on this? Followed another thread here, but looks like there are known issues. I'm on OP6T Android 10 TMobile. Thanks!
Click to expand...
Click to collapse
Same. Also Waiting for Dustin to update hopefully.
As far as the other thread, ill pm you.
Used it while at work today, and can confirm it's working on the OOS Q beta! Ran through about ~20GB of data today, and none was reflected in my hotspot usage. I will note, however, I was using a VPN on my phone all day as well, and everything still worked like a charm (don't know why it wouldn't). Thank you!!
Termux Bypass
I've done this for ever and it's not going to be restricted to who you have but it will 100 percent get around any data throttling.
Download Termux app and install openssh-server on it. Go ahead and hotspot your phone, then run ifconfig inside Termux to get your current tethering local IP. It will be the only 192. spit out when you run ifconfig. Save this. Run sshd -dD inside Termux which starts an openssh server waiting to be connected to in debug mode to audit traffic. Now pop onto a PC or router you can SSH into, whatever and connect it to your hotspot from your phone. Now SSH tunnel all the traffic from the device back through the openssh server your running on the Termux app. Now that you are on the same local network you can SSH tunnel into that IP address you saved earlier. As long as you make sure all your traffic passes through the tunnel it 100 percent shows that all your internet is being used by Termux app not your hotspot app so you need no other spoofing of hops or anything because to your phone and carrier you are just using a bunch of data in termux, you do it right you will never be throttled I've used 150GB data multiple times.
Step by step > https://github.com/RiFi2k/unlimited-tethering
RiFi2k said:
I've done this for ever and it's not going to be restricted to who you have but it will 100 percent get around any data throttling.
Download Termux app and install openssh-server on it. Go ahead and hotspot your phone, then run ifconfig inside Termux to get your current tethering local IP. It will be the only 192. spit out when you run ifconfig. Save this. Run sshd -dD inside Termux which starts an openssh server waiting to be connected to in debug mode to audit traffic. Now pop onto a PC or router you can SSH into, whatever and connect it to your hotspot from your phone. Now SSH tunnel all the traffic from the device back through the openssh server your running on the Termux app. Now that you are on the same local network you can SSH tunnel into that IP address you saved earlier. As long as you make sure all your traffic passes through the tunnel it 100 percent shows that all your internet is being used by Termux app not your hotspot app so you need no other spoofing of hops or anything because to your phone and carrier you are just using a bunch of data in termux, you do it right you will never be throttled I've used 150GB data multiple times.
Step by step > https://github.com/RiFi2k/unlimited-tethering
Click to expand...
Click to collapse
I've never used this before. I checked the instructions you linked, but they really don't add to the clarity of this part:
"Now that you are on the same local network you can SSH tunnel into that IP address you saved earlier."
Do you know of any video tutorial or anything that might help with this?
Hi,
how can I permanently disable MAC adress randomisation?
I can set this for each connection separately but I want to disable this feature completely.
Thx
Doenerbude said:
Hi,
how can I permanently disable MAC adress randomisation?
I can set this for each connection separately but I want to disable this feature completely.
Thx
Click to expand...
Click to collapse
From this site, it would appear you cannot in Android 10: https://source.android.com/devices/tech/connect/wifi-mac-randomization
I'm curious though, what use case do you have where you want to do this?
JohnKuczek said:
From this site, it would appear you cannot in Android 10: https://source.android.com/devices/tech/connect/wifi-mac-randomization
I'm curious though, what use case do you have where you want to do this?
Click to expand...
Click to collapse
I don't like that it's the default setting. For some reason, if I change WiFi networks (away from the one that autoconnected), I have to re-enter the password and have to remember to change it back to "Use device MAC".
brandon5491 said:
I don't like that it's the default setting. For some reason, if I change WiFi networks (away from the one that autoconnected), I have to re-enter the password and have to remember to change it back to "Use device MAC".
Click to expand...
Click to collapse
Is MAC randomisation causing a problem for you? Maybe someone can help if they understand the issue.
I have several WiFi networks to deal with at work and access control is based on MAC address.
Thats no security thing, only offline networks for testing purpose. SSID changes often and I always forget to change the setting...
@brandon5491 had the same issue with WPA3 but seems to be fixed with March Update (or newer AP firmware)
I have several WiFi networks to deal with at work and access control is based on MAC address.
Thats no security thing, only offline networks for testing purpose. SSID changes often and I always forget to change the setting...
@brandon5491 had the same issue with WPA3 but seems to be fixed with March Update (or newer AP firmware)
Well iOS and Android do MAC randomisation so it will be more than just you struggling with this issue, maybe raise the problem with your work? Maybe there is a tasker addon that can turn the option off based on some rule you create.
As for stopping you, I'm not sure how? If you join a network the device will use its fixed hardware MAC address which is approved. The MAC filtering should not be enforced unless you are connected to the network.
Randomized MAC addresses and IoT Devices
JohnKuczek said:
From this site, it would appear you cannot in Android 10:
I'm curious though, what use case do you have where you want to do this?
Click to expand...
Click to collapse
For me, it makes it nearly impossible to onboard new smart devices. Lifx, Kasa, Samsung, etc all need static MAC when adding them. You have to stop the install, go change the setting on the wifi for each device, then start the install all over again.
William