On Friday, December 19, 2014 08:23:02 PM Pau wrote:
1) The firewall problem is not yet fixed, so raw
images which does not
include the firewall packet are not properly working.
In fact the code doesn't really take advantage of openwrt firewall, we actually
depend on it on arbitrary choice
i don't like openwrt firewall, and in my experience has caused more problems
than solutions, I propose to abstract the linked code so it doesn't depend on
unnecessary openwrt firewall
In any case it should be a dependency of lime-proto-anygw and not of lime-
2) Last OpenWRT/trunk does not have the iptables nat
(CONFIG_PACKAGE_kmod-ipt-nat) by default enabled (WTF?), so it should be
added as dependency for lime-system. May be also related with the
default strip kernel/libraries options (which comes enabled).
It seems strange to me... maybe the suggested way of doing MASQUERADing as
changed and nftables should be used instead of iptables ?
BTW it should be a dependency of lime-proto-wan and not of lime-system
3) Would be nice to write the current options (even if
they are the
default ones) to /etc/config/lime once the lime-config script is
executed. So it should 1) use the options specified in the file 2) fill
the non-specified options. Then in the config file you got a picture of
the current whole system configuration, when you upgrade the node these
options are preserved and the node is configured in the same exact way
it was before.
This has already been discussed in the past I believe
4) Is there any way to specify: "do no configure
(or ignore) this radio
device" to lime-config?
Yes using mode manual same goes for network interface using proto manual
it is documented in /etc/config/lime
5) In my tests, when I try to set some parameters for
a specific radio
device (i.e only radio1), lime-config crashes. My first thought is that
if there is a specific configuration for radioX, lime-config expect to
find all the needed parameters there. I think it should try to find
first the parameters in the specific configuration and afterwards (if
the parameter does not exist) look in the generic/default wifi
I don't remember if with the actual architecture this is simple to do, if not
i wouldn't change it because it seems to me quite a corner case