27 May
2013
27 May
'13
8:43 p.m.
I think, if the heuristics to make the decisions are enough good, they
should work for all (or most) of the hardware devices.
For this cases, where the specific hardware have some strange stuff
(like tplink wdr4X00) maybe the best choice is to have a module named
(for example) addons.lua which have some specific functions to configure
some specific hardware. The HW model can be taken from /proc/cpuinfo.
By the way, if I'm not wrong there is a way to use the tplink switch
with Kernel VLANs, the trick is use the tag 0 (in the switch conf) for
the ports you want to use it. I should ask the gay who is dealing with
it in qMp.
On 27/05/13 22:30, Gioacchino Mazzurco wrote:
On Monday 27 May 2013 22:20:38 Pau wrote:
--
./p4u
I agree, the system should be 100%
auto-configurable. So the user can
download a generic image, install it and enjoy it. This is the same
approach we are following in qMp.
So the 3 previous firmware from us ( also
eigennet was completely autconf )
followed the same approach, but how to solve problem bounded to specific models
like black tplink ? ( on those devices it is a little trinky to make work vlan
on the switch because the eth0 and eth1 are not existent but are created
trought utagged vlan moreover the hardware switch has some limitation with
tagged vlan )
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev