Jump to content

TheFuzzyFish

Members
  • Content Count

    3
  • Joined

  • Last visited

About TheFuzzyFish

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. OH!!! Everything makes a whole lot of sense now! So wlan0 and wlan0-1 are the same hardware interface, just managed by different "programs" (put in quotes because it's actually managed by the kernel, not necessarily a program in the sense that people are used to using the term) on the data-link layer, and wlan1 is a completely different hardware interface. Might explain some things, especially the goofy MAC addresses. Excellent! Thank you very much for the speedy and accurate response.
  2. Okay okay I know, hold on. Before you mark this question as a repeat question and yell at me to search the forums a little bit harder, hear me out. So I recently became the (very) proud owner of a Wi-Fi Pineapple Tetra. I'm fairly well-versed in terms of the Linux system layout, but there is one thing that confuses me... For those of you who are unaware, (and this is the part where I need guidance, as I may be wrong) a Wi-Fi Pineapple Tetra is equipped with 2 radios, each radio having 2 antennas to meet a total of 4 antennas. That fact alone was pretty difficult for me to find, because looking at it from the operating system, I was under the impression that there were 3 radios, which is what has been confusing. All the schematics and descriptions I've seen describe the Tetra as having 2 radios... but then, how can there be three wireless interfaces? An even better question, how can they operate independently (I.E. one be in monitor, one be in managed, and one be in master mode)? Here is my hypothesis: there are 2 radios, wlan0 and wlan1. Wlan0-1 is somehow a hybrid of the two, utilizing some weird feature that allows us to make a pseudo-interface that isn't actually linked to a specific piece of hardware, but instead shares the workload between the two radios... but that violates the fact stated in the statement above: they can all act independently of one another. Then, another article I read described wlan0 as the first radio and wlan0-1 as the second radio, but then, where did wlan1 come from? I thought it only had 2 radios? I understand that wlan0 is the open/hidden AP from the Networking module and that wlan0-1 is the managed AP, that much I gathered from /etc/config/wireless. So I guess my final question is simple: Can someone please please please please help me understand where these radios are on the actually hardware device?? I'm looking into building some upgraded antennas for parts of the Pineapple, and I'd like to know exactly how they will affect what. I do know that wlan0 is hooked up to the two antennas closest to the ethernet port, and that wlan1 is the two antennas closest to the reset button, but that still leaves the vital question: where is wlan0-1? Plus, I'm curious and confused. Those two aspects of me like to combine into either hours of research, or a forum post. I've tried hours of research with no results, and so here I am. Any help would be greatly appreciated. Cheers!
  3. Hello! I'm relatively new to the forums, especially considering I just recently got my first Hak5 item 6 days ago for Christmas: the Hak5 Elite Field Kit. Quite a handful at first, but slowly I started to learn how everything works (thanks pocket guide!), and I have just a few questions about my favorite item in the bunch, the Wi-Fi Pineapple Tetra. Where is SSL in the main interface? I'm a high school student, so it's not like I can walk around with a laptop to do penetration testing, therefor I can't use a direct connection via ethernet or serial, nor do I have an android, so I have no micro USB interface. I do, however, have an iPhone, and thus I control the Pineapple Tetra via the management access point. So obviously, my connection to the web server is encrypted via WPA2, however being an aspiring penetration tester, I know that all it takes is someone listening to the handshake (or forcing my re-authentication) and that data, and after some time, the password to both my management AP and root account on the Pineapple is compromised. That's no good! Obviously, I've found ways around this (ssh -fNL 80:localhost:1471 root@172.16.42.1 on the computer, or I use ServerAuditor [now called Termius] to use local port forwarding on my phone), opening an SSH tunnel to route my HTTP traffic, which is close enough to SSL, but it's a pain. I also come from using strictly Apache2, and I'm unsure as to how I should configure Nginx to support SSL. Maybe in a future firmware update, there could be a setup for that? While we're on the topic of SSL, how come SSL is available for the Wi-Fi Pineapple Nano but not the Tetra?? I was very excited to get into some simpler MITM attacks, but was rather disappointed when I only found SSLsplit, which I'm not at all knowledgeable about. All I can tell from it is that it's very unreliable, sometimes working, and sometimes just flat out not. I could definitely be wrong on this next part, but seeing as how the Tetra and Nano share the same firmware (I think??), I don't quite see the point of offering completely different modules when it has nothing to do with the hardware. In my testing lab setup, I have a hidden network that I do some toying with, and was rather befuddled when I wandered into Wi-Fi Client mode to find that there was no option to connect to a hidden network! It wasn't even mentioned in the Help module. Possible future firmware addition? I know that there are multiple ways to broadcast wireless networks (Occupineapple, PineAP, and Networking), but I have yet to find any option in the UI or in the actual machine (via SSH) to host a fully-manageable network, where I control the specifics, such as encryption type (WPA2 is forced in the Management AP, whereas I like to toy with Radius, or even WEP), bandwidth throttling (can't have people stealing all the 3G on a field deployment!), bridging techniques (in Wi-Fi Client Mode, NAT is forced), etc... So yeah, maybe if some administrators happen across this article, they can make some notes for future firmware releases, or if a user comes along, they can enlighten me in some methods of achieving some things listed here. Thank you! Keep up the excellent work!
×
×
  • Create New...