public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Locking down a wireless network
Date: Thu, 29 Jan 2009 14:11:35 -0600	[thread overview]
Message-ID: <58965d8a0901291211q466588cdj51a2ae75538e5908@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0901291011i488de5a9haee5f369637d861d@mail.gmail.com>

On Thu, Jan 29, 2009 at 12:11 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Thu, Jan 29, 2009 at 9:40 AM, Grant <emailgrant@gmail.com> wrote:
>> My Gentoo router's wireless network is encrypted via WPA and doesn't
>> DHCP.  I'd like to take this a step further in case my WPA key gets
>> hacked.  Can I issue only certain IPs to certain MAC addresses?
>>
>> Does WPA2 require hardware support?
>>
>> - Grant
>
> My LinkSys wireless router supports MAC address filtering. I can add a
> MAC address to the allowed list and disallow everything else. It works
> for us so far, until someone manages to somehow find out an allowed
> MAC address and pretends to be that address. I'll deal with that
> should it ever happen. Unlikely I think...
>
> It is a little extra work adding a new device in as I have to discover
> its address but that's OK with me.
>
> I don't think is typically done in hardware as the specs change and
> hardware designers are reluctant to put the gates in. More likely it's
> done in firmware on a router like mine, or software if you're using
> some Gentoo box to do a job like this.

Well, using kismet to sniff out active MAC addresses of clients and
access points is dead simple, and MAC spoofing is even easier (emerge
net-analyzer/macchanger). Obviously trying to use a MAC that's already
active could result in collisions/IP conflict so the drive-by wifi
hijackers probably won't get much use of it, but if someone is doing
an attack on you they can wait for your laptop to be turned off or
wireless traffic idle, and then hop on that MAC and get in your
network. Even that should not be a problem if you've got eveything
else secured (like, if you allow passwordless entry to samba shares
from local address, and someone gets on your wireless, that could be
bad unless you put wifi in a different vlan or whatever). I don't have
mine set up that sophisticated, I am putting my faith in WPA2 being
strong enough to keep out intruders. I know I should probably be more
careful but I'm trusting and lazy. :) My internal devices are not
necessarily protected from each other.

I don't use MAC filtering, but I have the DHCP leases tied to MAC
addresses; I don't restrict it only to those addresses though. I have
a range (192.168.0.101-109) for reserved IP addresses, and dynamic
from 110+. My main desktop has 2 NICs and Wifi, second desktop has 2
NICs, Laptop has NIC & Wifi, cell phone has Wifi, land phone is Voip,
I have a second wireless router set up as a wireless bridge to which
my Xbox, Xbox 360 & Slingbox are attached, as well as any visitors who
happen to need to plug in a laptop in my living room. :) I let some of
my devices get dynamic IPs just because it doesn't matter (vonage,
slingbox, xbox 360) but the PCs I like to have well-defined addresses.



  reply	other threads:[~2009-01-29 20:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 17:40 [gentoo-user] Locking down a wireless network Grant
2009-01-29 17:47 ` Dan Cowsill
2009-01-29 17:50 ` Paul Hartman
2009-01-29 20:30   ` Grant
2009-01-29 20:39     ` Saphirus Sage
2009-01-29 20:39   ` Grant
2009-01-29 20:48     ` Saphirus Sage
2009-01-29 20:58     ` Paul Hartman
2009-01-29 21:02       ` Saphirus Sage
2009-01-29 22:15       ` Grant
2009-01-30 16:25       ` Grant
2009-02-03 21:22         ` Paul Hartman
2009-01-29 18:11 ` Mark Knecht
2009-01-29 20:11   ` Paul Hartman [this message]
2009-01-30 22:37 ` Stroller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58965d8a0901291211q466588cdj51a2ae75538e5908@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox