>
> On Sun, Mar 31, 2019 at 11:49 PM Lorenzo Bianconi
> wrote:
> >
> > >
> > > On Sun, Mar 31, 2019 at 12:15 PM Lorenzo Bianconi
> > > wrote:
> > > >
> > > > >
> > > > > On Sun, Mar 31, 2019 at 6:45 AM Lorenzo Bianconi
> > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > > bump.
> > > > > >
>
OpenVPN as of 2.4.7 uses some OpenSSL APIs that are deprecated in
OpenSSL >= 1.1.0.
Signed-off-by: Magnus Kroken
---
Thank you Rosen Penev for pointing this out.
As OpenSSL is built with deprecated APIs by default in OpenWrt
at the moment, I assume this will be the case for the 19.0x release,
an
Commit 124ab1dc0a and 5523ee3459 introduced the assignment of the
group "tty" to /dev/tty* devices in order to support unprivileged
user access to serial devices.
However, due to an improperly rebased commit this feature broke.
This patch restores the lost hunk in hotplug.json file to
re-introduc
Hello,
I've tried your suggenstions on my unit (and try to provide some
information from my work with the other two APs from OCEDO/Riverbed).
On 02.04.19 00:19, Petr Štetiar wrote:
> markus.sche...@gmail.com [2019-03-21 16:43:27]:
>
> Hi,
>
>> +label = "ursus:green:wlan2";
Hi,
Sorry for the inconvenience, but I'd like to insist on this topic since
it didn't get much traction on the first attempt.
I mostly succeeded in adding support for the COMFAST CF-E313AC devices,
but I ran into a couple of issues:
1) I need to remove the board-2.bin file shipped with the
ath10
> -Original Message-
> From: Petr Štetiar [mailto:yn...@true.cz]
> Sent: Dienstag, 2. April 2019 15:15
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 0/2] ar71xx: Add support for Bullet M
> (XW)
>
> Adrian Schmutzler [2019-04-02 14:07:
Adrian Schmutzler [2019-04-02 14:07:39]:
Hi,
> > # UBNT_CHIP e.g. one of (ar7240, ar933x, ar934x)
> > +# UBNT_VERSION e.g. one of (6.0.0, 8.5.0)
define Device/ubnt
UBNT_VERSION := 6.0.0
so it defaults to version 6.0.0 as it's used now, but it could be overriden if
the board needs to, like f
LGTM, except one nitpick in 1/2:
[...]
> # UBNT_CHIP e.g. one of (ar7240, ar933x, ar934x)
> +# UBNT_VERSION e.g. one of (6.0.0, 8.5.0)
> define Device/ubnt
[...]
> + UBNT_VERSION := 6.0.4
[...]
Maybe include the 6.0.4 in the commented list of versions, depending on how
literally you take t
Petr Štetiar [2019-04-02 13:26:42]:
> Ubiquity allows flashing of unsigned factory images via TFTP recovery
> method[1]. They claim in airOS v6.0.7 release changelog[2] following:
Please don't bother with this patch, I've sent it accidentaly. Removed from
patchwork as well. Sorry for the noise.
Hi,
this two patches are adding support for Ubiquity Bullet M (XW) to ar71xx.
First patch which fixes factory image so it's usable on newer AirOS versions
is basically just backport from ath79 and shouldn't hopefully introduce any
regressions. Without this patch, I simply wasn't able to boot ar71
Ubiquity allows flashing of unsigned factory images via TFTP recovery
method[1]. They claim in airOS v6.0.7 release changelog[2] following:
All future airOS versions will be signed in this way and not allow
unsigned firmware to be loaded except via TFTP.
U-boot bootloader on M-XW devices expect
CPU: AR9342 SoC
RAM: 64 MB DDR2
Flash:8 MB NOR SPI
Ports: 100 MBit (24V PoE in)
WLAN: 2.4/5 GHz
UART: 1 UART on PCB marked as J1 with 115200 8N1 config
LEDs: Power, Ethernet, 4x RSSI LEDs (orange, red, 2x green)
Buttons:Reset
UART connection details
.-
This is backport of the same functionality in ath79, from commit
d42a7c469 ("ath79: ubnt-m-xw: Fix factory image flashing using TFTP
recovery method")
Ubiquity allows flashing of unsigned factory images via TFTP recovery
method[1]. They claim in airOS v6.0.7 release changelog[2] foll
Currently, tplink-safeloader definition is only used as base for
another common definition, while multiple devices just repeat
the same relevant parameters in their definitions.
This patch adjusts tplink-safeloader so it can be actually used
for some targets in generic-tp-link.mk.
The only functi
14 matches
Mail list logo
