Skip to main content

Recon and SSID - Mapping With VisiWave Site Survey

My laptop is refurbished. I've written about how there are a few ... quirks. Being a technology professional, I felt okay with adopting an older machine, knowing I had the skill to fix moderate issues.

From dying drivers to monitor massacres, I've ID'd, solved, and documented a lot of issues. 

The newest one was my Wi-Fi adapter dropping the connection to a specific extender.

While troubleshooting, I was curious about doing recon of WiFi networks and broadcasting devices anyway.

That issue? A power setting. It was so determined to save power, it would disconnect. The extender is also flirting with the older end of 6 years old.

 The battery needs to be replaced, but that's new to me. As a Windows laptop, there are a plethora of options to pick. How do you decide which one is safest?

 I am suddenly concerned about this despite having 3 unofficial, 15$ Macbook Air chargers from eBay, and no explosions.

But let's move onto the Site Survey - Where can I find the strongest signal in my home?

It's not when I'm closer to the router - I'm certain materials interfere with it, when I use it outside. 

Using VisiWave - It even makes noise when it's scanning. They required me to upload a copy of my house's flooring plan. Absolutely not, but there's no restriction on the image I could upload, so I picked a stock image of some clouds.

It picked up some television boxes, even someone's smart device.




I erased that particular one, but kept some of the cool names.
If you can't have fun with your Wi-Fi SSID name, where can you have fun?

  When I finished making a vague outline of my home, I stopped the scan. This isn't going to be super accurate, just super interesting.



When you click a dot, it brings up some information on the bottom;





That smart device? Has no security. Not good. Further research (AKA: Looking up the MAC address to see if I can sus out a vendor), shows me the address was anonymized by the network administrator (Or built in security). While it's still unsecured, at least it can stand up to one bit of recon. 

Unless you search for smart device manufacturers for that particular product (It specifies the actual device, but I won't say what it is). Simply by knowing my neighbors, I have a good guess as to the brand that might be.

 

 I ran the scan on the other side of our property, near some other houses, and got some new SSIDs....and a second one of ours. The MACs look similar, but you can spoof a MAC Address. I did tinker with VLANs on the system, but that was with another router attached; Why did this 2nd one appear?


Other APs also repeated, but not the extensions.

I see some channels listed as simple numbers ('6') and others with MHz (1/40MHz'). There are a handful of people on Channel 11, but way more on 6.

In short, tools help, and more learning is required. This can be helpful for reconnaissance and finding hidden APs (That broadcast SSIDs) in a building that needs mapping.

Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more