From owner-freebsd-net@FreeBSD.ORG  Mon Sep  8 10:19:00 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B2D2A16A4BF
	for <freebsd-net@freebsd.org>; Mon,  8 Sep 2003 10:19:00 -0700 (PDT)
Received: from srv00.el.com.br (srv00.el.com.br [200.179.165.123])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 20AE843F93
	for <freebsd-net@freebsd.org>; Mon,  8 Sep 2003 10:18:59 -0700 (PDT)
	(envelope-from npd@el.com.br)
Received: from intranet.el.com.br (srv00.el.com.br [200.179.165.123])
	by srv00.el.com.br (elsmtp) with SMTP id A225170E39
	for <freebsd-net@freebsd.org>; Mon,  8 Sep 2003 14:18:34 -0300 (BRT)
Received: from 172.72.12.194
        (SquirrelMail authenticated user npd)
        by intranet.el.com.br with HTTP;
        Mon, 8 Sep 2003 14:18:34 -0300 (BRT)
Message-ID: <49569.172.72.12.194.1063041514.squirrel@intranet.el.com.br>
Date: Mon, 8 Sep 2003 14:18:34 -0300 (BRT)
From: npd@el.com.br
To: freebsd-net@freebsd.org
User-Agent: SquirrelMail/1.4.1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
Subject: Re: Was: No subject
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2003 17:19:00 -0000


> Doesn't turning on WEP and MAC addressing filtering stop them from
> associating with your AP?

   That's the problem Jeffrey: No. They're our real Internet clients. No
problems with it.
   The problem is that the add a second ip to their nic and use the
physical WLAN to build a VPN. The AP has a MAC filtering capability,
but it doesn't associate it with an IP :(
   Another question just raised: Even if I build a HostAP, will I be able
to block them of doing this?

   Thanks,

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Paiva, Gilson de        Domingos Martins
 mailto:npd@el.com.br    Brazil
 http://www.el.com.br/   E&L Producoes de Software
 http://www.FreeBSD.org/ FreeBSD: The Power to Serve
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=