Re: ath10k-ct all hash values are different?

2020-11-08 Thread Baptiste Jonglez
Hi, All versions of the firmware are mirrored here http://sources.openwrt.org/ It's just that the build system somehow fails to fallback to this mirror like it does for regular downloads (in other words: it's a bug) Ben, could you re-upload all versions so that older builds can still work? This

Re: Upcoming 19.07.4 and 18.07.9 stable releases

2020-11-11 Thread Baptiste Jonglez
On 11-11-20, Hauke Mehrtens wrote: > Hi, > > Currently 18.06 looks good for me and I would really like to do the final > release and call it then officially end of life. > > I would wait for the build bot results and then do it at the weekend. Yes, I fully agree, it's ready. Looking at buildbot

SAD DNS cache poisoning attack

2020-11-14 Thread Baptiste Jonglez
Hi, There is a new generic cache poisoning attack for DNS: https://www.saddns.net/ It's a bit tricky, but the general idea is that an attacker can guess the ephemeral port used by a DNS resolver make a DNS query (that's dnsmasq in our case). The attacker then "just" has to guess the transaction

Re: SAD DNS cache poisoning attack

2020-11-14 Thread Baptiste Jonglez
On 15-11-20, Baptiste Jonglez wrote: > There are two solutions to fix/workaround the problem: > > 1) randomize ICMP rate limiting (done in upstream kernel, there are >already OpenWrt patches to update it) I just checked, here are stable kernel versions containing the fix

[PATCH 19.07] ipq40xx: Revert "ipq40xx: fix ethernet vlan double tagging"

2020-11-20 Thread Baptiste Jonglez
From: Baptiste Jonglez This change has been causing several issues on ipq40xx devices, including: - VLAN tagging no longer works correctly: https://bugs.openwrt.org/index.php?do=details&task_id=3239 - poor performance with tagged VLANs: https://bugs.openwrt.org/index.php?do=details&

Re: [PATCH opkg 0/5] Purge packages from cache when they have incorrect checksum

2020-11-20 Thread Baptiste Jonglez
Hi, Any news on this patch series? It should definitely be considered before the 20.XX branching because it fixes FS#2690 (bug related to imagebuilder), and I would like to backport it to 19.07 at some point. Thanks, Baptiste On 25-08-20, Baptiste Jonglez wrote: > From: Baptiste Jong

[PATCH 19.07 v2] ipq40xx: Revert "ipq40xx: fix ethernet vlan double tagging"

2020-11-20 Thread Baptiste Jonglez
From: Baptiste Jonglez This change has been causing several issues on ipq40xx devices, including: - VLAN tagging no longer works correctly: https://bugs.openwrt.org/index.php?do=details&task_id=3239 - poor performance with tagged VLANs: https://bugs.openwrt.org/index.php?do=details&

Re: [PATCH 19.07] ipq40xx: Revert "ipq40xx: fix ethernet vlan double tagging"

2020-11-20 Thread Baptiste Jonglez
Hi, On 20-11-20, Adrian Schmutzler wrote: > > -Original Message- > > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > > On Behalf Of Baptiste Jonglez > > Sent: Freitag, 20. November 2020 11:21 > > To: openwrt-devel@lists.openwrt.org;

Re: [PATCH] Revert "build: switch VERSION_REPO to HTTPS"

2020-11-25 Thread Baptiste Jonglez
Hi, On 25-11-20, Petr Štetiar wrote: > Paul Spooren [2020-11-24 22:29:00]: > > Hi, > > > Using HTTPS for opkg dramatically slows down download of packages and reload > > of indexes. > > do you've such dramatic numbers handy? For the imagebuilder, it increases the *total* build time (not just

Re: SAD DNS cache poisoning attack

2020-12-05 Thread Baptiste Jonglez
On 05-12-20, Alexander 'lynxis' Couzens wrote: > Hi, > > I'm wondering is dnsmasq also vulnerable as forwarder? Or > only as recursive resolver? Yes, as forwarder. I don't think dnsmasq implements a real recursive resolver. > Did someone tested it? Is there a public poc? I tested the basic beh

Re: [RFC 0/5] ath79: add a lower RAM-using version of 8/32 devices

2020-12-06 Thread Baptiste Jonglez
Hi, On 06-12-20, Sven Roederer wrote: > Currently 8MB flash / 32MB RAM devices are fully supported in OpenWrt, as they > work quite well for basic usage (including full LuCI). > On some projects with advanced features (e.g. Freifunk) the lack of RAM turns > them into unstable devices. Mostly cau

Re: Lightweight policy-based routing

2020-12-06 Thread Baptiste Jonglez
On 04-12-20, Philip Prindeville wrote: > But I’m trying: > > config rule > option src '192.168.3.6' > option lookup 200 > > Per the cheatsheet and it’s resulting in: > > root@OpenWrt2:~# ip rule ls > 0:from all lookup local > 1:from all lookup 200 > 32766:from all loo

Security Advisory 2020-12-09-1 - Linux kernel - ICMP rate limiting can be used to facilitate DNS poisoning attack (CVE-2020-25705)

2020-12-10 Thread Baptiste Jonglez
https://openwrt.org/advisory/2020-12-09-1 DESCRIPTION A flaw has been found in the ICMP rate limiting algorithm of the Linux kernel. This flaw allows an off-path attacker to quickly determine open ephemeral ports that are used by applications making outbound connections. This can be exploited

Upcoming 19.07.6 release plan

