As Hnyman noted in https://github.com/dtaht/ceropackages-3.10/issues/13
we carry a few unnecessary dependecies in sqm-scripts, so remove one of
them (iptables-mod-filter) as we neither use it nor plan to use it.
Signed-off-by: Sebastian Moeller <moeller0@gmx.de>
The initial conversion to restart sqm on interfaces it is configured
for in case of (transient) dis- and reappearance was half finished.
These changes clean up the handling of exlicitly passed interfaces
in run.sh: no second argument defaults to all configured interfaces
the alternative is an individual interface name passed as 2nd
argument to run.sh. The first argument either is start or stop.
No argument at all will behave as if start was passed.
Survives light testing...
Signed-off-by: Sebastian Moeller <moeller0@gmx.de>
Alan Jenkins noted a bug in the smq luci GUI that effectively
erased several configuration paramters if two checkboxes were deselected.
This behaviour seems consistent in luci but certainly has the potential
to confuse users. While confusion can not really be avoided generally
it seems wise to change the default interpretation for empty or non-existent
itarget and etarget variables from the qdisc's default (5ms in the case of
one of the codels) to automatic determination of tghis variable dependent on
the configured bandwidth, as codels target variable should be large enough
to contain at least one full packet. With this change sqm-scripts will
do the right thing by default, but will yet allow the user to specify
over-ridding values (as long as the user does not un-check the
entry-field exposing check boxes). Survives light testing...
This change set also changes the sqm-scripts luci gui to note the user
of the change. For compatibility with existing setups sqm-scripts
will still honor "auto" as an alternative explicit way of requesting
automatic target selection. This might turn into a warning in the future
and might be phased out...
Signed-off-by: Sebastian Moeller <moeller0@gmx.de>
Backport of luci-app-sqm package from trunk.
I have been using it in my BB14.07 build without any problems.
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
Backport of sqm-scripts package from trunk.
I have been using it in my BB14.07 build without any problems.
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
The Makefile already uses the proper autoreconf fixup but leaves a manual
autoconf invocation in place.
The bad autoconf call leads to the following build error in the SDK:
configure.ac:3: installing `./config.guess'
configure.ac:3: installing `./config.sub'
configure.ac:20: installing `./install-sh'
configure.ac:20: installing `./missing'
src/Makefile.am: installing `./depcomp'
autoreconf: Leaving directory `.'
aclocal...
autoheader...
libtoolize... libtoolize nor glibtoolize not found
make[2]: *** [.../.configured_] Error 1
Remove the entire Build/Configure override to let libtorrent build correctly.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
The Makefile already uses the proper autoreconf fixup but leaves a manual
autoconf invocation in place.
The bad autoconf call leads to the following build error in the SDK:
( cd .../rtorrent-0.9.4-git; ./autogen.sh );
aclocal...
autoheader...
libtoolize... libtoolize nor glibtoolize not found
make[2]: *** [.../rtorrent-0.9.4-git/.configured_] Error 1
Remove the entire Build/Configure override to let rtorrent build correctly.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
Fixed issue in mwan3 status output with mwan3 interfaces not yet configuerd in network config
Removed nexthop argument as it is no longer used
Signed-off-by: Jeroen Louwes <jeroen.louwes@gmail.com>
Invoke the generic autoreconf fixup instead of calling the shipped autogen.sh.
This ensures that proper variants of libtoolize, autoconf, automake etc. are
used, otherwise it is not possible to rebuild protobuf-c in the SDK env.
The change requires backport to BB as it currently blocks the rebuild of ocerv.
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
Compilation of libxml2 on some distributions is problematic (at least
archlinux) for OpenWrt. This commit fixes the issue. Issue is caused
because configuration for some reason does not find gzopen from zlib.
This patch issues linker to include zlib anyway, if host system doesn't
have this issue, it is not a problem as linker should not link libs
twice anyway.
Signed-off-by: Oskari Rauta <oskari.rauta@gmail.com>
Backported to BB to fix https://dev.openwrt.org/ticket/18295
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
Fix issue where config file would be overwritten in some cases
Fix issue where local address of wan point-to-point links were unreachable from lan
Signed-off-by: Jeroen Louwes <jeroen.louwes@gmail.com>
