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 1MEwDc-000679-IK for garchives@archives.gentoo.org; Fri, 12 Jun 2009 02:10:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7BE77E04D3; Fri, 12 Jun 2009 02:10:10 +0000 (UTC) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by pigeon.gentoo.org (Postfix) with ESMTP id 26FE2E04D3 for ; Fri, 12 Jun 2009 02:10:10 +0000 (UTC) Received: by ewy9 with SMTP id 9so2031805ewy.34 for ; Thu, 11 Jun 2009 19:10:09 -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=7JrY+3I025JOpZwPLlWuoo1ni7ANfYDk1O+Xrua34Lg=; b=TQSHxo1k00gCwSKCe7rCfMDcYRPKJaAVEzVDOHrhMdMOZrSvTOq9Ud1nye271VWxBe BXqrvgTmU70nyezUneWbgvjSXCRRpmCkKdlRqOoL2ZB3e7rrdsC53fR7sl0y3MIIZyav +vJPNsBzbAYgx6MwsnIrAxqeIhdw1alTBV0AA= 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=x4nQlcE2qAJ3uX69AO59R0gobWIDN/ZuvnZz223lVDQ+AC9TzFB1Q5dUQ1TmH7BxqV 1KvpyfEO2+E/p7ii4ShR5qu3bbAjKP7HqKUMZDYXYRmsvCmF62q14YS/oyKbaY3gn4MH zLdRYqvN1nJEaP+1qyxfAY+zS1E9N1eU7XWb0= 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.210.39.8 with SMTP id m8mr231983ebm.16.1244772609557; Thu, 11 Jun 2009 19:10:09 -0700 (PDT) In-Reply-To: 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> Date: Thu, 11 Jun 2009 19:10:09 -0700 Message-ID: <49bf44f10906111910t3f641d40v4e030df7027efbe7@mail.gmail.com> Subject: Re: [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) From: Grant To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 1ee854eb-e4f6-46f1-9988-b5a708ffe8ad X-Archives-Hash: dad9022500f2d82f0dd3cde432e7f532 >>>> I've almost got this working, but I don't know what to include in the >>>> /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 >>>> device or configuration. =A0Do I need one? =A0If I leave INTERFACES em= pty >>>> and I don't start net.wlan0, I don't have a way to define the IP >>>> address for the AP, and shorewall's "loc" zone is empty because >>>> net.wlan0 hasn't started. >>> >>> 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. > > Hi there, > > I haven't used Shorewall, but for this you probably want to use bridging.= I > fear that may not be available in Shorewall's UI. > > I originally wrote = , > but that was some years ago now. It has had many contributions since, but= I > have no idea if it's up to date. > > Anyway, using the "simple NAT-forwarding setup" described in that article > (surely possible in Shorewall) the wireless laptop can access the interne= t > and wired PCs on the LAN. However it is not possible for wired PCs to (sa= y) > browse to file shares on the laptop without port-forwarding - because you > use a NAT, you have exactly the same problem as accessing your home-serve= r > from the office. > > Bridging brings the wireless clients *seamlessly* into the wired LAN - th= ey > behave exactly like the wired clients do. One can install Apache on the > wireless laptop and immediately connect to it from a wired PC. This is ho= w > all standalone ADSL wireless routers (eg Netgear DG834G) operate. > > I can't be of much practical help, as I have for some time been using a F= on > access-point, which is plugged into a network switch near my desk and whi= ch > gives me NATted wifi. It works, but I sure do miss teleportd > , which is crippled without > bridging. > > Stroller. Thanks Stroller. I'm into bridging eth1 and wlan0, but the truth is I don't even have an eth1 right now, although I plan to in the future. When I get eth1 going I'll bridge em for sure. - Grant