2020-12-18 Thread Baptiste Jonglez
___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/m

ramips mt7621 kernel crash related to TSO on 19.07

2020-12-22 Thread Baptiste Jonglez
Hi, OpenWrt 19.07 on mt7621 can sometimes crash under load. It does not trigger often so it might go unnoticed, but there are multiple reports of this issue and I also experienced it on a device. Here is an example crash log: https://bugs.openwrt.org/index.php?getfile=1116 Somebody managed t

Re: [PATCH] build/prereq: merge ifndef IB block together

2020-12-30 Thread Baptiste Jonglez
Hi, On 29-12-20, Paul Spooren wrote: > Multiple prereq checks are only required within the build system but not > for the ImageBuilder. These checks are excluded by using ifndef IB. > > This commit merges the three ifndef IB blocks together. To clarify, this is only cosmetic, right? I just saw

Persistent HTTP(S) connections in opkg

2020-12-30 Thread Baptiste Jonglez
Following the discussion in http://lists.openwrt.org/pipermail/openwrt-devel/2020-November/032297.html There are basically two options to implement persistent connections in opkg: 1) keep calling "wget", but pass the list of all packages to download at once. On the host, wget already impleme

[PATCH uclient] uclient-fetch: document missing options

2020-12-30 Thread Baptiste Jonglez
From: Baptiste Jonglez Missing ones were: --no-proxy, --quiet, --continue / -c Also improved readability of several options. Signed-off-by: Baptiste Jonglez --- uclient-fetch.c | 13 - 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/uclient-fetch.c b/uclient-fetch.c

Re: Persistent HTTP(S) connections in opkg

2021-01-01 Thread Baptiste Jonglez
Hi, On 31-12-20, Hauke Mehrtens wrote: > > I looked into performance problems of LuCI when using https some time ago. > > > > The slow part was the handshake, the normal stream cipher is relatively > > fast, even very slow devices should be able to do multiple MB/s. > > > > On the server side th

Backporting opkg fixes to 19.07

2021-01-24 Thread Baptiste Jonglez
Hi, I would like to backport the opkg fix for https://bugs.openwrt.org/index.php?do=details&task_id=2690 to 19.07. The opkg package in 19.07 is a bit old, it's using: f2166a8 libopkg: implement lightweight package listing logic Since there were several other changes in opkg master, I would cre

Re: Backporting opkg fixes to 19.07

2021-01-31 Thread Baptiste Jonglez
Hi, I've just pushed this to my (brand new) staging tree: https://git.openwrt.org/?p=openwrt/staging/zorun.git;a=shortlog;h=refs/heads/openwrt-19.07 If there are no objections, I will merge that in a couple of days. Baptiste On 24-01-21, Baptiste Jonglez wrote: > Hi, > > I

Upcoming 19.07.7 release

2021-02-05 Thread Baptiste Jonglez
Hi, We are planning a new 19.07 release in about a week (probably next week-end). If you are aware of changes that need to be integrated, now is the time to do it or mention it here! I plan to test & integrate a workaround for this ramips stability issue: https://bugs.openwrt.org/index.php?do=de

Re: Upcoming 19.07.7 release

2021-02-07 Thread Baptiste Jonglez
On 05-02-21, Jaap Buurman wrote: > > Hi, > > > > We are planning a new 19.07 release in about a week (probably next > > week-end). > > > > If you are aware of changes that need to be integrated, now is the time to > > do it or mention it here! > > > > I plan to test & integrate a workaround for th

Re: Upcoming 19.07.7 release

2021-02-14 Thread Baptiste Jonglez
On 07-02-21, Jaap Buurman wrote: > Are we sure disabling TSO is the actual fix though? There are a few > reasons I am doubting that assessment: > > 1. Here is a user that is reporting he has always been running with > TSO disabled, yet he does experience the bug: > https://forum.openwrt.org/t/mtk-

Re: Upcoming 19.07.7 release

2021-02-17 Thread Baptiste Jonglez
On 08-02-21, Etan Kissling (IC) wrote: > I have posted a few backports to 19.07 from master a few weeks back, with > these subjects: > > 1. [PATCH 19.07] mbedtls: add config option to compile with hkdf > 2. [PATCH 19.07] hostapd: add multicast_to_unicast and per_sta_vif > 3. [PATCH 19.07] hostapd

OpenWrt 19.07.7 service release

2021-02-18 Thread Baptiste Jonglez
Hi, The OpenWrt community is proud to announce the seventh service release of OpenWrt 19.07. It fixes security issues, improves device support, and brings a few bug fixes. The main changes from OpenWrt 19.07.6 are: Security fixes == * Security Advisory 2021-02-02-1 - netifd and odhc

[PATCH buildbot] phase2: exclude temporary files from sourceupload step

2021-03-24 Thread Baptiste Jonglez
From: Baptiste Jonglez When the dl/ directory is shared with several workers, there can be temporary "*.hash" and "*.dl" files being created by other workers. These files should be excluded from the sourceupload step, otherwise it can cause a failure when rsync tries to

[PATCH buildbot v2] phase1, phase2: exclude temporary source files from sourceupload step

2021-03-24 Thread Baptiste Jonglez
From: Baptiste Jonglez When the dl/ directory is shared with several workers, there can be temporary "*.hash" and "*.dl" files being created by other workers. These files should be excluded from the sourceupload step, otherwise it can cause a failure when rsync tries to

[PATCH buildbot] phase1, phase2: don't mark the build failed if a non-critical step fails

