From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MEw8u-0005r0-DN for garchives@archives.gentoo.org; Fri, 12 Jun 2009 02:05:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6E501E0424; Fri, 12 Jun 2009 02:04:49 +0000 (UTC) Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.152]) by pigeon.gentoo.org (Postfix) with ESMTP id 48FDFE0424 for ; Fri, 12 Jun 2009 02:04:49 +0000 (UTC) Received: by yw-out-1718.google.com with SMTP id 5so7204351ywm.46 for ; Thu, 11 Jun 2009 19:04:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=HI8fKavI272rgutwUa8Wq5rdHJ1kz5UsTHT83WopiFQ=; b=K8QTKRUgmT0920LfWwNWvRoJsGzOe4RPfnKIpBDHq2rllT9HqhuL5lqRjTDdL5dxy3 JuxMa81B7B+Lw1dCrB9DVyqT79D2508328F4G483ksBhN/teL2ilcdvHk89V9mxbyGh1 ZJ6qO37zJLZSnGAG09cT9QJ9dZywL6fcrGmhs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Mm5YFX8Kw8+fxPNBGAQ5CgjdVy7dVZTxeVMJ85io8QKJ3cJBtSSfp+wZzwafyqA7sp bI5CbZntbxHMMgR3kB7hqBdc+EV8zg28PBKbWKp54TWlVjPF+00N2cMjaCBbFgVToz0q iM1e0bx0wIw4q0IhZhCi0mmLVzzUAdGgYhRZs= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.90.73.17 with SMTP id v17mr2705984aga.37.1244772288937; Thu, 11 Jun 2009 19:04:48 -0700 (PDT) In-Reply-To: <4A31A461.20700@smash-net.org> References: <000606ca6620ef53cdcd6e935ccf6c4b.squirrel@jasoncarson.ca> <4A2EFFEE.6070803@smash-net.org> <22e332067298a86dc79f6def4e071ee3.squirrel@jasoncarson.ca> <4A2F8CEF.6070600@smash-net.org> <4A3011EA.9000908@smash-net.org> <49bf44f10906111513x4f177e37g6570a512256bee0a@mail.gmail.com> <4A319419.4000502@smash-net.org> <49bf44f10906111638y3725fe35s146a4c2f25ea3db7@mail.gmail.com> <4A31A461.20700@smash-net.org> Date: Thu, 11 Jun 2009 19:04:48 -0700 Message-ID: <49bf44f10906111904k46fd0fcbra0742098340f1f89@mail.gmail.com> Subject: Re: [gentoo-user] Atheros kernel driver and my wireless access point setup From: Grant To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 0e4e69de-5d66-440b-85d5-622efd739347 X-Archives-Hash: f5cfac4f47596c3383a66f3913864fc4 >>> What do you want to do with your accesspoint. You will need a bridge to= a >>> wired network if you want your ap attached to that wired network. This = is >>> quite usual though... >>> Without a bridge to a wired network, only the wlan systems are connecte= d >>> and >>> can not connect to your wired systems. >>> >> >> That's no problem, I'm OK with keeping eth1 and wlan0 separate. =A0Right >> now I just want to get wlan0 working. =A0Do you know how to do that? =A0= I >> can't start net.wlan0 because it chokes on master mode, so I don't >> know how to specify an IP for the AP or how to fill shorewall's "loc" >> zone as that is normally filled by net.wlan0. >> >> - Grant >> >> > > Leave INTERFACES blank. As you keep the networks seperated, hostapd does = not > depend on any other devices. > wlan0 is initialized by hostapd. So you are good to go. > The accesspoint itself, so to say the wlan part does not have any IP adre= ss, > at it is merely a connectionpoint for normal wlan systems. The IP adress = to > your device however is defined by the other nics. In your case eth1. I don't have eth1 set up yet. For now I just want eth0 on the WAN and wlan0 on the LAN. eth0 dhcp's from my ISP, but I need to specify a local IP address for my LAN somewhere right? > For the shorewall business, you have to tell, what you want to do with > shorewall exactely. > I dare say you have a wlan zone as your AP and a loc zone with eth1. As i= am > using bridging i can not tell you if and how shorewall responds. > But if you want to keep eth1 an wlan0 seperate, what so you need shorewal= l > for? Since the AP system is also the router, I use shorewall for NAT, port closing, port forwarding, and packet shaping. shorewall gives an empty loc zone error if I don't have net.wlan0 started because wlan0 is the only loc interface. - Grant