"Penetrate" connects you to wireless routers with default keys. Penetrate calculates WEP/WPA/WPA2 keys for some wireless routers.
The following wifi routers are supported:
Thomson,
Infinitum,
BBox,
DMax,
Orange,
SpeedTouch,
BigPond,
O2Wireless,
Otenet -Pirelli Discus -Eircom -DLink -Verizon FiOS (only some routers) -Fastweb (Pirelli & Telsey) -Jazztel_XXXX and WLAN_XXXX
Reversing Thomson routers requires a dictionary file, the app instructs you on how to set it up.
Penetrate is not a wireless cracking or hacking tool like aircrack. It does, however, give you keys which are useful for penetration testing. Use only with permission from network owners.
Have a nice day and happy cracking!
I am not entirely sure that I understand this post. Is "penetrate" an option on the Archos 101 or something that needs to be downloaded?
"penterate" is an app that cracks protected wireless networks with defaut keys, and you can get it from market
Thanks, i will give that a go
Related
I just bough my XDAIIs. Live in Sydney Australia.
I'm generally happy with it but the wifi reception is really bad.
I work at a Uni where we have a huge wireless Network with over 150 basestations and I work in the ITS department where we have at least 4 wireless access points. 3 of them a A radio and one is the BG radio.
From what I've seen the XDAIIs used the BG radio and not the A but I have been reasing several posts and it looks like the wifi antenna is very weak.
I too took my XDAIIs right in front of the base station set the reception to FULL and could barely manage a signal and even when it did manage a signal I couldn't connect.
I have
ROM Version 1.12.62
ROM Date 10/04/04
Radio Version: 1.02.00
Protocol: 1337.32
ExtROM Version: 1.12.925WWE
Is it possible to update the ROM on the XDAIIs yet with a later version such as ROM 2.02.t1WWE. I see posts inidcating its possible on XDAII but not XDAIIs
Peter Birkle
Peter,
I haven't bought a Blue Angel yet, primarily for this reason. However, I've been watching these forums closely to see if anyone knows what the problem is with WiFi reception.
So far, no one has posted a solution, and I fear it's not a ROM or software related issue, but a hardware design issue. My guess is that the WiFi antenna design is extremely poor and either:
1. Internals are interfering with the reception of the WiFi signal
2. The case (which I do believe is some metal alloy) might actually be preventing the internal antenna from receiving external signals.
Hope it helps. By the way, the Blue Angel only supports 802.11b, not 11g or 11a.
Some wireless defination
802.11a - almost proprietary wireless network (All PDA based devices are 802.11b, as per other reply)
802.11b - standard 11mb, and what has been mainstay of most wireless devices up until past 6 months
802.11g - standard 54mb wireless.
Sure there are some others in the range afterwards, but next comes configuration.
Most A wireless networks only communicate with other A networks, few were bought out with interopaeratibilty.
B networks will communicate with B Networks
Most G networks are set by default as communicate with G only (The fast setting), and are not changed to support both, as with many wireless networks, slows the entire speed to the lowest connected speed.
Nearly all G wireless networks are backward compatible with B networks and hence why is displayed on box B/G
Hope this clears it up.
For some real run, get wififofum and a bluetooth GPS, and plot out the access points, then hand to your security audit guy, watch those eyes turn red.
I'm not sure it is a hardware issue because mine works absolutely fine and I've spoken to others who have no problems. Anywhere in the house I get a really good signal (about two thirds on the signal quality indicator) and even outside I get a signal. And that is on best battery setting. A friend of mine lives three doors down (i.e. a lot of bricks in the way!) and I JUST get a signal in his house with best wi-fi performance set.
This would suggest the hardware is fine. Certainly it is on a par with my Dell 510m laptop with a centrino chip.
The only thing I've noticed is that the signal indicator drops off VERY quickly as I move away from the house. So it will stay on two thirds for quite some time and then suddenly drop down to almost nothing about 30 meters away.
ROM 1.12.62 WWE
Rom Date 10/04/04
Radio 1.02.00
WiFi fine on Cingular Siemens Sx66
Following these posts led me to have low expectation of the WiFi capability of the SX66, but having received mine on Monday, I am pleased to state, that at least on my unit, the WiFi is working great. On my AP, I run MAC filtering, 128bit WEP and shared authentication. To ease the installation, I turned my AP back to OPEN Authentication, WEP OFF, and MAC filtering OFF. In this config, the SX66 immediately found and connected to my AP. This also gave me an easy way to determine the MAC address of the SX66 for inclusion in my AP and my router tables (ie PPC Wireless LAN Manager MAIN tab). The WiFi signal strength indicated was on par with what my two other WiFi notebooks indicated(ie around 3/4 max). Taking this one step at a time, I then added the SX66's MAC address to my AP and router tables and turned on MAC filtering. That worked okay, so I then set the AP to WEP encryption and entered my 128 HEX (yes HEX) WEP key into the SX66. BINGO, that worked as well. Then I set the AP and the SX66 into Shared Authentication mode and that worked as well. So, I have my SX66 connected my well guarded WiFi AP with full filtering, encryption and authentication active.
As I mentioned, in testing the WiFi capability, I am finding it at least as good as what my Dlink DWL650+ PCCards running in my notebooks and it also seems to have similar range.
I did note that if you leave the Power Save Mode in the default setting ("Best Battery"),it really dogs down the perfomance of WiFi. I moved mine back to "Best Performance" and the web browsing speed is on par with my notebooks.
All in all, I am very pleased with the WiFi connectivity.
david
wi fi reception
Hi, I don't know about wi fi and all, but could it be an issue where there just isn't a good signal..or the signal you receive depends on where you are as it does if you have a tower close by or not? Sorry if I seem like I don't know what I'm talking about...because I don't. I've just been getting into these devices in the last 6 months and really behind...I'm wanting a blue angel (early next year), but want to make sure it's right for me and weigh the good against the bad
Hey all. So heres my deal. I have a Linksys E3000 router and an Edimax Wireless Extender I just picked up. I got this since in my house, the router is on one side of the house and so naturally, on the other side, I get 1 bar of wifi strength. Was hoping to improve that. So what I wanted to do was have both units have the same SSID and have the devices automatically switch between the physical devices (same SSID) as I get near them. This didnt work. In fact, both my S3 and my Nexus 7 kept getting confused and dropped connections often.
So now Im trying it where they have different SSIDs (lets say Router1 and Router2) so no conflicts. The issue I have is this. I want both my S3 and N7 to AUTO SWITCH to the better signal SSID. Im running Cyanogenmod 10.1 on both devices and I see in the adv wifi settings something about, 'Only connect to a network where strength is GOOD'. This seemed to be the answer, however it doesnt actually work. 1 network shows great and other shows fair and it still wont switch.
Wondering if there is any other way around this? Otherwise this extender is basically useless to me as I dont feel like constantly switching my wifi networks as I walk across the house. (wow I sound spoil when I say it like that lol)
Thanks all
Is it configured for Universal Repeater Mode?
When you say "it" are you referring to my router or the extender device?
The router BTW is a Linksys e3000 with dd-wrt and the other unit is edimax 7348rpn. I believe that's the right model. Its a little plugin unit. Thanks
RoachForLife said:
When you say "it" are you referring to my router or the extender device?
The router BTW is a Linksys e3000 with dd-wrt and the other unit is edimax 7348rpn. I believe that's the right model. Its a little plugin unit. Thanks
Click to expand...
Click to collapse
From the Edimax site:
Complies with the IEEE 802.11b/g and IEEE802.11n standards.
Supports 2.400~2.4835GHz frequency band.
High data rate up to 300Mbps network speed.
Auto rate fallback in case of obstacles or interferences.
Supports point-to-point and point-to-multi point bridge function.
Supports WDS (Wireless Distributed System) repeater mode.
Supports Universal Repeater mode.
Supports AP Client mode.
Supports four sets of ESSID to group the different wireless networks.
Supports roaming link integrity.
Provides 64/128 bit key length WEP data encryption.
Supports WPA, WPA2 security enhanced function (pre-shared key, 802.1x, TKIP, AES …).
Supports WPS (Wi-Fi Protected Setup) function.
Provides MAC access control.
Provides hidden SSID function.
Supports Web-based configuration.
Firmware upgradeable via Web browser.
So it can be configured into different modes. Make sure you have it configured for Universal Repeater Mode
Hi everyone,
I have my Nexus 7 connected to an verizon actiontec router. I am getting terrible wifi with WPA2 security enables. Loading websites takes forever and youtube constantly gives network error. I changed the encryption to WEP and its not disconnecting as much but I would prefer to run WPA2.
Anyone have any suggestions on what is causing the lag and disconnects? 2 laptops and 2 android phones no issues.
Try switching to 802.11g. The N7 is quite flaky in 802.11n mode with a lot of routers.
If you are using WEP, you are in effect forcing 802.11g mode, since 802.11n requires WPA2.
tni.andro said:
Try switching to 802.11g. The N7 is quite flaky in 802.11n mode with a lot of routers.
If you are using WEP, you are in effect forcing 802.11g mode, since 802.11n requires WPA2.
Click to expand...
Click to collapse
Thanks for the reply tni,
Is this a hardware issue or a software issue? Could hardwiring and IP number and switching back to WPA2 possibly fix the issue?
cloves said:
Is this a hardware issue or a software issue?
Click to expand...
Click to collapse
Driver and/or firmware. The Nexus 4, which has pretty much the same Wifi hardware, also has quite a few complaints about Wifi issues.
Could hardwiring and IP number and switching back to WPA2 possibly fix the issue?
Click to expand...
Click to collapse
It's highly unlikely that a fixed IP will make a difference.
Not sure if that came across, but you can use WPA2 with 802.11g (you need to configure that at the router).
Well I changed the router over to WPA2 and then in the advance preferences set it to 'Legacy Mode' to support only 802.11bg and the tablet seems to not be having many hang ups even with youtube. I'll post back if anything changes. Thanks and hopefully this helps a lot of people out there.
I'm using N7 2013 with two different routers,
Both with WPA2, and 802.11n.
No problems at all.
Well, I just did a heck of a lot of work on the IEEE 802.11 protocol suite. I am in no way an expert, but I picked up a bunch of interesting factoids.
- In the 802.11n protocol implementation, all devices must have 802.11n supported NICs. This includes all the clients, not just router. If you have even a single device that is doing legacy 802.11b/g while all the other client NICs are doing 802.11n, then the router will not do 802.11n for any device. Yes, all or nothing deal and the router does not show it. I used Wireshark to confirm this situation exists by drilling down a ton of 802.11 data frames. Despite the router staying set in the drop down menu to 802.11n, under the hood, all the devices dropped to 802.11g.
- Even worse, I know I have clients and router NICs that all support 802.11n, yet I get dropped into the 802.11g protocol. To try to find out what happened, I started from scratch. I put my router into 802.11n which lists it as "performance", then added a static IP to my Nexus 7. I immediately had 58Mb/sec. since 58Mb/sec > 54Mb/sec, I figured maybe I did get 802.11n this time since 802.11g gets 54Mb/sec in optimal conditions. When I went to check which protocol my Nexus 7 is using, I moved it in front of me, a distance no more than 18 inches, and saw my signal drop to next to nothing. I pulled up the Nexus 7's WiFi advanced settings to find out that I now only have 5Mb/sec and the protocol is now 802.11g. This means while roaming, if you hit a sufficient enough degradation in the signal, the Nexus 7 drops your 802.11n status like a hot potato and no, you can't get it back unless you reset everything. I mean at least, to date, I have not found a way to keep a device configured to stay with 802.11n even if the bandwidth drops.
Since I was given a drop down menu in my router as to which protocol I wanted to use and since the 802.11n specs say it is all or nothing, I thought that the router would enforce 802.11n and not allow a legacy NIC to connect to it. This is far from the case. Why they even give us a drop down menu if they are always going to do 802.11b/g/n anyway is beyond me.
Now that I have seen Nexus's wireless protocol drop from 802.11n to 802.11g outside of my control, I want to find all devices that misbehave like this and see if there is anything I can do to force the client to stay on 802.11n. Obviously, I also have to eliminate dead and near dead zones.
Just thought I'd share the all the fun I've had getting to this abysmal point.
I will dig into our smart phones and tablets another day to see if I can force it to stay with 802.11n even its Rx signal attenuated for a few seconds.
I hope this helps others and if your experience is different then mine, I'd love to here what your findings are.
You may be fighting interference not only from the neighbor's WiFi, but appliances in your home. Possible sources for rf noise would include dimmer switches, CRT and plasma screens, microwaves, cordless phones. An rf detector can be bought or built or an am radio tuned between stations can work.
I've seen anywhere from 5mbps to 300mbps connect speed, it can change in one session if the router dynamically adjusts throughput. Also, there may be a power level setting in the router setup to get your signal farther above the noise floor.
Sent from my Le Pan TC1020 using Tapatalk
---------- Post added at 09:23 AM ---------- Previous post was at 09:17 AM ----------
An easy rf detector: single coil electric guitar pickup and cheap practice amplifier sourced from a guitar shop. Ask the guitar tech for a good used p/u, they swap them out all the time.
The wider channels used for faster throughput will be more susceptible to interference than the g standard,IMO.
Sent from my Le Pan TC1020 using Tapatalk
So, weird thing started to happen last night. Both my Samsung devices ( my 2014 10.1 and my S4) started failing to get an IP from my wifi network. It would see the wifi network and report a strong signal, but would fail at the obtaining IP address. The IP assignment is handled by a Windows DHCP service running on a domain controller. I work in IT so I have a fairly extensive lab at home with routers, switches, servers, domain controllers, etc. The wireless access point in my home is a WNDR3700 with no WAN port config as my firewall/routing is done by a Cisco ASA 5505. All the 3700 does is provide wireless access to the network, essentially it acts solely as a wifi AP. Every other wireless device on the network is functioning fine including 3 laptops, a Blackberry and two other Android tablets ( Asus Transformers). So I know nothing is wrong with the dhcp or the AP in general. It's not a security issue as it is not failing on authentication, just on obtaining IP. So as a workaround I configured each one with a static IP and, of course, everything works fine.
One thing I noticed that seemed odd was that when I went to change the IP addr the address that was already in there, but greyed out sort of, was the wrong network for my home wifi. The phone and tablet both looked like they had a 192.168.1.0/24 address whereas my home wifi segment is 192.168.0.0/24. So maybe that had something to do with it. At the office now and both my phone and tablet have no issue connecting to our Cisco APs and getting a dhcp config from a Windows DHCP server. So pretty weird situation. I'm fine with leaving them on static config while on my home wifi network. Was just wondering if anyone else has seen this before?
Thanks
For any that might be interested. I used inSSIDer to find a less crowded channel for my 2.4 ghz band at home and both my Samsung devices are connecting and receiving ip addrs now.
Hi all, first post so sorry if it's in the wrong place! I seem to have an issue connecting to my Fire Stick via adbfire. Adbfire won't connect to my Stick (Followed all steps required) and I have a feeling that it could be because I'm connected to my university Halls of Residence WiFi which is a shared network; is it possible that because of this the IP Address on my laptop won't match the one with the Stick? If so, is there any possible workaround to be able to get Kodi on the device?
Many thanks!
John
Hi,
Most universities employ Layer 2 client isolation, so that one wireless client is not able to communicate with another client. You will likely need to bring in your own router and use your own wireless SSID (against most university network AUP) in order to connect and push things via ADB.
Easiest workaround I can think of is to create your own wifi network, either by using your own router (even without an active internet connection, there are cheap ones available) or you could try a laptop/desktop or a smartphone.
If you have a wired ethernet connection or get a router which can connect to another wifi network, you may be able to get away with your own router all the time, but it's a gamble depending on your uni (mine apparently claimed that they would ban people, but I've been using a cable router without any problems so far (touch wood)).
If you go the path of your own router, be sure you hide the SSID.
The Cisco APs we used, at the university I used to work at, had a dubious "feature" that would actively search out "rogue" SSIDs and would continuously associate/deassociate with them in order to overload the AP and cause them to lock up. They didn't want students using other public available SSIDs for fear of privacy concerns.