| 1 |
>>>>>> Thanks for the clarification Norman :-) |
| 2 |
>>>>>> |
| 3 |
>>>>>> ok, I removed net.wlan0 so it doesn't start up anymore. My computer |
| 4 |
>>>>>> booted |
| 5 |
>>>>>> up and all the services are working the way they should, however I am |
| 6 |
>>>>>> having a problem getting hostapd to start. Here is the error I get |
| 7 |
>>>>>> when |
| 8 |
>>>>>> I |
| 9 |
>>>>>> tried to start up hostapd... |
| 10 |
>>>>>> |
| 11 |
>>>>>> penguin ~ # /etc/init.d/hostapd start |
| 12 |
>>>>>> * Bringing up interface wlan0 |
| 13 |
>>>>>> * Configuring wireless network for wlan0 |
| 14 |
>>>>>> * Scanning for access points |
| 15 |
>>>>>> * no access points found |
| 16 |
>>>>>> * Failed to configure wireless for wlan0 |
| 17 |
>>>>>> * ERROR: net.wlan0 failed to start |
| 18 |
>>>>>> * ERROR: cannot start hostapd as net.wlan0 would not start |
| 19 |
>>>>>> |
| 20 |
>>>>>> It's suppose to be an access point, not scanning for one so do you |
| 21 |
>>>>>> have |
| 22 |
>>>>>> any idea what I should do now? |
| 23 |
>>>>>> |
| 24 |
>>>>>> |
| 25 |
>>>>>> |
| 26 |
>>>>>> |
| 27 |
>>>>>> |
| 28 |
>>>>> |
| 29 |
>>>>> Did you remove wlan0 from the /etc/conf.d/hostapd file? |
| 30 |
>>>>> |
| 31 |
>>>>> |
| 32 |
>>>>> |
| 33 |
>>>>> |
| 34 |
>>>> |
| 35 |
>>>> No, should I just leave it empty? |
| 36 |
>>>> INTERFACES="" |
| 37 |
>>>> |
| 38 |
>>>> What about /etc/hostapd/hostapd.conf? |
| 39 |
>>>> Do I leave it like this... |
| 40 |
>>>> interface=wlan0 |
| 41 |
>>>> ...or remove that line too? |
| 42 |
>>>> |
| 43 |
>>>> |
| 44 |
>>>> |
| 45 |
>>> |
| 46 |
>>> INTERFACES should at least contain the bridge device. The wired NIC does |
| 47 |
>>> not |
| 48 |
>>> hurt either. |
| 49 |
>>> In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which device |
| 50 |
>>> it |
| 51 |
>>> has to initialize, so leave it like this. |
| 52 |
>>> |
| 53 |
>> |
| 54 |
>> I've almost got this working, but I don't know what to include in the |
| 55 |
>> /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 |
| 56 |
>> device or configuration. Do I need one? If I leave INTERFACES empty |
| 57 |
>> and I don't start net.wlan0, I don't have a way to define the IP |
| 58 |
>> address for the AP, and shorewall's "loc" zone is empty because |
| 59 |
>> net.wlan0 hasn't started. |
| 60 |
>> |
| 61 |
>> - Grant |
| 62 |
>> |
| 63 |
>> |
| 64 |
> |
| 65 |
> What do you want to do with your accesspoint. You will need a bridge to a |
| 66 |
> wired network if you want your ap attached to that wired network. This is |
| 67 |
> quite usual though... |
| 68 |
> Without a bridge to a wired network, only the wlan systems are connected and |
| 69 |
> can not connect to your wired systems. |
| 70 |
|
| 71 |
That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right |
| 72 |
now I just want to get wlan0 working. Do you know how to do that? I |
| 73 |
can't start net.wlan0 because it chokes on master mode, so I don't |
| 74 |
know how to specify an IP for the AP or how to fill shorewall's "loc" |
| 75 |
zone as that is normally filled by net.wlan0. |
| 76 |
|
| 77 |
- Grant |
Archives