DPChallenge: A Digital Photography Contest You are not logged in. (log in or register
 

DPChallenge Forums >> General Discussion >> WiFi
Pages:  
Showing posts 1 - 25 of 38, (reverse)
AuthorThread
01/23/2013 01:21:11 PM · #1
Is there a way to see if anyone is connected thru your connection?
01/23/2013 01:25:00 PM · #2
//www.makeuseof.com/tag/catch-snoop-logging-wireless-network/
01/23/2013 01:27:38 PM · #3
Yes, absolutely. Your router has a web interface that is accessible from within your network. For most routers,, type in address 192.168.1.1 in your browser's address bar. You will get a prompt to enter the admin password for the router. Once you enter this, you will be presented with the router's administration "website." You can go to your DHCP table, and see every device that is connected to the network, either wired or wireless.
Note that for a few routers, specifically ATT Uverse equipment, the address is 192.168.1.254
01/23/2013 01:30:08 PM · #4
Thanks a lot guys!

01/23/2013 01:34:23 PM · #5
Yes and my router default is 192.168.0.1 (eta: my router is a Netgear and my previous D-Link was also 192.168.0.1)

It is probably worth googling your router model and "default IP address" if you are not sure what it is.

On my router, once logged in there is a "connected devices" button which shows me all the devices on the network. I actually have my network locked down so only specified devices can connect anyway - you should also be able to turn that feature on if you want to stop random devices from connecting.

There are a bunch of ways to make your wireless network a whole lot more secure, but seeing as you haven't asked that yet, I won't rattle off a load of potentially irrelevant stuff LOL.

Let us know if you want more info.

Message edited by author 2013-01-23 13:35:41.
01/23/2013 02:48:11 PM · #6
Actually that was my main reason for asking. Any further info would be appreciated.
Thanks
01/23/2013 03:19:03 PM · #7
Here are some basic guidelines for securing a home network. The essentials are enabling the router's security (requiring a key to log on) and changing the network's default name and password.
01/23/2013 03:21:36 PM · #8
First things first we could do with your router model as the config is different for all of them.

In essence, I would look at

1) ensuring you have encryption set, preferably WPA/WPA2 with PSK2 / AES but definitely not WEP as that can be cracked in seconds
2) ensure the default admin password has been changed to something strong
3) if you are never going to want to access your router admin from outside your home, make sure remote management is disabled
4) change your SSID (essentially the wifi network name) from the default
5) disable broadcasting of the SSID (this will mean it won't be visible to devices searching for a wifi network)
6) enable MAC address filtering... This is where you can essentially list specific devices that are allowed to connect to your network. It needs a bit of management every time you want to add a new device to your network but it gives you strong control
7) make sure the firewall of your router is enabled (newer routers tend to be firewall on by default it some older ones are firewall off by default). If you have more than one device on your network that needs accessing from the Internet in some way you may need to configure port forwarding / NAT - I.e. if you are serving your iTunes library from a specifc pc so that you can access it over the internet you need to tell your router that if it sees incoming traffic for iTunes it directs it to the correct pc - but you may have a filesharer running on another machine so you need to direct filesharer traffic to that machine). This is all done via port-forwarding.

There are probably other things that can be done but these are the settings I would look at in the first instance. Most of the terminology I have used is generic to all routers, but the mechanics of changing these settings will differ from one router to the next.

Lawry

Message edited by author 2013-01-23 15:27:13.
01/23/2013 03:28:44 PM · #9
Originally posted by kirbic:

Here are some basic guidelines for securing a home network. The essentials are enabling the router's security (requiring a key to log on) and changing the network's default name and password.


change the name to something like "virus32_install.exe" for fun.
01/23/2013 03:30:36 PM · #10
Originally posted by lawrysimm:


5) disable broadcasting of the SSID (this will mean it won't be visible to devices searching for a wifi network)


this actually can make your network vulnerable, just leave it broadcast and set a very tough passkey.
01/23/2013 03:32:32 PM · #11
I favour "Police Cybercrime Unit" as an SSID :-)

Kind of deters moochers....

SSID Suggestions
01/23/2013 03:36:49 PM · #12
Originally posted by mike_311:

Originally posted by lawrysimm:


5) disable broadcasting of the SSID (this will mean it won't be visible to devices searching for a wifi network)


this actually can make your network vulnerable, just leave it broadcast and set a very tough passkey.


Fair point.... A determined hacker can still discover your SSID anyway, and this can just cause problems with config if you can't find your own network and aren't particularly techie so feel free to skip this one :-)
01/23/2013 03:38:34 PM · #13
abraham linksys LOLOLOLOLOL
01/23/2013 04:52:44 PM · #14
Originally posted by FourPointX:

abraham linksys LOLOLOLOLOL


I prefer "Cisco Kid"
01/23/2013 04:54:40 PM · #15
My latest favorite setting is the dual networks. My wife doesnt want the kids to be able to access wireless at night so I set the 2.4ghz network with one passcode that the kids have and set that network to stop broadcasting from 11pm to 6am and leave the 5ghz network broadcasting 24 hrs for myself and her with another passcode.

Message edited by author 2013-01-23 16:55:51.
01/23/2013 05:08:48 PM · #16
I went with "FBI surveillance van #14"
01/23/2013 05:20:18 PM · #17
well if were talking funny ssid's there is one near my work called "surf my porn"
01/23/2013 06:37:17 PM · #18
Originally posted by smardaz:

My latest favorite setting is the dual networks. My wife doesnt want the kids to be able to access wireless at night so I set the 2.4ghz network with one passcode that the kids have and set that network to stop broadcasting from 11pm to 6am and leave the 5ghz network broadcasting 24 hrs for myself and her with another passcode.


