Hi,

>>> Should we keep it this way, or will be webif2 for our new network
>>> configuration ready in a few weeks?
>> Ok, maybe this was a bit misunderstanding... It's ok for me to fully
>> drop nvram support now to get a clean base release 1.0.
> 
> For that I would like to get results, if we manage to use special
> security feature for the wireless part working without nvram.
> Like WEP, WPA and WPA2. I will include the util "wl" so we can use 
> "up" statements in interfaces.
ok, for that nvram might be mandatory on some devices.
I mean get rid of it for non-hardware configurations like network stuff
and daemon configs.

>> I'd like to take a deeper look to the buildroot-ng style with an
>> /etc/config directory for that as it simplifies the webif
>> development A LOT!!
> 
> I think we will go another way. I have discussed an idea with some
> friends of mine. I will describe the idea, if I cleared it up.
Why do you want to reinvent the wheel? This stuff is not OpenWRT only
even the guys at Fraunhofer work with it. Some scripts are worked out by
them and Felix.

>> So, please get rid of nvram and don't support both. Webif may even be
>> backported to 1_0 if it works. It's not that important.
> 
> Hmm. Webif is not important for me, but may be we can attract more
> people to FreeWRT if we have one.
Yes. And there already is a webinterface project with x-wrt. But we can
only benefit from it when we try to be more compatible in the backend.
It's more easy to switch webif to /etc/config/* than to rewrite it.

/Markus

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers

Reply via email to