2021-03-24 Thread Baptiste Jonglez
From: Baptiste Jonglez Some steps are informative or optional (haltOnFailure=False), so it makes no sense to mark the whole build as failed if such a step fails. Depending on the case, we either mark the build as "warning" (warnOnFailure=True) or as successful (warnOnFailure=False).

[OpenWrt-Devel] [PATCH netifd] interface-ip: Fix broadcast address when using /31 IPv4 addressing

2015-09-14 Thread Baptiste Jonglez
A /31-addressed interface requires a 255.255.255.255 broadcast, because there is no room for a proper broadcast address. Without this, any packet destinated to the other end of the link is sent as broadcast, which is incorrect. Signed-off-by: Baptiste Jonglez --- interface-ip.c | 15

[OpenWrt-Devel] [PATCH v2 netifd] interface-ip: Fix broadcast address when using /31 or /32 IPv4 addressing

2015-09-14 Thread Baptiste Jonglez
From: Baptiste Jonglez A /31-addressed interface requires a broadcast address of 255.255.255.255, because there is no room for a proper broadcast address. Without this, any packet destinated to the other end of the link is sent as broadcast, which is incorrect. For consistency with the Linux

Re: [OpenWrt-Devel] [PATCH][ar71xx] Routerboard 951G Switch Fix

2016-02-14 Thread Baptiste Jonglez
Hi, On Wed, Jan 27, 2016 at 07:03:58PM +0300, Anton Kalmykov wrote: > Hi, 951G owners! > I have RB951G-2HnD device with AR9344 rev 3. It is configured like that: > - Balanced 2 WAN ports (mwan3) > - ipsec LAN-to-LAN > - OpenVPN server > - about 30 clients (wi-fi, lan) > > My results for different

Re: [OpenWrt-Devel] [RFC relayd 0/2] relayd: add ipv6 support

2016-04-19 Thread Baptiste Jonglez
Hi, On Mon, Apr 11, 2016 at 03:14:52PM +0200, Michal Kazior wrote: > I've been recently working on adding IPv6 support > to relayd (which supported only IPv4). > > It does, however, require a kernel patch to make > it actually usable because link-local addresses > are not routable by kernel by de

Re: [OpenWrt-Devel] [PATCH v2] firewall3: Fix multicast ICMPv6 replies not being sent by default anymore.

2016-05-02 Thread Baptiste Jonglez
Hi Vittorio, On Mon, May 02, 2016 at 08:17:48PM +0200, Vittorio Gambaletta (VittGam) wrote: > Since drop_invalid has been turned on by default, ICMPv6 echo requests > to well-known multicast addresses, such as ff02::1, are not replied to > by the router anymore, because conntrack considers those o

Re: [OpenWrt-Devel] [PATCH v2] firewall3: Fix multicast ICMPv6 replies not being sent by default anymore.

2016-05-02 Thread Baptiste Jonglez
On Mon, May 02, 2016 at 09:37:07PM +0200, Baptiste Jonglez wrote: > On Mon, May 02, 2016 at 08:17:48PM +0200, Vittorio Gambaletta (VittGam) wrote: > > Since drop_invalid has been turned on by default, ICMPv6 echo requests > > to well-known multicast addresses, such as ff02::1, are

Re: [OpenWrt-Devel] [PATCH] coova-chilli: Fix UCI parse error

2016-07-06 Thread Baptiste Jonglez
Hi Rajan, On Wed, Jul 06, 2016 at 07:03:43PM +0530, Rajan Vaja wrote: > UCI commands report errors in parsing coova-chilli > sample configuration file. Fix this issue by using > proper format in configuration. This package is maintained in the openwrt-packages Github repository: https://github

Re: [OpenWrt-Devel] Having a [kernel] package setting kernel CONFIG_XXX.

2016-07-16 Thread Baptiste Jonglez
Hi, On Fri, Jul 15, 2016 at 09:07:07AM +0100, David Fernandez wrote: > I'm trying to have a kernel package to emnable some kernel configuration > settings. > > I've tried using the KCONFIG:=CONFIG_XXX in the kernel packages, or creating > "config KERNEL_XXX" in any kind of package. > > Only to f

Re: [OpenWrt-Devel] [PATCH] buildroot: improve git submodule handling for packages

2016-07-19 Thread Baptiste Jonglez
On Sat, Feb 27, 2016 at 01:32:52AM +, Karl Palsson wrote: > This changes the buildroot dependency from git-1.6.2 to git 1.7.12.2, > which was released September 2012. I find this annoying, since Debian wheezy only has git 1.7.10.4. Actually, sometimes I use a squeeze box for building, and it w

[OpenWrt-Devel] [PATCH CC] script: download: change mirror for kernel.org

2016-07-30 Thread Baptiste Jonglez
At least one mirror in the ftp.all.kernel.org DNS seems to have broken FTP, resulting in very long timeouts. Update mirror to use the same one as trunk. This is a backport of r46875 from trunk. Signed-off-by: Baptiste Jonglez --- scripts/download.pl |4 ++-- 1 files changed, 2 insertions

Re: [OpenWrt-Devel] What happened to nut UPS config? (#20515)

2015-09-26 Thread Baptiste Jonglez
Hi David, Package-related patches should be submitted to the Github package repository: https://github.com/openwrt/packages/ Baptiste On Thu, Sep 17, 2015 at 11:32:36AM +0100, David Woodhouse wrote: > In my old AA setup, the nut package had an init script which built > ups.conf and upsd.users

Re: [OpenWrt-Devel] [PATCH v2 netifd] interface-ip: Fix broadcast address when using /31 or /32 IPv4 addressing

2015-09-26 Thread Baptiste Jonglez
nbd, did you have time to look at this new version of the patch? Thanks, Baptiste On Mon, Sep 14, 2015 at 12:25:33PM +0200, Baptiste Jonglez wrote: > From: Baptiste Jonglez > > A /31-addressed interface requires a broadcast address of 255.255.255.255, > because there is no room

Re: [OpenWrt-Devel] [PATCH] libnl: split into smaller libraries

2015-10-03 Thread Baptiste Jonglez
On Tue, Sep 22, 2015 at 03:42:26PM +0300, Alexandru Ardelean wrote: > So, > - bmon requires libnl-route > - aircrack-ng requires libnl-genl > - kismet i am not sure 100% ; maybe libnl-genl ; I did not want to > investigate much deeper > - ibrcommon requires libnl-genl and libnl-route > - keepalived

[OpenWrt-Devel] [PATCH] libnl: Fix URL

2015-10-04 Thread Baptiste Jonglez
From: Baptiste Jonglez Signed-off-by: Baptiste Jonglez --- package/libs/libnl/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package/libs/libnl/Makefile b/package/libs/libnl/Makefile index 241e9a7..c5873fd 100644 --- a/package/libs/libnl/Makefile +++ b/package

Re: [OpenWrt-Devel] [PATCH] libnl: split into smaller libraries

2015-10-04 Thread Baptiste Jonglez
On Sat, Oct 03, 2015 at 01:10:18PM +0200, Felix Fietkau wrote: > > As far as I understood this, libnl-tiny is a drop-in replacement for > > libnl-core. Or is there a difference in functionality or API/ABI? > libnl-tiny replaces the most commonly used parts of libnl-core + -genl. > The API is a bit

Re: [OpenWrt-Devel] [PATCH][ar71xx] Routerboard 951G Switch Fix

2015-11-14 Thread Baptiste Jonglez
Hi, On Wed, Dec 10, 2014 at 01:40:42PM -0700, Davey Hutchison wrote: > Fix pll_1000 value for eth0. Traffic would not flow from the eth0 interface. > The new PLL enables delay, use ath79_setup_ar934x_eth_cfg to also enable > AR934X_ETH_CFG_RXD_DELAY. I can confirm that this patch works on CC on

[OpenWrt-Devel] Enable initramfs build by default on mikrotik

2015-11-15 Thread Baptiste Jonglez
Hi, Mikrotik devices need an initramfs for installation: http://wiki.openwrt.org/toh/mikrotik/common#downloading_openwrt_image However, the needed configuration option (CONFIG_TARGET_ROOTFS_INITRAMFS) is absent from the build configuration in both CC and trunk: https://downloads.openwrt.org

[OpenWrt-Devel] [PATCH] netifd: Request DHCP option 121 (classless route) by default

2015-11-17 Thread Baptiste Jonglez
From: Baptiste Jonglez This option is very useful when the gateway configured by DHCP cannot be in the same subnet as the client. This happens, for instance, when using DHCP to hand out addresses in /32 subnets. Signed-off-by: Baptiste Jonglez --- package/network/config/netifd/files/lib

Re: [OpenWrt-Devel] [PATCH] netifd: Request DHCP option 121 (classless route) by default

2015-11-18 Thread Baptiste Jonglez
; however, it would be much easier if OpenWRT clients worked out-of-the-box on our network. > Bye, > Hans Thanks, Baptiste > On Wed, Nov 18, 2015 at 12:33 AM, Baptiste Jonglez < > bapti...@bitsofnetworks.org> wrote: > > > From: Baptiste Jonglez > > > > Thi

Re: [OpenWrt-Devel] [PATCH] netifd: Request DHCP option 121 (classless route) by default

2015-11-20 Thread Baptiste Jonglez
On Thu, Nov 19, 2015 at 03:41:10PM +0100, Hans Dedecker wrote: > On Thu, Nov 19, 2015 at 2:39 PM, Steven Barth wrote: > > > I don't see this argument as very convincing. I mean they still have > > control even if the client ORO's 121, they could simply ignore it. On top > > of that I think there

[OpenWrt-Devel] [PATCH v2] netifd: Request DHCP option 121 (classless route) by default

2015-11-20 Thread Baptiste Jonglez
From: Baptiste Jonglez This option is useful when the gateway configured by DHCP cannot be in the same subnet as the client. This happens, for instance, when using DHCP to hand out addresses in /32 subnets. A new configuration option "classlessroute" is available, allowing users

[OpenWrt-Devel] [PATCH] ar71xx: Build initramfs by default for Mikrotik devices

2015-11-22 Thread Baptiste Jonglez
From: Baptiste Jonglez Signed-off-by: Baptiste Jonglez --- target/linux/ar71xx/mikrotik/target.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/mikrotik/target.mk b/target/linux/ar71xx/mikrotik/target.mk index a2a41ed..b2fb0df 100644 --- a/target

Re: [OpenWrt-Devel] [PATCH][ar71xx] Routerboard 951G Switch Fix

2015-11-25 Thread Baptiste Jonglez
#tracking_reported_experience_with_suggested_patch_for_the_5_gige_ports Thanks, Baptiste On Sat, Nov 14, 2015 at 06:30:52PM +0100, Baptiste Jonglez wrote: > Hi, > > On Wed, Dec 10, 2014 at 01:40:42PM -0700, Davey Hutchison wrote: > > Fix pll_1000 value for eth0. Traffic would not flow from the eth0 > > interface. The new P

Re: [OpenWrt-Devel] [PATCH v2] netifd: Request DHCP option 121 (classless route) by default

2015-12-20 Thread Baptiste Jonglez
Hi, Any news on this patch? As requested, the v2 patch introduces a configuration knob to disable requesting option 121. Thanks, Baptiste On Fri, Nov 20, 2015 at 11:50:56PM +0100, Baptiste Jonglez wrote: > From: Baptiste Jonglez > > This option is useful when the gateway configure

Re: [OpenWrt-Devel] [PATCH][ar71xx] Routerboard 951G Switch Fix

2015-12-20 Thread Baptiste Jonglez
Hi, I'm bumping again, this patch is necessary to make the gigabit switch work on the Mikrotik 951G-2HnD (tested on CC). Thanks, Baptiste On Wed, Nov 25, 2015 at 06:18:29PM +0100, Baptiste Jonglez wrote: > Hi, > > Sorry to bump up the thread again. Is there anything blocking t

[OpenWrt-Devel] Call for participation for BattleMesh V12 (8-14 July 2019, Paris)

2019-05-31 Thread Baptiste Jonglez
Hello, The local organization team is proud to announce that this year's Battlemesh will be held near Paris, from 8 to 14 July! The event aims to bring together people from across the globe who are interested in community networks, including wireless mesh network technologies, fiber infrastructur

[OpenWrt-Devel] ipq40xx: fails to boot with SMP on Mikrotik hAP ac² / RBD52G-5HacD2HnD (WIP)

2019-07-29 Thread Baptiste Jonglez
Hi, I am trying to finish the port of Mikrotik hAP ac², but I still can't get it to boot properly with SMP. Adding "nosmp" to the cmdline makes the initramfs boot fine. Here is the work-in-progress tree that Hauke based on the RB450Gx4 work: https://github.com/mmaker/openwrt/tree/device/hAP-ac%

Re: [OpenWrt-Devel] ipq40xx: fails to boot with SMP on Mikrotik hAP ac² / RBD52G-5HacD2HnD (WIP)

2019-07-29 Thread Baptiste Jonglez
On 29-07-19, Hauke Mehrtens wrote: > On 7/29/19 11:25 AM, Baptiste Jonglez wrote: > > Is there something obviously wrong in the DTS? As far as I know, other > > ipq40xx devices don't have an issue with SMP. > > Did you try to revert this commit: > https://git

Re: [OpenWrt-Devel] ipq40xx: fails to boot with SMP on Mikrotik hAP ac² / RBD52G-5HacD2HnD (WIP)

2019-07-30 Thread Baptiste Jonglez
n :) > If you want, I'll try to enable SMP and see if my board boots. > If you have any insight on WiFi, please let me know. > > I'd like to help where I can. > > On Mon, Jul 29, 2019 at 4:10 PM Baptiste Jonglez < > bapti...@bitsofnetworks.org> wrote: > >

Re: [OpenWrt-Devel] lede-imagebuilder-17.01.5-ar71xx-generic.Linux-x86_64 fails to build image

2018-09-03 Thread Baptiste Jonglez
Hi, On 18-07-18, Mikael Bak wrote: > Hi, > > Image builder for 17.01.5 seems broken. > > It works well for 17.01.4 and 18.06.0-rc1 on my system. I'm having the same issue with the ar71xx imagebuilder on Arch Linux: 17.01.4 and 18.06.1 both work fine, but 17.01.5 fails with the same error messag

Re: [OpenWrt-Devel] lede-imagebuilder-17.01.5-ar71xx-generic.Linux-x86_64 fails to build image

2018-09-05 Thread Baptiste Jonglez
On 03-09-18, Baptiste Jonglez wrote: > On 18-07-18, Mikael Bak wrote: > > Hi, > > > > Image builder for 17.01.5 seems broken. > > > > It works well for 17.01.4 and 18.06.0-rc1 on my system. > > I'm having the same issue with the ar71xx imagebuilder on

[OpenWrt-Devel] [PATCH] kernel: Add support for Winbond w25q128jv SPI NOR flash

2018-10-18 Thread Baptiste Jonglez
From: Baptiste Jonglez Newer batches of several Mikrotik boards contain this yet-unsupported flash chip, for instance: - rb941-2nd (hAP lite) - rb952ui-5ac2nd (hAP ac lite) - RBM33G and probably other Mikrotik boards need this patch as well. The patch was submitted upstream by Robert Marko

[OpenWrt-Devel] [PATCH openwrt-18.06] kernel: Add support for Winbond w25q128jv SPI NOR flash

2018-10-18 Thread Baptiste Jonglez
From: Baptiste Jonglez Newer batches of several Mikrotik boards contain this yet-unsupported flash chip, for instance: - rb941-2nd (hAP lite) - rb952ui-5ac2nd (hAP ac lite) - RBM33G and probably other Mikrotik boards need this patch as well. The patch was submitted upstream by Robert Marko

Re: [OpenWrt-Devel] [PATCH openwrt-18.06] kernel: Add support for Winbond w25q128jv SPI NOR flash

2018-10-22 Thread Baptiste Jonglez
Hi Hauke, Thanks for merging the other patch in master! Can you also merge this one in the openwrt-18.06 branch? This will add support for the newer Mikrotik boards in the next 18.06.X release. Regards, Baptiste On 18-10-18, Baptiste Jonglez wrote: > From: Baptiste Jonglez > > Newe

