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.
