Philip Prindeville wrote:
> Terry Markovich wrote:
>   
>> Darrick Hartman (lists) wrote:
>>   
>>     
>>> Kristian Kielhofner wrote:
>>>     
>>>       
>>>> On 4/21/08, Kevin Kiely <[EMAIL PROTECTED]> wrote:
>>>>       
>>>>         
>>>>> Does anyone know if any of the wireless USB adapters are supported with
>>>>>  ASTLinux, like the Netgear WG111?  If so, which are know to work well
>>>>>  natively with ASTLinux?
>>>>>
>>>>>  Thanks,
>>>>>
>>>>>  Kevin
>>>>>
>>>>>         
>>>>>           
>>>> Kevin,
>>>>
>>>>   Just about any cards supported by Linux should be supported by
>>>> AstLinux.  Due to the generic nature of chipsets it's tough to say
>>>> which brands are supported.
>>>>
>>>>   However, if I were you I'd look out for something Atheros based
>>>> (supported by madwifi).
>>>>       
>>>>         
>>> Kevin,
>>>
>>> Before you put too much effort into this, Astlinux does not implement 
>>> WPA_supplicant in anyway, so the best encryption (if you call it that) 
>>> is WEP.  It's something on the list to do, but not near the top yet.  If 
>>> the encryption is not important, then as Kristian said, the chips 
>>> supported by madwifi probably would be your best choice.
>>>
>>> Darrick
>>>     
>>>       
>> I have built hostapd (0.5.10) for astlinux 1.2, which provides wpa/wpa2 
>> and works really well.  I built it with madwifi-ng r3349-20080212.
>>
>> I modified the hostap makefile quite a bit, I'll provide it if anyone is 
>> interested.
>>
>> Terry
>>   
>>     
>
> I was trying to build and use this, but there are various issues.
>
> For instance, the WIFI_ENABLE, WPA_ENABLE, and WPA_KEY variables are 
> left out of /etc/rc.conf.
>
> Also, the canned /stat/etc/hostapd.conf has the bridge and interface 
> hard-coded into it.
>
> Also, does it make sense to have $AP0 and $ATH0 *both* set?  Or should 
> this be either/or?
>
> The links in /etc/runlevels/default/S??hostap are missing, so 
> /etc/init.d/hostap never gets run.
>
>  From what I can, you also can't have one key set for $AP0, and another 
> for $AP1, etc.
>
> Is there a reason to not just have:
>
> ATH0="wifi0:ssid:channel:enc-method:enc-key-#:passkey"
>
> for instance?
>
> -Philip
>   

One other question...  For the WIFIMODS... there's no way to pass in 
parameters for modprobe.  I'm thinking we should change the delimiter 
from space to semi-colon or comma (some arguments take comma-separated 
values, so semi-colon is the least problematic).

Maybe also change the name from WIFIMODS to WIFI_MODS so we can detect 
configs that haven't been updated.

Thoughts?

-Philip






-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to