Indeed. I love this feature of the newer routers. We don't have kids, but we have a steady stream of guests that want to use the wifi. We have a network for guests that has a simple password that human beings can remember, and a separate network with a 50+ character crazy password that nobody could ever remember that our own stuff is connected to.

As far as Lawry's list....

I agree with Mike that turning off SSID broadcasting causes more trouble for legitimate users than security benefit. Same thing with MAC address filtering. MAC addresses are easy to spoof, and if you're doing the other things right (WPA2, good passwords), MAC address filtering is probably of minimal benefit. The rest of the advice is all good stuff.

The SSID on my totally locked down TrendNet router is "Linksys". But I'm just being perverse. The main thing about SSID names is to *not* give it a name that clearly identifies it as yours, especially if you're an interesting target.

One of my coworkers spent an entire Christmas break trying to break into some neighbor's wifi that had the SSID "Get your own wifi, b*tch!" He eventually got in, but it took 11 days on a 128 core blade server to break the password. Once he got in, he changed the SSID to something else that was even more unprintable, changed the password, and went back to using his own wifi.
01/23/2013 07:58:14 PM · #19
Thanks again folks.
01/23/2013 10:13:59 PM · #20
Originally posted by bhuge:

I went with "FBI surveillance van #14"


I always change those whenever I see them to "hacked FBI surveillance can"
01/23/2013 10:15:28 PM · #21
Originally posted by Ann:

Originally posted by smardaz:

My latest favorite setting is the dual networks. My wife doesnt want the kids to be able to access wireless at night so I set the 2.4ghz network with one passcode that the kids have and set that network to stop broadcasting from 11pm to 6am and leave the 5ghz network broadcasting 24 hrs for myself and her with another passcode.


Indeed. I love this feature of the newer routers. We don't have kids, but we have a steady stream of guests that want to use the wifi. We have a network for guests that has a simple password that human beings can remember, and a separate network with a 50+ character crazy password that nobody could ever remember that our own stuff is connected to.

As far as Lawry's list....

I agree with Mike that turning off SSID broadcasting causes more trouble for legitimate users than security benefit. Same thing with MAC address filtering. MAC addresses are easy to spoof, and if you're doing the other things right (WPA2, good passwords), MAC address filtering is probably of minimal benefit. The rest of the advice is all good stuff.

The SSID on my totally locked down TrendNet router is "Linksys". But I'm just being perverse. The main thing about SSID names is to *not* give it a name that clearly identifies it as yours, especially if you're an interesting target.

One of my coworkers spent an entire Christmas break trying to break into some neighbor's wifi that had the SSID "Get your own wifi, b*tch!" He eventually got in, but it took 11 days on a 128 core blade server to break the password. Once he got in, he changed the SSID to something else that was even more unprintable, changed the password, and went back to using his own wifi.


11 days??? He needs some new software.
01/23/2013 10:39:45 PM · #22
Originally posted by mike_311:

Originally posted by lawrysimm:


5) disable broadcasting of the SSID (this will mean it won't be visible to devices searching for a wifi network)


this actually can make your network vulnerable, just leave it broadcast and set a very tough passkey.


I believe it make your device more vulnerable to SSID cloning in other places (since it broadcasts the SSID when it is looking for a connection), not actually making your network less secure.

I would like to know how often this has actually happened (wouldn't they need to close your encryption key too) If your SSID is hidden at least someone camping in your neighborhood looking for networks to get into won't see it except possibly while you are initially connecting.

I used to hide mine, I don't know. Some devices don't like to connect to hidden SSIDs and the benefit was questionable, so I started broadcasting again. You have to weigh the odds of an intrusion and the impact vs. the hassle. If you have a lot of personal data you really want to protect on a computer that doesn't leave the house plus you had mobile devices but don't want them networked together you can always create a second network.

Message edited by author 2013-01-23 22:50:50.
01/23/2013 10:41:15 PM · #23
Originally posted by lawrysimm:


6) enable MAC address filtering... This is where you can essentially list specific devices that are allowed to connect to your network. It needs a bit of management every time you want to add a new device to your network but it gives you strong control


Just remember, NOTHING can connect to your netowork until the MAC address has been added. If you get a new device or a friend comes over you will have to log onto the router and add the MAC address.
01/23/2013 11:01:36 PM · #24
Originally posted by Zeissman:

Originally posted by lawrysimm:


6) enable MAC address filtering... This is where you can essentially list specific devices that are allowed to connect to your network. It needs a bit of management every time you want to add a new device to your network but it gives you strong control


Just remember, NOTHING can connect to your netowork until the MAC address has been added. If you get a new device or a friend comes over you will have to log onto the router and add the MAC address.

I got a brand new Vaio laptop last year. It connected itself to my LAN before I even had a chance to read its MAC! MAC address filtering is useless.
01/24/2013 12:38:42 PM · #25
Originally posted by IAmEliKatz:

Originally posted by Ann:


One of my coworkers spent an entire Christmas break trying to break into some neighbor's wifi that had the SSID "Get your own wifi, b*tch!" He eventually got in, but it took 11 days on a 128 core blade server to break the password. Once he got in, he changed the SSID to something else that was even more unprintable, changed the password, and went back to using his own wifi.


11 days??? He needs some new software.


It took 11 days to build the multi-terabyte rainbow table that it took to crack the password. Once the rainbow table was built, I think he cracked the password in less than 10 minutes.

Pages:  
Current Server Time: 04/19/2024 03:12:09 PM

Please log in or register to post to the forums.


Home - Challenges - Community - League - Photos - Cameras - Lenses - Learn - Prints! - Help - Terms of Use - Privacy - Top ^
DPChallenge, and website content and design, Copyright © 2001-2024 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 04/19/2024 03:12:09 PM EDT.