Hi all,
Ended up having some problems again and when I got back to my email I
noticed that I was getting a lot of 'too many bounces' notifications
even though I have whitelisted the mailing lists for LEDE. Any ideas?
Also, I noticed in the git log there were issues with older kernel
versions. I
Hi all,
The firewall package advertises utc_time uci option for firewall rules
and redirects, however, based in the iptables-extensions manpage, only
UTC time is supported by the time extension.
This matches my experience with attempting to use local timezone with
firewall rules based on time (do
On Tue, 18 Oct 2016 13:09:22 +0200
Zefir Kurtisi wrote:
> Hi,
>
> to those understanding the package dependency logic by heart, I'm
> trying to achieve something I assumed to be common, but fail to get
> there with the help of the available documentation.
>
> The short version is this:
> * pack
on 2016-10-19 Charles wrote:
> Questions:
A similar observation: With OpenWrt 15.05.1, after booting, dmesg
output contains driver messages related to regulatory domain
changes and final (I hope) settings:
> [ 10.85] cfg80211: Calling CRDA to update world regulatory domain
> [ 10.88]
On Wed, 19 Oct 2016 22:05:43 +0200
Petr Štetiar wrote:
> Felix Fietkau [2016-10-19 21:44:06]:
>
> > I'd like to know why you need to use local time for the RTC, I think
> > that's rather uncommon.
>
> You mean system time in local time, right? RTC should be in UTC and
> in current sysftime i
On Wed, 19 Oct 2016 22:05:43 +0200
Petr Štetiar wrote:
> Felix Fietkau [2016-10-19 21:44:06]:
>
> > I'd like to know why you need to use local time for the RTC, I think
> > that's rather uncommon.
>
> You mean system time in local time, right? RTC should be in UTC and
> in current sysftime i
Hi,
im new on lede and im a user, no dev. Hope its ok to ask.
I got an archer c5 flashed to a C7 (works perfect since month with openwrt).
I stumbled over messages - and i dont no if this is also on openwrt.
Looks like there are not a problem (wifi works)
root@Archer-Lede:/# dmesg | grep ath10
On 20 October 2016 at 16:12, Karl Palsson wrote:
> Rafał Miłecki wrote:
>> On 20 October 2016 at 08:11, Chris Blake
>> wrote:
>> > I agree that would work in terms of functionality, but the issue with
>> > that logic is if you hold the button over 5 seconds, the system LED
>> > will start flash
Rafał Miłecki wrote:
> On 20 October 2016 at 08:11, Chris Blake
> wrote:
> > I agree that would work in terms of functionality, but the issue with
> > that logic is if you hold the button over 5 seconds, the system LED
> > will start flashing (as expected) but then no action is taken on the
> >
On 10/19/2016 07:12 PM, Alexandru Ardelean wrote:
> On Tue, Oct 18, 2016 at 2:09 PM, Zefir Kurtisi
> wrote:
>>
>> Hi,
>>
>> to those understanding the package dependency logic by heart, I'm trying to
>> achieve something I assumed to be common, but fail to get there with the
>> help of
>> the ava
On 10/20/2016 10:20 AM, Jiri Pirko wrote:
> Thu, Oct 20, 2016 at 09:48:48AM CEST, garet...@orcon.net.nz wrote:
>> Hi Jiri
>> This is a common problem on XM devices due to new uboot on AirOS >= 5.6.x,
>> although I haven't got any XW devices to test but its possibly the same?
>> Try downgrading back
On 2016-10-19 23:49, Petr Štetiar wrote:
> Hi Felix,
>
> it seems like that this autoconnect feature is causing some regressions and a
> headaches to few people :-) I'm talking about this commit in particular:
>
> Author: Felix Fietkau
> Date: Thu Sep 22 20:07:45 2016 +0200
>
>
It used to only do the sync+reboot for button presses less than 1
second. jffs2reset and reboot for button presses longer than 5
seconds, and _nothing_ for presses between 1 and 5 seconds.
(Potentially leaving room for someone else to add some other
hook, but realistically just useless)
I noticed
Rafał Miłecki wrote:
> On 19 October 2016 at 16:59, Chris Blake
> wrote:
> > diff --git a/package/utils/beep/Makefile b/package/utils/beep/Makefile
> > new file mode 100644
> > index 000..b9bb4d80
> > --- /dev/null
> > +++ b/package/utils/beep/Makefile
> > @@ -0,0 +1,50 @@
> > +#
> > +# Cop
Because there are two versions of this device there are two different $board
values cf-e380ac-v1 and cf-e380ac-v2, however there is one struct for gpio's in
the corresponding mach file referencing cf-e380ac. What would be the procedure
or protocol to follow here in regards to using $board in di
Refresh patches for all targets that support kernel 4.4.
compile/run-tested on cns3xxx & imx6.
Signed-off-by: Koen Vandeputte
---
include/kernel-version.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 2452f6d.
Thu, Oct 20, 2016 at 09:48:48AM CEST, garet...@orcon.net.nz wrote:
>Hi Jiri
>This is a common problem on XM devices due to new uboot on AirOS >= 5.6.x,
>although I haven't got any XW devices to test but its possibly the same?
>Try downgrading back to AirOS v5.5.11 or less or apply the following pat
Hi Jiri
This is a common problem on XM devices due to new uboot on AirOS >= 5.6.x,
although I haven't got any XW devices to test but its possibly the same?
Try downgrading back to AirOS v5.5.11 or less or apply the following patches
which I can confirm fix the problem on my XM devices.
https://raw
Hi.
Trying Ubiquity power beam M5. According to the instructions on openwrt
wiki, I'm using loco m5 firmware. All looks fine, only configuration is
lost after every reboot.
Tried:
openwrt-15.05.1-ar71xx-generic-ubnt-loco-m-xw-squashfs-sysupgrade.bin
openwrt-15.05-ar71xx-generic-ubnt-loco-m-xw-squ
19 matches
Mail list logo
