Remember the idea here is to use whatever the best tool is that you have, WEP is better than nothing, WPA is better than WEP and WPA2 is better than WPA. Most home networks are not that noisy so you force an attacker to use additional tools to create traffic. Use WPA or WPA2 if available (I know that WEP is "crackable" but you've got to have a lot of packets to do that. Make sure that you also change the default password(s) on the router Change the SSID to something other than what the manufacturer provided Have you got any other useful tips for home or small office wireless routers? If so, send them to us via the contact page and we'll post additional ideas here. By logging into DShield I can see graphically what is coming at my home network based on what the SOHO router is logging. I use the wired SOHO router to create my logs, from the router they go to a desktop computer with a fixed IP address, then that computer submits them to DShield once an hour. See the how-to page over at DShield for instructions. If you have one of the popular SOHO routers (Linksys, Netgear, DLink, etc.) the odds are good that they can create logs for the DShield service. This is yet another "layer" since it makes war driving from the curb very difficult with standard antennas. So if the router is below ground, the signal is fine inside the house, but drops off significantly more than a few feet away outside the house. Why put the wireless SOHO router below ground? Well, wireless signals are at 2.4GHz if you are using 802.11b/g service and at that frequency they don't travel very well through dirt. Change the default frequency (channel) to one that is not used by my neighbors Limit the number of DHCP licenses to only what I need Keep the router at or below ground level On the wireless SOHO router, I do the following for wireless protection:
#SOHO NOTES SERIAL MAC KRACK PLUS#
My IP subnetting looks like this:Ħ8.x.y.z - wired SOHO router, low (WAN) sideġ92.168.1.1 - wired SOHO router, high (LAN) sideġ92.168.1.11.15 - DHCP assigned wired hostsġ92.168.1.2 - old two port router, low sideġ92.168.2.1 - old two port router, high sideġ92.168.2.21.25 - test computers with fixed IP addressesġ92.168.1.3 - wireless SOHO router, low sideġ92.168.3.1 - wireless SOHO router, wireless sideġ92.168.3.31.35 - DHCP assigned wireless hostsīy using discipline in subnetting I have a much easier time troubleshooting problems, plus I've created a few "layers of defense" in my home network. Also, I have an old two-port router that connects to the wired SOHO router, and behind that old router is my test network on its own subnet. Being the geek that I am, there are two SOHO routers in my basement, one wired (connected to the cable modem) and one wireless (connected to the wired router.) By using two devices I can create a separately numbered wireless LAN. Wired and wireless hosts are behind the SOHO router and get their IP addresses, DNS settings, etc.
In a "typical" setup the cable modem connects to a SOHO wireless router. Nothing fancy but perfect for building a home network. I am in a "normal" suburban neighborhood, average sized wood frame house, two levels above ground plus a basement, garage, porch, etc. Dual-homing in your house tends to upset the residential ISPs so therefore let's don't go down that road today. To simplify things, let's just assume that I have one ISP.
I am on a cable modem system and also have access to a fiber optic service provided by the local telco. After all, practice what you preach, right? :) So I thought that the ideas we've come up with over the past few years would be good for discussion here.
#SOHO NOTES SERIAL MAC KRACK HOW TO#
We always get into a sidebar discussion at some point about how to safely configure your home wireless router or gateway. As most of our readers probably know, I teach SANS Security Essentials (SEC 401) about five times a year at the large SANS conferences. Today's tip focuses on small office/home office (SOHO) wireless routers.
0 kommentar(er)
