> The webif story:
> What to do with webif/webif2 for 1.0? Some days ago I talked to
> Markus and he said, he needs webif for some projects, so I decided
> to keep nvram based network configuration and webif in parallel to
> our new network configuration. 
> 
> 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.

I tried to investigate the x-wrt work and the buildroot-ng stuff and
noticed that x-wrt goes heavily the OpenWRT way and hangs on with
Whiterussian for now.

In webif2 I started to take what I found usuable from x-wrt and
cleaned it up for a first shot. Next I'm thinking about rewriting
the network config stuff to interact with the "interfaces" file.

What still keeps missing is a kind of registry for the other stuff:
ntp-Server, syslog settings, timezone, dhcp settings ...

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!!

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.

WBX:
please don't use "eth0" in /etc/network/interfaces try to always use
the vlan-interface eth0.0 and configure the ports for our supported
devices.

bye,
  Markus

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

Reply via email to