[haiku-development] Re: Breaking down wireless stack in tasks

"Fredrik Holmqvist" <fredrik.holmqvist@xxxxxxxxx> wrote:
> I'm trying to break down how to integrate wireless into our network 
> stack.
> (This might be complety flawed, please bear with me)

I guess this heavily depends on how you do it, and what you want to 
achieve as short targets.
I for one would start by porting a FreeBSD WLAN driver and extend the 
FreeBSD compatibility layer as needed, but, if at all possible, mostly 
separated from the existing layer.

Then I would see how to best integrate that functionality with the rest 
of the stack (possibly with a dedicated device module), and wrap an 
Haiku-like API around the wireless stack to be used for native drivers. 
Inbetween I would make the features available through ifconfig, and 
later the net_server as well.

Basically, there should be adapter agnostic wireless configurations, 
and the net_server will then try them (if configured to do so) one by 
one (starting with the strongest), until it found a suitable one.
The NetworkStatus should be extended to make that info available, as 
well as to show all networks in range.
When a wireless network is being configured, the networking stack 
should try the different options itself (unless instructed otherwise), 
instead of assuming the user would know the difference between WPA, 
WEP, TKIP and whatever else.

Bye,
   Axel.

Other related posts: