[OpenWrt-Devel] [PATCH] include/feeds.mk: fix distfeeds.conf without per-feed repos
commit 514a4b3e1b4e4 ("include/feeds.mk: rework generation of opkg
distfeeds.conf") made the per-feed "base" repo unconditional, making
the default configuration fail when PER_FEED_REPO is disabled:
root@wrt1900ac-1:~# cat /etc/opkg/distfeeds.conf
src/gz openwrt_core
http://openwrt.mork.no/18.06.0/targets/mvebu/cortexa9/packages
src/gz openwrt_base
http://openwrt.mork.no/18.06.0/packages/arm_cortex-a9_vfpv3/base
root@wrt1900ac-1:~# opkg update
Downloading
http://openwrt.mork.no/18.06.0/targets/mvebu/cortexa9/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading
http://openwrt.mork.no/18.06.0/targets/mvebu/cortexa9/packages/Packages.sig
Signature check passed.
Downloading
http://openwrt.mork.no/18.06.0/packages/arm_cortex-a9_vfpv3/base/Packages.gz
*** Failed to download the package list from
http://openwrt.mork.no/18.06.0/packages/arm_cortex-a9_vfpv3/base/Packages.gz
Collected errors:
* opkg_download: Failed to download
http://openwrt.mork.no/18.06.0/packages/arm_cortex-a9_vfpv3/base/Packages.gz,
wget returned 8.
Cc: Matthias Schiffer
Fixes: 514a4b3e1b4e ("include/feeds.mk: rework generation of opkg
distfeeds.conf")
Signed-off-by: Bjørn Mork
---
This needs to be backported to the 18.06 branch. Builds with PER_FEED_REPO
disabled are currently broken there too.
include/feeds.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/feeds.mk b/include/feeds.mk
index 3e0801e656bf..fa114c2a5f9e 100644
--- a/include/feeds.mk
+++ b/include/feeds.mk
@@ -34,8 +34,8 @@ endef
define FeedSourcesAppend
( \
echo 'src/gz %d_core %U/targets/%S/packages'; \
- echo 'src/gz %d_base %U/packages/%A/base'; \
$(strip $(if $(CONFIG_PER_FEED_REPO), \
+ echo 'src/gz %d_base %U/packages/%A/base'; \
$(foreach feed,$(FEEDS_AVAILABLE), \
$(if $(CONFIG_FEED_$(feed)), \
echo '$(if $(filter m,$(CONFIG_FEED_$(feed))),# )src/gz
%d_$(feed) %U/packages/%A/$(feed)'; \
--
2.11.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] kernel: bump 4.9 to 4.9.116 for 18.06
Hi Stijn, It seems a new helper was introduced in newer kernels: -- a/fs/ext4/super.c ++ b/fs/ext4/super.c @@ -3103,14 +3103,8 @@ static ext4_group_t ext4_has_uninit_itab if (!gdp) continue; - if (gdp->bg_flags & cpu_to_le16(EXT4_BG_INODE_ZEROED)) - continue; - if (group != 0) + if (!(gdp->bg_flags & cpu_to_le16(EXT4_BG_INODE_ZEROED))) break; - ext4_error(sb, "Inode table for bg 0 marked as " - "needing zeroing"); - if (sb_rdonly(sb)) << - return ngroups; } return group; can be altered to -- a/fs/ext4/super.c ++ b/fs/ext4/super.c @@ -3103,14 +3103,8 @@ static ext4_group_t ext4_has_uninit_itab if (!gdp) continue; - if (gdp->bg_flags & cpu_to_le16(EXT4_BG_INODE_ZEROED)) - continue; - if (group != 0) + if (!(gdp->bg_flags & cpu_to_le16(EXT4_BG_INODE_ZEROED))) break; - ext4_error(sb, "Inode table for bg 0 marked as " - "needing zeroing"); - if (sb->s_flags & MS_RDONLY) << - return ngroups; } return group; to make the patch applicable for 4.9 kernels. Koen ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] libpcap: patch to add limits.h to pcap-usb-linux.c
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Upstream patch that fixes compilation errors: 'PATH_MAX' and 'NAME_MAX' undeclared with musl. Signed-off-by: Eneas U de Queiroz --- ...205-pcap-usb-linux.c-add-missing-limits.h.patch | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 package/libs/libpcap/patches/205-pcap-usb-linux.c-add-missing-limits.h.patch diff --git a/package/libs/libpcap/patches/205-pcap-usb-linux.c-add-missing-limits.h.patch b/package/libs/libpcap/patches/205-pcap-usb-linux.c-add-missing-limits.h.patch new file mode 100644 index 00..cae8012ede --- /dev/null +++ b/package/libs/libpcap/patches/205-pcap-usb-linux.c-add-missing-limits.h.patch @@ -0,0 +1,22 @@ +From aafa3512b7b742f5e66a5543e41974cc5e7eebfa Mon Sep 17 00:00:00 2001 +From: maxice8 +Date: Sun, 22 Jul 2018 18:54:17 -0300 +Subject: [PATCH] pcap-usb-linux.c: add missing limits.h for musl systems. + +fix compilation on musl libc systems like Void Linux and Alpine. +--- + pcap-usb-linux.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/pcap-usb-linux.c b/pcap-usb-linux.c +index 6f8adf65e..b92c05ea1 100644 +--- a/pcap-usb-linux.c b/pcap-usb-linux.c +@@ -50,6 +50,7 @@ + #include + #include + #include ++#include + #include + #include + #include -- 2.16.4 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] kernel: bump 4.9 to 4.9.116 for 18.06
On 2018-07-30 21:31, Stijn Segers wrote: * Refreshed patches. * Removed patches: - target/linux/ar71xx/patches-4.9/103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch superseded by upstream - target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch superseded by upstream - target/linux/brcm63xx/patches-4.9/001-4.11-01-mtd-m25p80-consider-max-message-size-in-m25p80_read.patch accepted upstream - target/linux/brcm63xx/patches-4.9/001-4.15-08-bcm63xx_enet-correct-clock-usage.patch accepted upstream - target/linux/brcm63xx/patches-4.9/001-4.15-09-bcm63xx_enet-do-not-write-to-random-DMA-channel-on-B.patch accepted upstream Compile-tested on: ar71xx Run-tested on: ar71xx Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +- ...fix-register-address-in-ath79_ddr_wb_flus.patch | 23 -- .../403-mtd_fix_cfi_cmdset_0002_status_check.patch | 69 - ...low-to-pass-probe-types-via-platform-data.patch | 4 +- .../411-mtd-cfi_cmdset_0002-force-word-write.patch | 8 +- .../patches-4.9/910-unaligned_access_hacks.patch | 10 +- ...gnore-dtco-targets-when-filtering-symbols.patch | 2 +- .../patches-4.9/950-0031-Add-dwc_otg-driver.patch | 2 +- ...-consider-max-message-size-in-m25p80_read.patch | 30 -- ...-4.15-08-bcm63xx_enet-correct-clock-usage.patch | 101 -- ...t-do-not-write-to-random-DMA-channel-on-B.patch | 29 -- .../024-1-tcp-tsq-add-tsq_flags-tsq_enum.patch | 6 +- ...-remove-one-locked-operation-in-tcp_wfree.patch | 4 +- ...-tcp-tsq-add-shortcut-in-tcp_tasklet_func.patch | 6 +- ...4-4-tcp-tsq-avoid-one-atomic-in-tcp_wfree.patch | 4 +- ...q-add-a-shortcut-in-tcp_small_queue_check.patch | 2 +- ...tcp-tcp_mtu_probe-is-likely-to-exit-early.patch | 2 +- ...tsq-move-tsq_flags-close-to-sk_wmem_alloc.patch | 14 +- ...add-a-missing-barrier-in-tcp_tasklet_func.patch | 2 +- .../025-tcp-allow-drivers-to-tweak-TSQ-logic.patch | 4 +- ...ort-for-releasing-multiple-instances-of-a.patch | 2 +- ..._alloc_page_frag-to-page_frag_alloc-and-_.patch | 4 +- ..._page_frag-functions-to-__page_frag_cache.patch | 6 +- .../090-net-generalize-napi_complete_done.patch| 8 +- .../generic/hack-4.9/207-disable-modorder.patch| 4 +- .../hack-4.9/211-host_tools_portability.patch | 2 +- .../linux/generic/hack-4.9/220-gc_sections.patch | 4 +- ...c_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch | 2 +- .../pending-4.9/201-extra_optimization.patch | 2 +- ...610-netfilter_match_bypass_default_checks.patch | 6 +- .../pending-4.9/630-packet_socket_type.patch | 6 +- .../generic/pending-4.9/834-ledtrig-libata.patch | 10 +- .../900-gen_stats-fix-netlink-stats-padding.patch | 49 --- .../patches-4.9/600-skb_avoid_dmabounce.patch | 2 +- ...MTD-m25p80-allow-loading-mtd-name-from-OF.patch | 4 +- .../202-core-linux-support-layerscape.patch| 6 +- .../patches-4.9/703-phy-support-layerscape.patch | 2 +- .../patches-4.9/817-usb-support-layerscape.patch | 10 +- .../sunxi/patches-4.9/0052-stmmac-form-4-12.patch | 344 ++--- 39 files changed, 238 insertions(+), 561 deletions(-) delete mode 100644 target/linux/ar71xx/patches-4.9/103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch delete mode 100644 target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch delete mode 100644 target/linux/brcm63xx/patches-4.9/001-4.11-01-mtd-m25p80-consider-max-message-size-in-m25p80_read.patch delete mode 100644 target/linux/brcm63xx/patches-4.9/001-4.15-08-bcm63xx_enet-correct-clock-usage.patch delete mode 100644 target/linux/brcm63xx/patches-4.9/001-4.15-09-bcm63xx_enet-do-not-write-to-random-DMA-channel-on-B.patch delete mode 100644 target/linux/generic/pending-4.9/900-gen_stats-fix-netlink-stats-padding.patch Hi Stijn, The patch is also missing the fix for the possible ext4 corruption issue on newly created filesystems [1] It seems tough that there is no proper backport available yet for this stable tree .. [2] Koen [1] https://github.com/torvalds/linux/commit/5012284700775a4e6e3fbe7eac4c543c4874b559.patch [2] https://www.spinics.net/lists/stable/msg249577.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] kernel: bump 4.14 to 4.14.59 for 18.06
On 2018-07-30 21:31, Stijn Segers wrote: * Refreshed patches. * Patches made redundant by changes upstream: - target/linux/ramips/patches-4.14/0036-mtd-fix-cfi-cmdset-0002-erase-status-check.patch * Patches accepted upstream: - target/linux/apm821xx/patches-4.14/020-0001-crypto-crypto4xx-remove-bad-list_del.patch - target/linux/apm821xx/patches-4.14/020-0011-crypto-crypto4xx-fix-crypto4xx_build_pdr-crypto4xx_b.patch - target/linux/brcm63xx/patches-4.14/001-4.15-08-bcm63xx_enet-correct-clock-usage.patch - target/linux/brcm63xx/patches-4.14/001-4.15-09-bcm63xx_enet-do-not-write-to-random-DMA-channel-on-B.patch - target/linux/generic/backport-4.14/080-net-convert-sock.sk_wmem_alloc-from-atomic_t-to-refc.patch - target/linux/generic/pending-4.14/900-gen_stats-fix-netlink-stats-padding.patch Compile-tested on: ramips/mt7621, x86/64 Run-tested on: ramips/mt7621, x86/64 Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +- ...0001-crypto-crypto4xx-remove-bad-list_del.patch | 32 ...to4xx-remove-unused-definitions-and-write.patch | 2 +- ...to4xx-set-CRYPTO_ALG_KERN_DRIVER_ONLY-fla.patch | 2 +- ...to4xx-remove-double-assignment-of-pd_uinf.patch | 2 +- ...to4xx-enable-AES-RFC3686-ECB-CFB-and-OFB-.patch | 2 +- ...pto4xx-refactor-crypto4xx_copy_pkt_to_dst.patch | 2 +- ...to4xx-replace-crypto4xx_dev-s-scatter_buf.patch | 8 +- ...to4xx-fix-crypto4xx_build_pdr-crypto4xx_b.patch | 84 -- .../802-usb-xhci-force-msi-renesas-xhci.patch | 2 +- ...-add-support-for-performing-fake-doorbell.patch | 2 +- .../patches-4.14/830-huawei_e970_support.patch | 4 +- ...-4.15-08-bcm63xx_enet-correct-clock-usage.patch | 101 ...t-do-not-write-to-random-DMA-channel-on-B.patch | 29 .../025-tcp-allow-drivers-to-tweak-TSQ-logic.patch | 4 +- ...-sock.sk_wmem_alloc-from-atomic_t-to-refc.patch | 172 - ...15-netfilter-exit_net-cleanup-check-added.patch | 2 +- .../generic/hack-4.14/207-disable-modorder.patch | 4 +- .../hack-4.14/211-host_tools_portability.patch | 2 +- .../linux/generic/hack-4.14/220-gc_sections.patch | 2 +- .../linux/generic/hack-4.14/902-debloat_proc.patch | 2 +- ...rocess-negative-stack-offsets-on-stack-tr.patch | 2 +- .../pending-4.14/201-extra_optimization.patch | 2 +- ...610-netfilter_match_bypass_default_checks.patch | 6 +- .../pending-4.14/630-packet_socket_type.patch | 6 +- .../generic/pending-4.14/834-ledtrig-libata.patch | 10 +- .../900-gen_stats-fix-netlink-stats-padding.patch | 49 -- .../patches-4.14/0052-net-phy-add-FC.patch | 2 +- ...ci-allow-imod-interval-to-be-configurable.patch | 2 +- .../oxnas/patches-4.14/999-libata-hacks.patch | 8 +- .../0032-USB-dwc2-add-device_reset.patch | 2 +- ...td-fix-cfi-cmdset-0002-erase-status-check.patch | 29 ...0037-mtd-cfi-cmdset-0002-force-word-write.patch | 2 +- 33 files changed, 44 insertions(+), 540 deletions(-) delete mode 100644 target/linux/apm821xx/patches-4.14/020-0001-crypto-crypto4xx-remove-bad-list_del.patch delete mode 100644 target/linux/apm821xx/patches-4.14/020-0011-crypto-crypto4xx-fix-crypto4xx_build_pdr-crypto4xx_b.patch delete mode 100644 target/linux/brcm63xx/patches-4.14/001-4.15-08-bcm63xx_enet-correct-clock-usage.patch delete mode 100644 target/linux/brcm63xx/patches-4.14/001-4.15-09-bcm63xx_enet-do-not-write-to-random-DMA-channel-on-B.patch delete mode 100644 target/linux/generic/backport-4.14/080-net-convert-sock.sk_wmem_alloc-from-atomic_t-to-refc.patch delete mode 100644 target/linux/generic/pending-4.14/900-gen_stats-fix-netlink-stats-padding.patch delete mode 100644 target/linux/ramips/patches-4.14/0036-mtd-fix-cfi-cmdset-0002-erase-status-check.patch Hi Stijn, Thanks for the patch. The patch is missing the fix for the possible ext4 corruption issue on newly created filesystems [1] Stijn Tintel bumped a kernel update to master adding it, which can be used as a reference [2] Koen [1] https://github.com/torvalds/linux/commit/5012284700775a4e6e3fbe7eac4c543c4874b559.patch [2] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=22b9f99b87fa1ff991180cabf02dd04d1bddce2b ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Arduino support no ttyUSB0 no ttyACM0 :((
On 31/07/2018 10:02, free...@tango.lu wrote: Hello List, I have got a new WRT 1200 AC running LEDE: https://downloads.openwrt.org/releases/17.01.4/targets/mvebu/generic/ Sadly noticed that the ttyUSB ttyACM support is missing. Is there an alternate kernel which has these? If someone precompiled the kernel modul what I can just wget: Firmware Version LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685) Kernel Version 4.4.92 on the router that would be nice although it would be just too easy... I really don't want to go DDwrt on this one. Do you have a vmware/vbox image with all the toolchains to crossbuild the kernel and apps for this platform? Thank you. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel To connect an Arduino to your Lede router you need to install usb-to-serial adapter kernel modules (Linux "drivers"). For most things you will need to install packages to add functions. Please install the following packages (with "opkg install" if you are with terminal or with Luci software page) kmod-usb-serial kmod-usb-serial-ark3116 kmod-usb-serial-belkin kmod-usb-serial-ch341 kmod-usb-serial-cp210x kmod-usb-serial-ftdi kmod-usb-serial-mct kmod-usb-serial-mos7720 kmod-usb-serial-oti6858 kmod-usb-serial-pl2303 kmod-usb-serial-simple kmod-usb-serial-ti-usb And then plug the Arduino again. In practice you will probably need only one of these but I don't know what is the usb-to-serial chip used in your arduino (or clone). They don't need much space anyway, so install all. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Arduino support no ttyUSB0 no ttyACM0 :((
On 2018-07-31 10:02, free...@tango.lu wrote: Hello List, I have got a new WRT 1200 AC running LEDE: https://downloads.openwrt.org/releases/17.01.4/targets/mvebu/generic/ Sadly noticed that the ttyUSB ttyACM support is missing. Is there an alternate kernel which has these? If someone precompiled the kernel modul what I can just wget: Firmware Version LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685) Kernel Version 4.4.92 on the router that would be nice although it would be just too easy... I really don't want to go DDwrt on this one. Do you have a vmware/vbox image with all the toolchains to crossbuild the kernel and apps for this platform? Thank you. did you install the needed kernel modules for usb and/or serial port depending on what your after. also how is openwrt related to arduino? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] ath9k: Max 3 dBi gain for FCC (365-ath9k-adjust-tx-power-reduction-for-US-regulatory-do.patch)
Hi, I've just checked the FCC "antenna reduction workaround" patch [1] in ath9k. The code uses twicepower (.5 dB unit used by QCA) and uses 6 (3dBi) as allowed gain for FCC. The comment also states "FCC allows maximum antenna gain of 3 dBi". Where does the 3dBi come from? 15.247(b)(4) talks about 6 dBi [2]: > (4) The conducted output power limit > specified in paragraph (b) of this section > is based on the use of antennas > with directional gains that do not exceed > 6 dBi. Except as shown in paragraph > (c) of this section, if transmitting > antennas of directional gain greater > than 6 dBi are used, the conducted > output power from the intentional radiator > shall be reduced below the stated > values in paragraphs (b)(1), (b)(2), > and (b)(3) of this section, as appropriate, > by the amount in dB that the > directional gain of the antenna exceeds > 6 dBi. Btw. I am not sure whether all countries which use the FCC DFS rules also use the same antenna gain limits. But let us assume for now that this is ok. Kind regards, Sven [1] https://github.com/openwrt/openwrt/blob/81542331cb1827650f3abd69375d964d0ce2d050/package/kernel/mac80211/patches/365-ath9k-adjust-tx-power-reduction-for-US-regulatory-do.patch [2] https://www.gpo.gov/fdsys/pkg/CFR-2013-title47-vol1/pdf/CFR-2013-title47-vol1-sec15-247.pdf signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 6rd issues with 18.06-rc2 on ubnt-erx-sfp
On 2018-07-31 10:01, Hans Dedecker wrote: On Mon, Jul 30, 2018 at 12:02 AM Torbjorn Jansson wrote: On 2018-07-29 22:16, Hans Dedecker wrote: On Fri, Jul 27, 2018 at 2:36 PM Torbjorn Jansson wrote: Hello i decided to try to upgrade my erx-sfp from an old snapshot (probably a year or so old) to 18.06-rc2. for the most part it worked out but there is something odd going on with my 6rd wan interface and i'm not sure where to start the troubleshooting. with luci-proto-ipv6 and 6rd packages installed i get a lot of stuff like this in syslog: 14:29:07 2018 daemon.notice netifd: wan6 (24771): Command failed: Unknown error 14:29:07 2018 daemon.notice netifd: Interface 'wan6' is now down 14:29:07 2018 daemon.notice netifd: Interface 'wan6' is setting up now 14:29:08 2018 daemon.notice netifd: wan6 (24856): Command failed: Unknown error 14:29:08 2018 daemon.notice netifd: Interface 'wan6' is now down 14:29:08 2018 daemon.notice netifd: Interface 'wan6' is setting up (dates removed to make log easier to fit in mail without line breaks) this repeats every second and 6rd interface seems to get ip adress but it is not quite working. plus i noticed under Network -> Interfaces in webinterface i now have two similar looking 6rd interfaces. one named WAN6 and thats the one i created and another one that cant be edited that's called WAN_6 WAN6 is listed as protocol: IPv6-over-IPv4 (6rd) WAN_6 is listed as protocol: Virtual dynamic interface (IPv6-over-IPv4 (6rd)) the last interface must be something new or a problem or something. it is also that interface that gets the ipv6 addresses. any idea whats wrong? or how to find out what command failed in the log? Hi, You cannot enable both an automatic 6rd interface (wan_6) and a manual created 6rd interface (wan6); Either remove the manual created 6rd interface or set iface6rd to 0 in the wan network config which will disable the automatic creation of the 6rd wan_6 interface Hans i'm not sure i get it. where is the auto created 6rd interface that can't be edited coming from if not from the one i created myself? The auto created 6rd interface is created by the dhcp script (https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/network/config/netifd/files/lib/netifd/dhcp.script;h=00604f40e70e8ba988bde6af04437d326b5b548a;hb=HEAD#l62) in case the 6rd DHCP option is received. So it seems your ISP is providing 6rd info via DHCP oh, i see. i'm not sure if isp always provided it or if the auto created 6rd interface in openwrt from dhcp is a new thing. i know that when i initially set it up a long time ago i did not get anything auto created. i was under the impression my isp considered 6rd to be experimental. the errors stopped once i changed "bring up on boot" on wan6 and ipv6 still works (after reboot) but i don't understand why. This confirms my statement above about 6rd info being provided by DHCP the config i'm running with is exactly the same as i had on old version of openwrt/lede and it worked just fine. i guess something is different now. Pretty sure nothing has changed recently related to the 6rd logic; I guess it's a race condition between the wan_6 and wan6 interface which was before not visible if i delete wan6 then I delete all 6rd settings like remote ipv4 address, the ipv6 prefix and so on. If the automatic created 6rd interface gives you IPv6 connectivity there's no reason to keep the manual created wan6 interface Hans i will try to delete it and see what happens. but first id like to take a look at the dhcp reply i get from my isp. maybe i can run a tcpdump or something to catch it as it renews. thanks for explaining. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Arduino support no ttyUSB0 no ttyACM0 :((
Hello List, I have got a new WRT 1200 AC running LEDE: https://downloads.openwrt.org/releases/17.01.4/targets/mvebu/generic/ Sadly noticed that the ttyUSB ttyACM support is missing. Is there an alternate kernel which has these? If someone precompiled the kernel modul what I can just wget: Firmware Version LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685) Kernel Version 4.4.92 on the router that would be nice although it would be just too easy... I really don't want to go DDwrt on this one. Do you have a vmware/vbox image with all the toolchains to crossbuild the kernel and apps for this platform? Thank you. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 6rd issues with 18.06-rc2 on ubnt-erx-sfp
On Mon, Jul 30, 2018 at 12:02 AM Torbjorn Jansson wrote: > > On 2018-07-29 22:16, Hans Dedecker wrote: > > On Fri, Jul 27, 2018 at 2:36 PM Torbjorn Jansson > > wrote: > >> > >> Hello > >> > >> i decided to try to upgrade my erx-sfp from an old snapshot (probably a > >> year or > >> so old) to 18.06-rc2. > >> for the most part it worked out but there is something odd going on with > >> my 6rd > >> wan interface and i'm not sure where to start the troubleshooting. > >> > >> with luci-proto-ipv6 and 6rd packages installed i get a lot of stuff like > >> this > >> in syslog: > >> 14:29:07 2018 daemon.notice netifd: wan6 (24771): Command failed: Unknown > >> error > >> 14:29:07 2018 daemon.notice netifd: Interface 'wan6' is now down > >> 14:29:07 2018 daemon.notice netifd: Interface 'wan6' is setting up now > >> 14:29:08 2018 daemon.notice netifd: wan6 (24856): Command failed: Unknown > >> error > >> 14:29:08 2018 daemon.notice netifd: Interface 'wan6' is now down > >> 14:29:08 2018 daemon.notice netifd: Interface 'wan6' is setting up > >> (dates removed to make log easier to fit in mail without line breaks) > >> > >> this repeats every second and 6rd interface seems to get ip adress but it > >> is > >> not quite working. > >> > >> plus i noticed under Network -> Interfaces in webinterface i now have two > >> similar looking 6rd interfaces. > >> one named WAN6 and thats the one i created and another one that cant be > >> edited > >> that's called WAN_6 > >> > >> WAN6 is listed as protocol: IPv6-over-IPv4 (6rd) > >> WAN_6 is listed as protocol: Virtual dynamic interface (IPv6-over-IPv4 > >> (6rd)) > >> > >> the last interface must be something new or a problem or something. > >> it is also that interface that gets the ipv6 addresses. > >> > >> > >> any idea whats wrong? > >> or how to find out what command failed in the log? > > Hi, > > > > You cannot enable both an automatic 6rd interface (wan_6) and a manual > > created 6rd interface (wan6); Either remove the manual created 6rd > > interface or set iface6rd to 0 in the wan network config which will > > disable the automatic creation of the 6rd wan_6 interface > > > > Hans > > i'm not sure i get it. > where is the auto created 6rd interface that can't be edited coming from if > not > from the one i created myself? The auto created 6rd interface is created by the dhcp script (https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/network/config/netifd/files/lib/netifd/dhcp.script;h=00604f40e70e8ba988bde6af04437d326b5b548a;hb=HEAD#l62) in case the 6rd DHCP option is received. So it seems your ISP is providing 6rd info via DHCP > > the errors stopped once i changed "bring up on boot" on wan6 and ipv6 still > works (after reboot) but i don't understand why. This confirms my statement above about 6rd info being provided by DHCP > > the config i'm running with is exactly the same as i had on old version of > openwrt/lede and it worked just fine. > i guess something is different now. Pretty sure nothing has changed recently related to the 6rd logic; I guess it's a race condition between the wan_6 and wan6 interface which was before not visible > if i delete wan6 then I delete all 6rd settings like remote ipv4 address, the > ipv6 prefix and so on. If the automatic created 6rd interface gives you IPv6 connectivity there's no reason to keep the manual created wan6 interface Hans ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