[OpenWrt-Devel] Breaking compatibility with pre-1.5.1 babeld on OpenWRT/LEDE

2017-01-09 Thread Baptiste Jonglez
Dear babeld users on OpenWRT/LEDE, Starting from babeld 1.5.1, the UCI format for configuring babeld on OpenWRT had changed to be more consistent with upstream babeld (use the same option names, and a few other changes). At the time, I had ensured backward compatibility, see: https://wiki.open

[OpenWrt-Devel] Babeld now has procd support on OpenWRT/LEDE

2017-01-12 Thread Baptiste Jonglez
Hi, Here is yet another OpenWRT-related change for babeld: I just merged procd support for babeld [2], after more than two years of lingering [1]. The only user-visible changes should be: - babeld now logs to the system log (visible with "logread") instead of a file in /var/log. This is nice

Re: [OpenWrt-Devel] Loss of connectivity on ADSL reset

2017-01-13 Thread Baptiste Jonglez
On Fri, Jan 13, 2017 at 09:24:04AM +, Tim Coote wrote: > > > On 12 Jan 2017, at 21:24, Hans Dedecker wrote: > > > >> config interface 'e0ext' > >>option ifname 'pppoe-e0' > > You need to configure the ifname as an aliased interface of interface e0; > > eg > > option ifname @e0 > > > T

[OpenWrt-Devel] [RFC] A new developper documentation for OpenWrt/LEDE

2017-10-25 Thread Baptiste Jonglez
Hi, As an occasional contributor to OpenWrt/LEDE, I am often frustrated by the lack of good technical documentation. By "technical documentation", I mean a detailed, reasonably complete and up-to-date documentation on "How things work under the hood" and "How to do advanced stuff with the build s

Re: [OpenWrt-Devel] Desktop configuring tool

2014-07-13 Thread Baptiste Jonglez
On Mon, Jul 14, 2014 at 07:37:37AM +0200, Jakub Jančo wrote: > Hello, > > does exist something like winbox for mikrotik? > It should be owrt api(UCI+ssh for example) and desktop GUI. UCI over SSH doesn't look very pretty, I'd say ubus over HTTP is a better idea: http://wiki.openwrt.org/doc/tec

[OpenWrt-Devel] IPv6 firewall and Port Control Protocol (Was: Barrier Breaker 14.07-rc1)

2014-07-14 Thread Baptiste Jonglez
On Mon, Jul 14, 2014 at 11:12:01AM +0200, John Crispin wrote: > > The OpenWrt developers are proud to announce the first release > candidate of OpenWrt Barrier Breaker. Excellent news, thanks! > * Native IPv6-support > - RA & DHCPv6+PD client and server > - Local prefix allocation &

Re: [OpenWrt-Devel] IPv6 firewall and Port Control Protocol (Was: Barrier Breaker 14.07-rc1)

2014-07-14 Thread Baptiste Jonglez
Hi Steven, On Mon, Jul 14, 2014 at 02:38:16PM +0200, Steven Barth wrote: > Hi Baptiste, > > in general our current firewalling approach is to keep defaults for IPv4 and > IPv6 relatively close (not considering NAT here of course). Could you detail the reasoning behind this approach? "Don't conf

Re: [OpenWrt-Devel] IPv6 firewall and Port Control Protocol (Was: Barrier Breaker 14.07-rc1)

2014-07-16 Thread Baptiste Jonglez
On Tue, Jul 15, 2014 at 11:45:27AM -0400, Aaron Z wrote: > As I understand it, if a device on the inside of the network initiates > the connection to a device on the outside (say from a VOIP phone to a > VOIP server), return connections from the server are allowed. Yes, this is exactly the role of

[OpenWrt-Devel] Netifd support for tunnels and address configuration

2014-07-17 Thread Baptiste Jonglez
Hi, I am currently adding GRE support for OpenWRT, based on 6in4 support [1] (since I couldn't find any documentation). What is the proper way to support address configuration for tunnel interfaces? It seems redundant to handle static address configuration for each tunnel type, especially with t

Re: [OpenWrt-Devel] OpenWRT IPv6 firewall

2014-07-17 Thread Baptiste Jonglez
On Thu, Jul 17, 2014 at 03:21:32PM +0100, Fernando Frediani wrote: > Hello guys, > > This discussion if becoming each day more confusing for something, which for > me, is very simple assuming the following: > > - IPv6 as IPv4 should block *any incoming connection* on the WAN > interface inclu

Re: [OpenWrt-Devel] Netifd support for tunnels and address configuration

2014-07-17 Thread Baptiste Jonglez
On Thu, Jul 17, 2014 at 06:28:09PM +0200, Hans Dedecker wrote: > Hi Baptiste, > > I have added GRE support (gre/gretap/grev6/grev6tap) in netifd which I'm > currenlty testing. The implementation looks the same as for 6rd/dslite tunnel > interfaces (thus allowing to set mtu/ttl/remote end point);

[OpenWrt-Devel] Duplicate netifd protocol for l2tp

2014-07-18 Thread Baptiste Jonglez
Hi, Two packages provide the "proto l2tp" netifd protocol: xl2tpd [1] in the new packages feed, and l2tpv3tun [2] in oldpackages. The config are totally different, the problem is really a name clash. What is the recommended way to deal with name clashes in netifd protocols, without breaking exist

Re: [OpenWrt-Devel] Duplicate netifd protocol for l2tp

2014-07-21 Thread Baptiste Jonglez
Steven Barth wrote: > I renamed the xl2tpd netifd protocol to "l2tpv2" and kept the l2tpv3 as > "l2tp" as documented in the wiki. Thanks :) On Mon, Jul 21, 2014 at 08:47:58AM +0200, Dirk Neukirchen wrote: > > The config are totally different, the problem is really a name clash. > > It seems they

