Re: [OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update

Hi, On Thu, Apr 12, 2018 at 1:02 PM, John Crispin wrote: > try enabling KALLSYMS to get a verbose stack trace. Thanks for the pointer. I compiled a new image KALLSYMS, but now I am not able to reproduce the error. Perhaps there was something dirty in my build directory. I will

[OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update

Hello, I have recently updated some ramips mt7621-devices (ZBT WG3526) to the latest nightly. Almost everything seems to work fine, but using either wifi interface in client mode seems triggers an oops. I see two different oops-messages: Message 1: [ 66.442802] CPU 1 Unable to handle kernel

[OpenWrt-Devel] [PATCH] x86: Add APU3 reference to x86 board.d

There is a new APU-model available, APU3. The device is configured in the same way as the APU1 and APU2, so the same LED/network setup can be used. I considered changing the case to pc-engines-apu*, but I chose to follow the existing pattern and add the full board name. Signed-off-by: Kristian

[OpenWrt-Devel] [PATCH v3] ramips: Add support for ZBT WG3526

From: Kristian Evensen <kristian.even...@gmail.com> The WG3526 is the follow-up to the 2626 and is mostly the same, with the excaption that the mt7602 has been replaced with the mt7603. The internal wifi setup has also changed slightly. Based on my tests, everything that worked on the 2626

Re: [OpenWrt-Devel] [PATCH] [ramips] Adjust image size limit for the D-Link DIR-860L B1

Hi, On Thu, Mar 31, 2016 at 12:47 AM, Daniel Engberg wrote: > Currently the maximum image size defaults to 8Mbyte even though this model > has 16Mbyte of flash memory. Something has gone wrong when merging this patch (look at the Makefile in the upstream

[OpenWrt-Devel] [PATCH v2] ramips: Add support for ZBT WG3526

From: Kristian Evensen <kristian.even...@gmail.com> The WG3526 is the follow-up to the 2626 and is mostly the same, with the excaption that the mt7602 has been replaced with the mt7603. The internal wifi setup has also changed slightly. Based on my tests, everything that worked on the 2626

[OpenWrt-Devel] [PATCH] ramips: Add support for ZBT WG3526

From: Kristian Evensen <kristian.even...@gmail.com> The WG3526 is the follow-up to the 2626 and is mostly the same, with the excaption that the mt7602 has been replaced with the mt7603. The internal wifi setup has also changed slightly. Based on my tests, everything that worked on the 2626

[OpenWrt-Devel] [PATCH] ramips: Incorrect file mode change

From: Kristian Evensen <kristian.even...@gmail.com> Commit d0f5ab6d95a1 ("ramips: Added support for ZBT-826 / ZBT-1026") incorrectly changed the mode of the ramips shell scripts from 755 to 644. I.e., they are not excutable any more and for example devices will be left wit

[OpenWrt-Devel] [PATCH] netifd: Route traffic from LAN to WAN using rules

From: Kristian Evensen <kristian.even...@gmail.com> After commit ebd3d8417c7a ("interface: fix moving interface address routes to the table specified by ip[46]table"), it is no longer possible for clients on LAN to reach machines on the WAN. This patch restores support fo

[OpenWrt-Devel] [PATCH] netifd: Do not add local/source policy rules multiple times

From: Kristian Evensen <kristian.even...@gmail.com> interface_ip_set_enabled() is usually called two times right after one another, once to handle config_ip and once to handle proto_ip. As long as ip->iface->l3_dev.dev is set, the local/source policy rules are updated. This value i

[OpenWrt-Devel] Issue with kernel 4.1/4.4 on Linksys-routers

Hello, I tried to compile and test trunk on two Linksys-routers (1200AC and 1900ACv2). After manually enabling the Generic Thermal sysfs driver, compilation went fine. However, none of the routers want to boot. Hooking up a serial shows what seems to be a filsystem issue, the following error is

Re: [OpenWrt-Devel] [PATCH netifd 3/6] interface-ip: Remove ip loop policy rules as kernel issue is fixed

Hi, On Wed, Sep 9, 2015 at 3:45 PM, Hans Dedecker wrote: > Remove ip loop policy rules as workaround for the kernel using unspecified > address > to lookup locally originating traffic is fixed by > http://lkml.iu.edu/hypermail/linux/kernel/1505.0/03094.html > >

Re: [OpenWrt-Devel] [PATCH netifd 2/6] iprule: Insert network and address ip rules before main table lookup rule

On Wed, Sep 23, 2015 at 1:07 PM, Hans Dedecker wrote: > Indeed we're using source based routing in combination with a default route > in the main routing table; even the specific routing table(s) can contain a > default route > Based on the addr rule the traffic is guided to a

Re: [OpenWrt-Devel] [PATCH netifd 2/6] iprule: Insert network and address ip rules before main table lookup rule

Hi, On Wed, Sep 9, 2015 at 3:45 PM, Hans Dedecker wrote: > Specific IP address and network rules are now checked before the main table > lookup as the main table > often holds a default route. As a result the IP address and network rules > pointing to s specific > routing

Re: [OpenWrt-Devel] [PATCH netifd 2/6] iprule: Insert network and address ip rules before main table lookup rule

On Wed, Sep 23, 2015 at 1:23 PM, Kristian Evensen <kristian.even...@gmail.com> wrote: > On Wed, Sep 23, 2015 at 1:07 PM, Hans Dedecker <dedec...@gmail.com> wrote: >> Indeed we're using source based routing in combination with a default route >> in the main routing table

Re: [OpenWrt-Devel] [PATCH netifd 2/6] iprule: Insert network and address ip rules before main table lookup rule

Sorry about partial reply, clumsy fingers. On Wed, Sep 23, 2015 at 11:31 AM, Hans Dedecker wrote: > Can you share the uci network config and ifstatus of the different > interfaces ? UCI config is nothing more than ... proto dhcp ... ip4/ip6table X >> >> >> I don't see any

[OpenWrt-Devel] [PATCH] netifd: Prevent flapping IPv6 routes

From: Kristian Evensen <kristian.even...@gmail.com> Comparing valid_until will always return false as the value is updated for each route update message. This causes IPv6 routes to jump more around than House of Pain, which might have undesirable consequences for user-space and user

Re: [OpenWrt-Devel] [PATCH] mvebu: add config and patches for kernel 4.1

Hi, On Fri, Sep 11, 2015 at 3:31 PM, Daniel Golle wrote: > I assume you did make sure that these two flaws are actually > regressions, i.e. both worked on 3.18, right? Yes, everything worked fine on 3.18. I am compiling a new image now and will send dmesg output when that

Re: [OpenWrt-Devel] [PATCH] mvebu: add config and patches for kernel 4.1

Hi, I tested this patch on my WRT1200AC and it seems to work fine, with one exception. For some reason, the WAN (eth0) always has L2 state DOWN (confirmed by ip link), even though WAN is connected and working fine (verified with USB dongle). Any tips on how to proceed to fix this? As a side not,

Re: [OpenWrt-Devel] [PATCH] netifd: Set source IP for DHCP default route

On Wed, Dec 10, 2014 at 9:10 AM, Hans Dedecker dedec...@gmail.com wrote: As a side effect of this patch I noticed multiple default routes (one default route with source IP set and one default route with source IP unset) are present in netifd if the dhcp server replies the default route both in

[OpenWrt-Devel] [PATCH] netifd: Pass source address to proto_add_ipv4_route

From: Kristian Evensen kristian.even...@gmail.com Enable callers to pass the source IP of an IPv4 route when using proto_add_ipv4_route(). This is useful with for example DHCP in a multihomed scenario, as it provides an easy way to match default routes with the correct IP address. One use case

[OpenWrt-Devel] [PATCH] netifd: Set source IP for DHCP default route

From: Kristian Evensen kristian.even...@gmail.com This patch depends on Pass source address to proto_add_ipv4_route. I have not found a scenario that would break by setting the source address on default, but please let me know if any special considerations should be taken. Signed-off

[OpenWrt-Devel] [PATCH] netifd: Fix source routing

DELROUTE. Store the source address in RTA_PREFSRC, so that option works as specified in documentation. Signed-off-by: Kristian Evensen kristian.even...@gmail.com --- system-linux.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/system-linux.c b/system-linux.c index 83827d5

Re: [OpenWrt-Devel] [PATCH] netifd: Fix source routing

On Tue, Nov 25, 2014 at 8:47 PM, Steven Barth cy...@openwrt.org wrote: Maybe we should use RTA_PREFSRC for IPv4 and RTA_SRC for IPv6? Sounds good to me. I am not to familiar with configuring IPv6, so I was not aware that RTA_SRC is used differently there. If no-one else jumps in before me, I

Re: [OpenWrt-Devel] ar71xx: Problems with USB WIFI dongles

Hi all, On Sat, Aug 9, 2014 at 12:03 PM, Kristian Evensen kristian.even...@gmail.com wrote: 2) When disconnecting any WIFI dongle, I always get a kernel oops. This happens irrespective of if the dongle is active (for example connected to network) or if I have just connected it to the router

[OpenWrt-Devel] ar71xx: Problems with USB WIFI dongles

Hello, I am currently working on a small project and I have come across a problem I have not been able to solve myself. My setup is as following, I have a TP-LINK WDR4300 (so ar71xx) router that will be used as an access point to share a WAN connection. The WAN connection is a different wifi. My

Re: [OpenWrt-Devel] [RFC netifd] Out-of-sync reference counter causes seg. fault

Hi Felix, On Sun, Jun 29, 2014 at 8:36 PM, Felix Fietkau n...@openwrt.org wrote: Please test the latest version and check if that hack is still necessary. Thanks for your reply. I tested with latest netifd and latest libubus, to make sure that I got the reload-fixes. The issue is unfortunately

Re: [OpenWrt-Devel] [RFC netifd] Out-of-sync reference counter causes seg. fault

On Sun, Jun 29, 2014 at 11:19 PM, Felix Fietkau n...@openwrt.org wrote: Thanks for the info about the commit that broke it, now this issue makes more sense to me. Please try this patch: With this patch everything works fine, I do not see the crash any more. Thanks for the help! -Kristian

[OpenWrt-Devel] [RFC netifd] Out-of-sync reference counter causes seg. fault

From: Kristian Evensen kristian.even...@gmail.com Hello, I have written a small tool which automatically adds/removes a usb LAN dongle from uci. When the USB device is inserted, I add entries to UCI (using libuci) and do network reload (using libubus). When the device is removed, I remove

Re: [OpenWrt-Devel] Question about the /tmp/resolv.conf.auto file

Hi, On Mon, Mar 31, 2014 at 11:39 AM, banglang huang banglang.hu...@gmail.com wrote: And I want to learn how this file can be generated and why the openwrt knows the dns ip address automatically (nameserver) ?? This file is generated by the network interface daemon (netifd) in the

Re: [OpenWrt-Devel] Question about the /tmp/resolv.conf.auto file

Hi, On Mon, Mar 31, 2014 at 11:58 AM, Tymon banglang.hu...@foxmail.com wrote: How can it retrieve the nameserver in 'DHCP' way ? When a nameserver is retrieved through DHCP, it is part of the reply sent by the DHCP server. It is set (and communicated to) netifd through the

[OpenWrt-Devel] [PATCH] Enable compiling iptables nfacct support

From: Kristian Evensen kristian.even...@gmail.com This patch adds the userspace and kernelspace match for nfacct, the extended accounting infrastructure. Signed-off-by: Kristian Evensen kristian.even...@gmail.com --- package/kernel/linux/modules/netfilter.mk | 21 + package

[OpenWrt-Devel] Netifd and SIGSEV with 3G/PPP modems

Hello, I have spent some days debugging an issue I am frequently seeing with netifd and ppp modems. When connecting the modem after having connected and disconnected it once, i.e., the second time netifd sees the modem, netifd frequently thows a sigsev. After going through the code, adding

Re: [OpenWrt-Devel] USB instabilities on Atheros AR9344

Hi Michel, Thank you very much for a quick reply and sorry for my late reply. I was without internet and access to the device yesterday. On Fri, Nov 29, 2013 at 6:21 PM, Michel Stempin michel.stem...@wanadoo.fr wrote: Are your devices and hubs enumerated as full or high-speed? They are all

Re: [OpenWrt-Devel] USB instabilities on Atheros AR9344

Hi again, On Fri, Nov 29, 2013 at 6:21 PM, Michel Stempin michel.stem...@wanadoo.fr wrote: What happens if you turn off the WiFi during this time? When looking through the config, I just noticed that wifi has always been turned off. -Kristian ___

[OpenWrt-Devel] USB instabilities on Atheros AR9344

Hello, I am currently working on an embedded project based on the Atheros AR9344 SoC. As a prototype device, we are using the TP-Link TL-WDR4300 router (http://wiki.openwrt.org/toh/tp-link/tl-wdr4300) and latest OpenWRT trunk. The kernel is 3.10.18. We have over the last couple of weeks

[OpenWrt-Devel] [PATCH libubox/uloop v2] Restore signal handler after uloop_run()

From: Kristian Evensen kristian.even...@gmail.com uloop_run calls uloop_setup_signals() to set up signal handling before the while loop, but does not remove the signal handling after the loop has ended. This can cause problems for for example applications using the ubus file descriptor

[OpenWrt-Devel] [PATCH libubox/uloop] Remove signal handle after uloop_run()

From: Kristian Evensen kristian.even...@gmail.com uloop_run calls uloop_setup_signals() to set up signal handling before the while loop, but does not remove the signal handling after the loop has ended. This can cause problems for for example applications using the ubus file descriptor

Re: [OpenWrt-Devel] Understanding/reimplementing forwarding acceleration used by Broadcom (ctf)

Hi Rafael, I will just reply to both emails here. First, it seems as though my ebtables knowledge has gotten a bit rusty and there were some details I forgot. The tool is used for firewalling bridges, so, the LAN and WAN interface has to make up a bridge. I succeeded with a simple configuration

Re: [OpenWrt-Devel] Understanding/reimplementing forwarding acceleration used by Broadcom (ctf)

Hi Rafal, On Sat, Aug 24, 2013 at 5:19 PM, Rafał Miłecki zaj...@gmail.com wrote: I wonder what do you think about this solution. Is this something we could try to implement ourself? Is it worth it? Is there some existing project doing similar thing? This is a very interesting discovery. Have

[OpenWrt-Devel] [PATCH] Make generic multi-wan work properly with overlapping subnets

Hi, The current generic multi-wan implementation does not work properly when a device is connected to multiple overlapping subnets. Reaching machines outside the networks work, but attempts to reach machines inside the networks will always go through the first interface that was added with the

[OpenWrt-Devel] [PATCH] Netifd: Generic multi-wan support v3

This patch implements the comments received for version 1 (see https://lists.openwrt.org/pipermail/openwrt-devel/2013-May/020119.html), and improves upon version 2 by respecting metrics. * Routes are only added to the specified table. The only exception are the IPv4-routes Linux automatically

[OpenWrt-Devel] [PATCH] Netifd: Generic multi-wan support v2

From: Kristian Evensen kristian.even...@gmail.com This patch implements the comments received for version 1 (see https://lists.openwrt.org/pipermail/openwrt-devel/2013-May/020119.html). * Routes are only added to the specified table. The only exception are the IPv4-routes Linux generates

[OpenWrt-Devel] [PATCH] Netifd: Generic multi-wan support

From: Kristian Evensen kristian.even...@gmail.com Multi-wan support was recently added to netifd, but limited to IPv6. This patch enables multi-wan for IPv4 as well. In addition, the patch introduces some changes that make the multi-wan support more robust. 1) Instead of using the interface

<    1   2