Grant schrieb:
Thanks for the clarification Norman :-)
ok, I removed net.wlan0 so it doesn't start up anymore. My computer
booted
up and all the services are working the way they should, however I am
having a problem getting hostapd to start. Here is the error I get when
I
tried to start up hostapd...
penguin ~ # /etc/init.d/hostapd start
* Bringing up interface wlan0
* Configuring wireless network for wlan0
* Scanning for access points
* no access points found
* Failed to configure wireless for wlan0
* ERROR: net.wlan0 failed to start
* ERROR: cannot start hostapd as net.wlan0 would not start
It's suppose to be an access point, not scanning for one so do you have
any idea what I should do now?
Did you remove wlan0 from the /etc/conf.d/hostapd file?
No, should I just leave it empty?
INTERFACES=""
What about /etc/hostapd/hostapd.conf?
Do I leave it like this...
interface=wlan0
...or remove that line too?
INTERFACES should at least contain the bridge device. The wired NIC does not
hurt either.
In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which device it
has to initialize, so leave it like this.
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. Do I need one? If I leave INTERFACES empty
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.
- Grant
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 connected
and can not connect to your wired systems.