Re: [OpenWrt-Devel] IPv6-question / fe80 / linklocal / uniq?

2014-07-22 Thread Baptiste Jonglez
On Tue, Jul 22, 2014 at 11:50:55AM +0200, Bastian Bittorf wrote: > when reading http://en.wikipedia.org/wiki/IPv6#Link_local_address > it seems to me, that the linklocal-address should be uniq, "unique" is ambiguous: do you mean that the same LL address can't be present on different interfaces? on

Re: [OpenWrt-Devel] IPv6-question / fe80 / linklocal / uniq?

2014-07-22 Thread Baptiste Jonglez
On Tue, Jul 22, 2014 at 02:08:16PM +0200, Bastian Bittorf wrote: > * Baptiste Jonglez [22.07.2014 13:21]: > > > root@box:~ ip neigh | grep ^'fe80::' | grep "lladdr $mac" > > > fe80::1cfc:fe65:769:3784 dev wlan0 lladdr 84:b1:53:b2:b8:b3 STALE > > &g

Re: [OpenWrt-Devel] [PATCH] gre: Generic Routing Encapsulation package support

2014-08-02 Thread Baptiste Jonglez
Thank you for this nice implementation. I've started some documentation on http://wiki.openwrt.org/doc/uci/network A few comments after testing gre/gretap on BB-rc2 (with netifd 2014-07-30 from trunk): 1/ the firewall rules added by "zone" do no seem to be flushed when the interface goes down

Re: [OpenWrt-Devel] [PATCH] gre: Generic Routing Encapsulation package support

2014-08-02 Thread Baptiste Jonglez
On Sat, Aug 02, 2014 at 11:51:33PM +0900, Baptiste Jonglez wrote: > 2/ "tunlink" does not seem to work for anything else than "wan". When >trying to set it to "lan" (which is properly defined in the network >config), the tunnel is not created. Th

Re: [OpenWrt-Devel] [PATCH] gre: Generic Routing Encapsulation package support

2014-08-03 Thread Baptiste Jonglez
On Sun, Aug 03, 2014 at 11:37:51AM +0200, Steven Barth wrote: > tbh. we should get rid of that option network stuff. > I merged it anyway at first so we can get some experience with this > gre-integration. > Normally you should use something like this instead: > > config interface mygre >

[OpenWrt-Devel] [BB-rc3] Disabling DHCPv6 also disables IPv6 SLAAC

2014-08-22 Thread Baptiste Jonglez
Hi, The default behaviour of BB is to hand out statically assigned IPv6 addresses through DHCPv6. To disable this behaviour and only keep SLAAC through RA, I disabled dhcpv6 in /etc/config/dhcp: config dhcp 'lan' option interface 'lan' option start '70' option limit '64'

Re: [OpenWrt-Devel] [BB-rc3] Disabling DHCPv6 also disables IPv6 SLAAC

2014-08-22 Thread Baptiste Jonglez
On Fri, Aug 22, 2014 at 07:59:27PM +0200, Steven Barth wrote: > Please try with: > option dhcpv6 disabled > > instead of "none" That worked, thanks! What is the default value, then? Is it "none" or "disabled"? What is the difference? > Cheers, > > Steven > ___

Re: [OpenWrt-Devel] [BB-rc3] Disabling DHCPv6 also disables IPv6 SLAAC

2014-08-22 Thread Baptiste Jonglez
On Fri, Aug 22, 2014 at 10:38:24PM +0200, Bastian Bittorf wrote: > * Baptiste Jonglez [22.08.2014 22:34]: > > What is the default value, then? Is it "none" or "disabled"? What is the > > difference? > > internally it's a bool/switch, which can hav

[OpenWrt-Devel] Using "-" in section names

