From owner-freebsd-questions@FreeBSD.ORG Sun Dec 29 16:06:41 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74F57D09 for ; Sun, 29 Dec 2013 16:06:41 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EED8B1EDB for ; Sun, 29 Dec 2013 16:06:40 +0000 (UTC) Received: from [192.168.1.35] (host86-161-162-125.range86-161.btcentralplus.com [86.161.162.125]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id rBTG6cOp015877 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 29 Dec 2013 16:06:39 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52C0488E.4090006@fjl.co.uk> Date: Sun, 29 Dec 2013 16:06:38 +0000 From: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: IT security and pentesting tools on FreeBSD References: <20131229143625.b3f3a2cf.freebsd@edvax.de> <52C04198.5070102@fjl.co.uk> <20131229165032.6b82d8a0.freebsd@edvax.de> In-Reply-To: <20131229165032.6b82d8a0.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Dec 2013 16:06:41 -0000 On 29/12/2013 15:50, Polytropon wrote: >> >As to the MAC address, easy. Something like: >> > >> >ifconfig bge1 link EE:EE:EE:EE:EE:EE >> > >> >It'll either work, or it won't work. > What does its working depend on? Has it to be a specific feature > or functionality of the wireless card? Yep - the hardware and the driver need to support the feature. I'm pretty sure that most modern adapters do, but the drivers may be a bit behind. FWIW I just tried it on a Broadcomm, and it worked (after the ARP cache timed out!). I'd guess most wireless NICs are fairly new and therefore support it, but you'll just try it and see - and try a different card if the first one doesn't work. It's not something do all the time so I don't have a list. Regards, Frank.