Backport of r39212
Signed-off-by: Rafał Miłecki
---
I've noticed folks on OpenWrt forum being unhappy because of lacking
backport of r39212:
https://forum.openwrt.org/viewtopic.php?id=39956&p=10
Of course noone decided to handle that. There is my try.
Compile-tested only.
---
.../561-ath9k-ar93
hi All,
I’ve been a user and light developer of OpenWRT for many years, but have begun
my first full blown project with OpenWRT a few months ago. I’m very comfortable
with the overall build process, patching, BSP specific files, etc. etc. but am
having a hard time grasping the overall workflow
start_daemon_for_all_ddns_sections expects a event interface argument
from hotplug event [1]. But init script cannot pass such a thing. Let
the argument default to `wan' to solve this.
[1] 7e76203 [packages] ddns-scripts: add an option to specify the used
interface - default to wan to retain com
/sys/kernel/debug/ is now only accessible to root,
use zabbix_helper_mac80211 (suid helper) to compute
mac80211.phydiscovery (the discovery rule)
Signed-off-by: Etienne CHAMPETIER
---
admin/zabbix/files/mac80211 | 2 +-
admin/zabbix/files/zabbix_helper_mac80211.c | 89 ++
Is there any plan to swith from syslogng to rsyslog in some future OpenWrt
release?
I'm investigating how to log my devices and it seams that syslogng is
subpar solution on devices that have intermittent connection.
Please correct me if I'm wrong, but with syslogng when connection goes down
syslo
Sven Eckelmann writes:
> On Saturday 18 January 2014 01:14:28 Kalle Valo wrote:
>
>> > Just as general information to the state of ath10k, my current test showed
>> >
>> > some problems with it:
>> > * Samsung GT-I9300 only got horrible slow connections to an QCA9880 but
>> >
>> >an Intel
