Posted: Mon Sep 15, 2014 23:59 Post subject: Is it possible to crack Wi-Fi password?
Asus RT-N16, DD-WRT v24-sp2 (08/07/10) mega
I found unknown android devices in control panel.
Password was changed 2 days ago.
As far I know WPS is absent in DD-WRT. How can users log in to Wi-Fi if they don't know Wi-Fi password? I'm shure they can't know password from trusted users with office notebooks.
There's only few information in your post. What encryption are you using? WEP? WPA? WPA2? What authentication? TKIP? AES? How long is your Key? Is it a safe key? Is there any option that android-clients could connect via ethernet to the router? At which place do you see the android devices in the control panel?
Getting a dhcp lease does not make them "in". _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
There's only few information in your post. What encryption are you using? WEP? WPA? WPA2? What authentication? TKIP? AES? How long is your Key? Is it a safe key? Is there any option that android-clients could connect via ethernet to the router? At which place do you see the android devices in the control panel?
These are my wireless settings:
Key is alphanumeric and strong enogh. I think.
I look for list of connected devices at Status|WAN and Status|Wireless pages.[/img]
I don't know much about this, but how would a device communicate to authenticate if they were not connected?
You have nothing to worry about if you are using WPA2-aes with a reasonable passphrase. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Murrkf, DHCP is not a security feature. It's easy to use an manual IP-Address in the same subnet.
@dodz: Use Security Mode "WPA2 Personal" instead of "WPA2 Personal Mixed", or are you using clients which don't support AES? A full 64-character passphrase will be much more secure than a passphrase with only 11 characters.
I don't know why you're seeing any devices at Status->WAN. This site is not designed for showing connected devices. Please post a screenshot of it.
Murrkf, DHCP is not a security feature. It's easy to use an manual IP-Address in the same subnet.
My point is that just because a device connects to the router, does not mean that it has any network access, as it still has to be authenticated. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
@dodz: Use Security Mode "WPA2 Personal" instead of "WPA2 Personal Mixed", or are you using clients which don't support AES? A full 64-character passphrase will be much more secure than a passphrase with only 11 characters.
Thanks for good advice!
mittelhessen wrote:
I don't know why you're seeing any devices at Status->WAN. This site is not designed for showing connected devices. Please post a screenshot of it.
I've made mistake. I'd write "Status|LAN" of course.
@Murrkf: DHCP has nothing to do with an authentication. If someone knows or cracked the passphrase, it will be very easy to use any IP-address in the same subnet. There is no DHCP necessary!
@Murrkf: DHCP has nothing to do with an authentication. If someone knows or cracked the passphrase, it will be very easy to use any IP-address in the same subnet. There is no DHCP necessary!
This has nothing to do with what I am saying, which is the reverse of what you wrote. Just because someone has a connection to the router does not mean that they have been authenticated and have access to the Lan. In other words, if they don't know the passphrase, they can't get in. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
You confuce the sequence! There're two different "connections". First of all, there's the wifi-connection. Second of all, there's the ip-connection. IP-connection doesn't play any role without having an established wifi-connection. So IP-adressing (including DHCP) doesn't play any role because it needs an established wifi- (or ethernet) connection.
