From owner-freebsd-questions@FreeBSD.ORG Mon Oct 31 18:44:52 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5323816A41F for ; Mon, 31 Oct 2005 18:44:52 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8535043D48 for ; Mon, 31 Oct 2005 18:44:51 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j9VIinem008308; Mon, 31 Oct 2005 20:44:50 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j9VIinol001720; Mon, 31 Oct 2005 20:44:49 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j9VIinC7001719; Mon, 31 Oct 2005 20:44:49 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 31 Oct 2005 20:44:49 +0200 From: Giorgos Keramidas To: Stijn Hoop , freebsd-questions@freebsd.org Message-ID: <20051031184449.GA1690@flame.pc> References: <20051031182539.GA52720@pcwin002.win.tue.nl> <20051031182851.GB1428@flame.pc> <20051031184058.GB52720@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051031184058.GB52720@pcwin002.win.tue.nl> Cc: Subject: Re: cannot get IP working between associated ath0 & AP, what to do? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 18:44:52 -0000 On 2005-10-31 19:40, Stijn Hoop wrote: > On Mon, Oct 31, 2005 at 08:28:51PM +0200, Giorgos Keramidas wrote: > > > Any hints on where I might go from here to debug this? I know the > > > setup should work because in a previous life [1] it Worked With > > > Windows[TM] (and on the same AP). > > > > You haven't firewalled everything off, right? > > Good call! I certainly hope not. I haven't touched the AP since > getting it working with the same laptop in Windows, at least none of > its firewall rules. I'll triplecheck asap though. Make sure you're not running a BSD firewall too, like the one I had a few days ago and kept failing to obtain an address from my wireless AP at home because of the paranoid ruleset I was using :)