2014-08-27 Thread Baptiste Jonglez
Hi, I am currently writing an init script using the callback method [1], on BB-rc3. However, it does not seem possible to use "-" in a section name, for instance: config interface 'tun-test' option 'rxcost' '42' The "config_cb" function never gets called for this section (but "option_cb

[OpenWrt-Devel] Parsing list of options with the callback method

2014-08-27 Thread Baptiste Jonglez
Hi, According to [1], it should be possible to parse list of options in a UCI file using an "option_cb()" callback. It does not seem to work as expected, for instance this block: config example list 'import_table' '42' list 'import_table' '53' leads to the following calls: config_cb ex

Re: [OpenWrt-Devel] Using "-" in section names

2014-08-27 Thread Baptiste Jonglez
On Wed, Aug 27, 2014 at 07:49:21PM +0200, Jo-Philipp Wich wrote: > Hi, > > yes there is a reason, the initial uci implementation was shell based > and section names are part of generated variable names which must not > contain dashes. So, it shouldn't be necessary with the C implementation? > Si

Re: [OpenWrt-Devel] Parsing list of options with the callback method

2014-08-28 Thread Baptiste Jonglez
m this shell script: http://git.openwrt.org/?p=openwrt.git;a=blob;f=package/base-files/files/lib/functions.sh;h=0d4b2a33dbbf4e18acd474ae2adaad0ea3c1c4a0;hb=HEAD or from uci itself. Any clue? On Wed, Aug 27, 2014 at 07:11:39PM +0200, Baptiste Jonglez wrote: > Hi, > > According to [

Re: [OpenWrt-Devel] Using "-" in section names

2014-08-29 Thread Baptiste Jonglez
On Wed, Aug 27, 2014 at 08:38:16PM +0200, Jo-Philipp Wich wrote: > Even if "-" would be allowed you'd still need to deal with "@", ".", > "#", ":" and other funny characters that are legal in ifnames. > > The only suitable way using the existing syntax constraints is to use an > option value, simi

Re: [OpenWrt-Devel] [PATCH] babeld: use procd to start, stop, and respawn

2014-09-08 Thread Baptiste Jonglez
Hi, Note that babeld is maintained in https://github.com/openwrt-routing/packages. Nevertheless, comments inline. On Sun, Sep 07, 2014 at 05:56:32PM -0400, Tristan Plumb wrote: > Changes the babeld init script to utilize procd and Nice, it was a requested feature: https://github.com/openwrt-r

Re: [OpenWrt-Devel] [PATCH] babeld: use procd to start, stop, and respawn

2014-09-08 Thread Baptiste Jonglez
FYI - Forwarded message from Juliusz Chroboczek - Date: Mon, 08 Sep 2014 16:03:56 +0200 From: Juliusz Chroboczek To: Baptiste Jonglez Cc: openwrt-devel@lists.openwrt.org, babel-us...@lists.alioth.debian.org Subject: Re: [Babel-users] [OpenWrt-Devel] [PATCH] babeld: use procd to start

Re: [OpenWrt-Devel] [PATCH] base-files: procd initscripts restart on reload

2014-09-14 Thread Baptiste Jonglez
On Sun, Sep 14, 2014 at 08:14:11AM -0400, Tristan Plumb wrote: > Currently procd enabled initscripts will restart on reload when the command > line changes, which works for many packages, but not anything that keeps its > configuration in a file, like dnsmasq. Wouldn't it be better to check whethe

Re: [OpenWrt-Devel] [PATCH] GRE: Tos support

2014-09-28 Thread Baptiste Jonglez
On Sun, Sep 28, 2014 at 09:35:05PM +0200, Hans Dedecker wrote: > Tos support is added as a generic grev4/grev6 parameter which can have the > following values : > -inherit (outer header inherits the tos value of the inner header) > -hex value > > Signed-off-by: Hans Dedecker Thanks, I

Re: [OpenWrt-Devel] kernel changes on recompilation?

2014-10-01 Thread Baptiste Jonglez
When you activate/deactivate packages in menuconfig, it may modify what gets compiled into the kernel, to add/remove support for the various subsystems needed by the packages you build. This will cause the kernel to be rebuilt with a different package number. If you just rebuild the image without

Re: [OpenWrt-Devel] Ralink ethernet update

2014-10-30 Thread Baptiste Jonglez
On Thu, Oct 30, 2014 at 11:04:17PM +0200, Roman Yeryomin wrote: > On 30 October 2014 16:20, Mingyu Li wrote: > > i checkout the latest code and rebuild for rt-n15 > > only test 3 times lan to wan tcp performance 60 seconds one thread > > > > netperf version 2.6.0 > > 116.33, 116.20, 102.84 (10^6bi

Re: [OpenWrt-Devel] [RFC] ncurses vs ncursesw

2014-11-09 Thread Baptiste Jonglez
On Sun, Nov 09, 2014 at 09:40:37PM +0200, Alexandru Ardelean wrote: > I'll try to get opinions about this. > > Since we're in the middle of packages migration, maybe it's an interesting > opportunity to try to use ncursesw and drop ncurses. > > ncursesw is ncurses + Unicode (UTF8) support > > Bo

[OpenWrt-Devel] ImageBuilder frontend projects, or how to generate custom OpenWrt images

2019-09-29 Thread Baptiste Jonglez
Hi, In my community network we are changing the way we generate OpenWrt firmware images, and I took this opportunity to look at the existing methods based on the OpenWrt ImageBuilder and/or SDK. In the end, I found way more projects than I thought would exist! I documented everything I found her

Re: [OpenWrt-Devel] [Battlemesh] ImageBuilder frontend projects, or how to generate custom OpenWrt images

2019-10-19 Thread Baptiste Jonglez
Hi, On 30-09-19, Philipp Borgers wrote: > you should take look at the Freifunk Berlin firmware and the Gluon project: > > https://github.com/freifunk-berlin/firmware > > https://gluon.readthedocs.io/en/v2019.1.x/ > > The Freifunk Berlin firmware uses uci-defaults scripts quite a lot for setting

Re: [OpenWrt-Devel] wlan factory defaults

2019-11-11 Thread Baptiste Jonglez
Hi, On 11-11-19, Piotr Dymacz wrote: > On 11.11.2019 20:33, Ivan Baktsheev wrote: > > How to put this configuration into device? This is not a question for > > OpenWrt developers, but for people, who build customized OpenWrt firmware. > > It’s definitely better to customise build using scripts/c

Re: [OpenWrt-Devel] Question: Migration from ar71xx to ath79

2020-01-10 Thread Baptiste Jonglez
Good point, the ar71xx - ath79 migration needs more documentation. I have just created https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79 but it needs some work: is sysupgrade supposed to work in some cases? With/without saving the configuration? Is there any danger when forcing upg

  1   2   3   >