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 1MF470-0004mK-3v for garchives@archives.gentoo.org; Fri, 12 Jun 2009 10:36:01 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7031FE0510; Fri, 12 Jun 2009 10:35:52 +0000 (UTC) Received: from india533.server4you.de (india533.server4you.de [85.25.151.41]) by pigeon.gentoo.org (Postfix) with ESMTP id 19E93E0510 for ; Fri, 12 Jun 2009 10:35:52 +0000 (UTC) Received: from [192.168.0.17] (pD95FD9E1.dip.t-dialin.net [217.95.217.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by india533.server4you.de (Postfix) with ESMTP id BFF9B770619 for ; Fri, 12 Jun 2009 12:35:50 +0200 (CEST) Message-ID: <4A322F86.5000700@smash-net.org> Date: Fri, 12 Jun 2009 12:35:50 +0200 From: =?ISO-8859-1?Q?Norman_Rie=DF?= User-Agent: Thunderbird 2.0.0.21 (X11/20090430) 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 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> <49bf44f10906111904k46fd0fcbra0742098340f1f89@mail.gmail.com> In-Reply-To: <49bf44f10906111904k46fd0fcbra0742098340f1f89@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: cde2e08b-aa54-4063-aec5-b9106944bd7f X-Archives-Hash: 0507ab1a697afc2e01e43c7af5ab96db Grant schrieb: >> 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 adress, >> 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? > > wlan0 in master mode does _not_ have an IP adress. So far eth0 is the only ip adress your device has. If you do not spezify a local ip adress on eth1, you will not have any local ip adress. >> 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 shorewall >> 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 > > You can let shorewall depend on hostapd, so your shorewall starts after hostapd and your wlan0. Check the "depend()" section in shorewalls rc-script.