Re: [OpenWrt-Devel] We are seeking bandwith per user configuration
Yes sure shell script is ok payment is up to you my dear friend tell me what payment will get you happy :) I like to use OpenWRT to reserve seperate bandwith to our workers in office building all of the people is disabled by default some people permitted to access to the internet from MAC address but permitted people will use dhcp IP and seperate dedicated bandwith for their MAC (but not grouped band with becouse if some one in that group use torrend others complainig) I like to see permitted users MAC list with each ones DL UL ider on a config file or in an Luci admin page :) My best regars Atilla Oguz Ersoz - Original Message - From: Bastian Bittorf bitt...@bluebottle.com To: Oguz Ersoz atilla.o.er...@gmail.com Sent: Wednesday, May 15, 2013 10:40 AM Subject: Re: [OpenWrt-Devel] We are seeking bandwith per user configuration * Oguz Ersoz atilla.o.er...@gmail.com [15.05.2013 09:31]: we seek some one to configure OpenWRT to basic queue list and limit each users DL UL for mac address if any one able to do it please get in touch with me example 3 user is enough for us user1 AA-AA-AA-B2-DA-08DL=4000 UL=400 user2AA-AA-AA-B2-DA-09DL=1000 UL=100 user3AA-AA-AA-B2-DA-10DL=512 UL=50 We use this setup too [1]. is a shell-script ok for you? what is your proposal for paying us? bye, bastian [1] https://github.com/bittorf/kalua ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attitude Adjustment (r36608) Configuration config problems
On 05/15/2013 02:15 AM, cmsv wrote: I have encountered the following problems while compiling images: The reason being is for example that the network configuration file for a dlink is not fully the same as for example tp-link. Having any of these config files in buildroot dir/files/config/ will eventually brick routers that for example have a different switch configuration; will fail working properly for wireless and have functioning problems with system. These files exist in buildroot dir/package/base-files/files/etc/ and while building the image they get merged with the specifics of the hardware. My question is if we can have the same merging task done while having buildroot dir/files/ . Have you considered either...? a) use ./scripts/env to mantain a different set of /files for each model or b) use an /etc/uci-defaults/smart-template.sh : it can check the hardware model where it is running live, and apply the config based on that information Hope that helps ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] gpsd: Bump version to 3.9
This patch bumps gpsd version to 3.9. Signed-off-by: Sebastian Muszynski ba...@linkt.de --- Index: feeds/packages/net/gpsd/Makefile === --- feeds/packages/net/gpsd/Makefile(revision 36638) +++ feeds/packages/net/gpsd/Makefile(working copy) @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=gpsd -PKG_VERSION:=3.7 +PKG_VERSION:=3.9 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://download-mirror.savannah.gnu.org/releases/gpsd -PKG_MD5SUM:=52d9785eaf1a51298bb8900dbde88f98 +PKG_MD5SUM:=53a88f24a0973d23427e82e9a8914f19 PKG_BUILD_DEPENDS:=libncurses libusb-1.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[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 index to decide on interface metric, a
table-option is added to interfaces. This way, users are sure which tables will
be used for policy routing and can avoid overlaps. The table-option must be set
for an interface to be 'multi-wan', and all routes belonging to the interface
will be added to this table.
2) Routes are added both to the original table (for example main) and the
interface-specific table. This is done to ensure networked applications running
on the node will behave as intended. If routes are only added to the
interface-specific tables, traffic from applications not binding to an interface
will not be routed correctly.
The IPv6 multi-wan support has been converted to use the generic functions.
---
interface-ip.c | 35 +++
interface.c| 10 ++
interface.h| 4
proto.c| 1 +
system-linux.c | 28 ++--
5 files changed, 60 insertions(+), 18 deletions(-)
diff --git a/interface-ip.c b/interface-ip.c
index e265563..f88162b 100644
--- a/interface-ip.c
+++ b/interface-ip.c
@@ -90,16 +90,19 @@ match_if_addr(union if_addr *a1, union if_addr *a2, int
mask)
return !memcmp(p1, p2, sizeof(*p1));
}
-static int set_ipv6_source_policy(bool add, const union if_addr *addr, uint8_t
mask, int ifindex)
+static int set_ip_source_policy(bool add, bool v4, const union if_addr *addr,
+uint8_t mask, int ifindex, unsigned int table)
{
struct iprule rule = {
- .flags = IPRULE_INET6 | IPRULE_SRC | IPRULE_LOOKUP |
IPRULE_PRIORITY,
+ .flags = IPRULE_SRC | IPRULE_LOOKUP | IPRULE_PRIORITY,
.priority = 65535,
- .lookup = interface_ip_resolve_v6_rtable(ifindex),
+ .lookup = table,
.src_addr = *addr,
.src_mask = mask,
};
+ rule.flags |= (v4) ? IPRULE_INET4 : IPRULE_INET6;
+
return (add) ? system_add_iprule(rule) : system_del_iprule(rule);
}
@@ -267,6 +270,7 @@ interface_ip_add_route(struct interface *iface, struct
blob_attr *attr, bool v6)
if (!route)
return;
+ route-iface = iface;
route-flags = v6 ? DEVADDR_INET6 : DEVADDR_INET4;
route-mask = v6 ? 128 : 32;
if ((cur = tb[ROUTE_MASK]) != NULL) {
@@ -433,8 +437,11 @@ interface_update_proto_addr(struct vlist_tree *tree,
if (!(a_old-flags DEVADDR_EXTERNAL) a_old-enabled
!keep) {
interface_handle_subnet_route(iface, a_old, false);
- if ((a_old-flags DEVADDR_FAMILY) == DEVADDR_INET6)
- set_ipv6_source_policy(false, a_old-addr,
a_old-mask, dev-ifindex);
+ if(iface-interface_table 0){
+ bool v4 = (a_old-flags DEVADDR_FAMILY) ==
DEVADDR_INET4;
+ set_ip_source_policy(false, v4, a_old-addr,
a_old-mask,
+ dev-ifindex,
iface-interface_table);
+ }
system_del_address(dev, a_old);
}
@@ -446,8 +453,11 @@ interface_update_proto_addr(struct vlist_tree *tree,
if (!(a_new-flags DEVADDR_EXTERNAL) !keep) {
system_add_address(dev, a_new);
- if ((a_new-flags DEVADDR_FAMILY) == DEVADDR_INET6)
- set_ipv6_source_policy(true, a_new-addr,
a_new-mask, dev-ifindex);
+ if(iface-interface_table 0){
+ bool v4 = (a_new-flags DEVADDR_FAMILY) ==
DEVADDR_INET4;
+ set_ip_source_policy(true, v4, a_new-addr,
a_new-mask,
+ dev-ifindex,
iface-interface_table);
+ }
if ((a_new-flags DEVADDR_OFFLINK) || iface-metric)
interface_handle_subnet_route(iface, a_new,
true);
@@ -758,8 +768,9 @@ interface_update_prefix(struct vlist_tree *tree,
// Set null-route to avoid routing loops and set routing policy
system_add_route(NULL, route);
if (prefix_new-iface)
- set_ipv6_source_policy(true, route.addr, route.mask,
- prefix_new-iface-l3_dev.dev-ifindex);
+ set_ip_source_policy(true, false, route.addr,
route.mask,
+ prefix_new-iface-l3_dev.dev-ifindex,
+ prefix_new-iface-interface_table);
[OpenWrt-Devel] [PATCH] mac82011: Fix auto channel selection for dual band cards
From: Sujith Manoharan c_man...@qca.qualcomm.com
Use the HW mode to determine which channel to choose
when the card is dual-band, otherwise, a channel from
the 2GHz band would be chosen when hwmode is set to 11a or 11na.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
package/mac80211/files/lib/wifi/mac80211.sh | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/package/mac80211/files/lib/wifi/mac80211.sh
b/package/mac80211/files/lib/wifi/mac80211.sh
index a052a1c..7a6f05c 100644
--- a/package/mac80211/files/lib/wifi/mac80211.sh
+++ b/package/mac80211/files/lib/wifi/mac80211.sh
@@ -19,12 +19,6 @@ mac80211_hostapd_setup_base() {
[ -n $channel -a -z $hwmode ] wifi_fixup_hwmode $device
- [ $channel = auto ] {
- channel=$(iw phy $phy info | \
- sed -ne '/MHz/ { /disabled\|passive\|radar/d; s/.*\[//;
s/\].*//; p; q }')
- config_set $device channel $channel
- }
-
[ -n $hwmode ] {
config_get hwmode_11n $device hwmode_11n
[ -n $hwmode_11n ] {
@@ -43,6 +37,20 @@ mac80211_hostapd_setup_base() {
}
}
+ [ $channel = auto ] {
+ case $hwmode in
+ b|g)
+ channel=$(iw phy $phy info | \
+ sed -ne '/MHz/ {
/^.*5.*\|disabled\|passive\|radar/d; s/.*\[//; s/\].*//; p; q }')
+ ;;
+ a)
+ channel=$(iw phy $phy info | \
+ sed -ne '/MHz/ {
/^.*2.*\|disabled\|passive\|radar/d; s/.*\[//; s/\].*//; p; q }')
+ ;;
+ esac
+ config_set $device channel $channel
+ }
+
local country_ie=0
[ -n $country ] country_ie=1
config_get_bool country_ie $device country_ie $country_ie
--
1.8.2.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Multi-homing routers
Hi everyone, I am looking for a home router that can have multiple interfaces used as WAN ports for multi-homing applications (behind multiple ISPs). By strictly home routers I mean Linksys, Netgear, D-link, and the like; something that the beginner to average user would be able to easily find on Amazon, etc. (and not devices like http://www.pcengines.ch/index.htm, http://routerboard.com/ or http://soekris.com/). I have tried to assign a LAN port as a virtual WAN but have ran into problems when the intf goes down and up again... Thanks! Vasilis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 0/2] Add new target for i.MX23-based boards
This revised patchset will add support for i.MX23-based boards, starting with Olimex Olinuxino. This is an ARM9-based board which comes in different flavours depending on devices and expansion ports. Currently supported: - 3.8.11 kernel - ext4 rootfs - USB - ethernet - RTC Work in progress for: - I2C - SPI - probably sound and FB Patch list: [PATCH 1/2]: Add tools support for i.MX23 [PATCH 2/2]: Add target for i.MX23 Regards, Zoltan Herpai ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] [tools]: Add tools support for i.MX23
Add tools support for booting up an i.MX23-based board via bootlets.
Signed-off-by: Zoltan HERPAI wigy...@uid0.hu
---
Index: package/imx-bootlets/patches/003-add-olinuxino.diff
===
--- package/imx-bootlets/patches/003-add-olinuxino.diff (revision 0)
+++ package/imx-bootlets/patches/003-add-olinuxino.diff (revision 0)
@@ -0,0 +1,171 @@
+diff -ruN imx-bootlets-10.05.02.orig/linux.db
imx-bootlets-10.05.02/linux.db
+--- imx-bootlets-10.05.02.orig/linux.db2010-05-14 06:56:28.0
+0200
imx-bootlets-10.05.02/linux.db 2012-10-27 01:35:55.0 +0200
+@@ -1,10 +1,10 @@
+-// STMP378x ROM command script to load and run Linux kernel
++// IMX23_OLINUXINO ROM command script to load and run Linux kernel
+
+ sources {
+ power_prep=./power_prep/power_prep;
+ sdram_prep=./boot_prep/boot_prep;
+ linux_prep=./linux_prep/output-target/linux_prep;
+- zImage=/home/b18647/repos/ltib_latest/rootfs/boot/zImage;
++ zImage=../../kernel/linux-3.6-rc1/arch/arm/boot/zImage;
+ }
+
+ section (0) {
+diff -ruN
imx-bootlets-10.05.02.orig/linux_prep/board/imx23_olinuxino_dev.c
imx-bootlets-10.05.02/linux_prep/board/imx23_olinuxino_dev.c
+--- imx-bootlets-10.05.02.orig/linux_prep/board/imx23_olinuxino_dev.c
1970-01-01 01:00:00.0 +0100
imx-bootlets-10.05.02/linux_prep/board/imx23_olinuxino_dev.c
2012-10-27 01:35:55.0 +0200
+@@ -0,0 +1,54 @@
++/*
++ * Platform specific data for the IMX23_OLINUXINO development board
++ *
++ * Fadil Berisha fadil.r.beri...@gmail.com
++ *
++ * Copyright 2008 SigmaTel, Inc
++ * Copyright 2008 Embedded Alley Solutions, Inc
++ * Copyright 2009-2010 Freescale Semiconductor, Inc. All Rights Reserved.
++ *
++ * This file is licensed under the terms of the GNU General Public License
++ * version 2. This program is licensed as is without any warranty of any
++ * kind, whether express or implied.
++ *
++ * http://www.opensource.org/licenses/gpl-license.html
++ * http://www.gnu.org/copyleft/gpl.html
++ */
++#include setup.h
++#include keys.h
++#include lradc_buttons.h
++
++/
++ * LRADC keyboard data *
++ /
++int lradc_keypad_ch = LRADC_CH0;
++int lradc_vddio_ch = LRADC_CH6;
++
++struct lradc_keycode lradc_keycodes[] = {
++ { 100, KEY4 },
++ { 306, KEY5 },
++ { 601, KEY6 },
++ { 932, KEY7 },
++ { 1260, KEY8 },
++ { 1424, KEY9 },
++ { 1707, KEY10 },
++ { 2207, KEY11 },
++ { 2525, KEY12 },
++ { 2831, KEY13 },
++ { 3134, KEY14 },
++ { -1, 0 },
++};
++
++/
++ * Magic key combinations for Armadillo *
++ /
++u32 magic_keys[MAGIC_KEY_NR] = {
++ [MAGIC_KEY1] = KEY4,
++ [MAGIC_KEY2] = KEY6,
++ [MAGIC_KEY3] = KEY10,
++};
++
++/
++ * Default command line *
++ /
++char cmdline_def[] = console=ttyAMA0,115200;
+diff -ruN
imx-bootlets-10.05.02.orig/linux_prep/cmdlines/imx23_olinuxino_dev.txt
imx-bootlets-10.05.02/linux_prep/cmdlines/imx23_olinuxino_dev.txt
+---
imx-bootlets-10.05.02.orig/linux_prep/cmdlines/imx23_olinuxino_dev.txt
1970-01-01 01:00:00.0 +0100
imx-bootlets-10.05.02/linux_prep/cmdlines/imx23_olinuxino_dev.txt
2012-10-27 01:35:55.0 +0200
+@@ -0,0 +1,3 @@
++noinitrd console=ttyAMA0,115200 root=/dev/mmcblk0p2 rw rootwait ssp1=mmc
++noinitrd console=ttyAMA0,115200 root=/dev/mmcblk0p2 rw rootwait ssp1=mmc
++noinitrd console=ttyAMA0,115200 root=/dev/mmcblk0p2 rw rootwait ssp1=mmc
+diff -ruN imx-bootlets-10.05.02.orig/linux_prep/core/setup.c
imx-bootlets-10.05.02/linux_prep/core/setup.c
+--- imx-bootlets-10.05.02.orig/linux_prep/core/setup.c 2010-05-14
06:56:28.0 +0200
imx-bootlets-10.05.02/linux_prep/core/setup.c 2012-10-27
01:35:55.0 +0200
+@@ -84,6 +84,8 @@
+ #include ../../mach-mx28/includes/registers/regsrtc.h
+ #elif defined(STMP378X)
+ #include ../../mach-mx23/includes/registers/regsrtc.h
++#elif defined(IMX23_OLINUXINO)
++#include ../../mach-mx23/includes/registers/regsrtc.h
+ #endif
+
+ #define NAND_SECONDARY_BOOT 0x0002
+diff -ruN imx-bootlets-10.05.02.orig/linux_prep/include/mx23/platform.h
imx-bootlets-10.05.02/linux_prep/include/mx23/platform.h
+--- imx-bootlets-10.05.02.orig/linux_prep/include/mx23/platform.h
2010-05-14 06:56:28.0 +0200
imx-bootlets-10.05.02/linux_prep/include/mx23/platform.h 2012-10-27
01:35:55.0 +0200
+@@ -19,6 +19,10 @@
+
+ #if defined (BOARD_STMP378X_DEV)
+ #define MACHINE_ID 0xa45
++
++#elif defined (BOARD_IMX23_OLINUXINO_DEV)
++#define MACHINE_ID 0x1009
++
+ #else
+ #error Allocate a machine ID for your board
+ #endif
+diff -ruN imx-bootlets-10.05.02.orig/linux_prep/Makefile
imx-bootlets-10.05.02/linux_prep/Makefile
+--- imx-bootlets-10.05.02.orig/linux_prep/Makefile
[OpenWrt-Devel] [PATCH 2/2] imx23: Add target for i.MX23
Adding target support for i.MX23, with initial profiles for the different Olinuxino boards. Signed-off-by: Zoltan HERPAI wigy...@uid0.hu --- Index: target/linux/imx23/image/Makefile === --- target/linux/imx23/image/Makefile (revision 0) +++ target/linux/imx23/image/Makefile (revision 0) @@ -0,0 +1,42 @@ +# +# Copyright (C) 2010 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +include $(TOPDIR)/rules.mk +include $(INCLUDE_DIR)/image.mk + +JFFS2_BLOCKSIZE=128k 16k +JFFS2OPTS += -n + +#define Image/BuildKernel +# mkdir -p $(BIN_DIR) +# cp $(KDIR)/vmlinuz $(BIN_DIR)/$(IMG_PREFIX)-zImage +#endef + +#define Image/Prepare +# cp $(LINUX_DIR)/arch/arm/boot/zImage $(KDIR)/vmlinuz +#endef + + +define Image/Build/jffs2-64k + dd if=$(KDIR)/root.jffs2-64k of=$(BIN_DIR)/openwrt-$(BOARD)-jffs2-64k.img bs=65536 conv=sync +endef + +define Image/Build/jffs2-128k + dd if=$(KDIR)/root.jffs2-128k of=$(BIN_DIR)/openwrt-$(BOARD)-jffs2-128k.img bs=131072 conv=sync +endef + +define Image/Build/squashfs + $(call prepare_generic_squashfs,$(KDIR)/root.squashfs) + dd if=$(KDIR)/root.squashfs of=$(BIN_DIR)/openwrt-$(BOARD)-squashfs.img bs=131072 conv=sync +endef + +define Image/Build + $(call Image/Build/$(1)) + dd if=$(KDIR)/root.$(1) of=$(BIN_DIR)/$(IMG_PREFIX)-root.$(1) bs=128k conv=sync +endef + + +$(eval $(call BuildImage)) Index: target/linux/imx23/profiles/003-Micro.mk === --- target/linux/imx23/profiles/003-Micro.mk(revision 0) +++ target/linux/imx23/profiles/003-Micro.mk(revision 0) @@ -0,0 +1,19 @@ +# +# Copyright (C) 2009 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +# FiXME: need to add usb soc + +define Profile/MICRO + NAME:=OLinuXino-MICRO board +# PACKAGES:=kmod-rtl8187 +endef + +define Profile/MICRO/Description + Base packages for -MICRO boards. +endef +$(eval $(call Profile,MICRO)) + Index: target/linux/imx23/profiles/000-Maxi.mk === --- target/linux/imx23/profiles/000-Maxi.mk (revision 0) +++ target/linux/imx23/profiles/000-Maxi.mk (revision 0) @@ -0,0 +1,19 @@ +# +# Copyright (C) 2009 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +# FiXME: need to add usb soc and snd + +define Profile/MAXI + NAME:=OLinuXino-MAXI board + PACKAGES:=kmod-usb-net-smsc95xx +endef + +define Profile/MAXI/Description + Base packages for -MAXI boards. +endef +$(eval $(call Profile,MAXI)) + Index: target/linux/imx23/profiles/002-Mini.mk === --- target/linux/imx23/profiles/002-Mini.mk (revision 0) +++ target/linux/imx23/profiles/002-Mini.mk (revision 0) @@ -0,0 +1,19 @@ +# +# Copyright (C) 2009 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +# FiXME: need to add usb soc and snd + +define Profile/MINI + NAME:=OLinuXino-MINI board + PACKAGES:=kmod-rtl8187 +endef + +define Profile/MINI/Description + Base packages for -MINI boards. +endef +$(eval $(call Profile,MINI)) + Index: target/linux/imx23/profiles/001-Mini-Wifi.mk === --- target/linux/imx23/profiles/001-Mini-Wifi.mk(revision 0) +++ target/linux/imx23/profiles/001-Mini-Wifi.mk(revision 0) @@ -0,0 +1,19 @@ +# +# Copyright (C) 2009 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +# FiXME: need to add usb soc and snd + +define Profile/MINI-WIFI + NAME:=OLinuXino-MINI-WIFI board + PACKAGES:=kmod-rtl8187 +endef + +define Profile/MINI-WIFI/Description + Base packages for -MINI-WIFI boards. +endef +$(eval $(call Profile,MINI-WIFI)) + Index: target/linux/imx23/config-default === --- target/linux/imx23/config-default (revision 0) +++ target/linux/imx23/config-default (revision 0) @@ -0,0 +1,266 @@ +CONFIG_ALIGNMENT_TRAP=y +# CONFIG_AMBA_PL08X is not set +# CONFIG_APM_EMULATION is not set +CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y +CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y +CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y +CONFIG_ARCH_MXS=y +# CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set +CONFIG_ARCH_NR_GPIO=0 +CONFIG_ARCH_REQUIRE_GPIOLIB=y +# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set +# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_ARCH_VT8500_SINGLE is not set +CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y +CONFIG_ARM=y +CONFIG_ARM_AMBA=y
Re: [OpenWrt-Devel] Netifd: Generic multi-wan support
Hi Kristian, at first: thanks for your feedback. I really like the general idea of this patch, however: 1) Instead of using the interface index to decide on interface metric, a table-option is added to interfaces. This way, users are sure which tables will be used for policy routing and can avoid overlaps. The table-option must be set for an interface to be 'multi-wan', and all routes belonging to the interface will be added to this table. This might be acceptable for IPv4 but is not for IPv6. I see the point of the table-attribute and don't object to it. However it must not default to main but to something interface-specific. One of the main points of adding multi-wan IPv6-support was to filter IPv6 traffic by source-address so that it is isn't sent through an interface where the source-address might be rejected by the upstream router or where it simply shouldn't go (e.g. in case of ULA-traffic). 2) Routes are added both to the original table (for example main) and the interface-specific table. This is done to ensure networked applications running on the node will behave as intended. If routes are only added to the interface-specific tables, traffic from applications not binding to an interface will not be routed correctly. Again I doubt this is a good idea and at least for IPv6 this again totally defeats the purpose (e.g. source-filtering, see above). Does a routing policy for each interface table from lo lookup ... (like it was done for IPv6) not cover all locally originating traffic? If it does not, please provide an example where this isn't sufficient. So in the current state: NAK from my side. I could however imagine a compromise here and being in favor for this if we make the following changes to it: * Adding an interface-specific default for the interface_table. * Adding routes to specific tables only (not twice to different tables). * Adding default routing policies for IPv4 so that each table is looked up from every source-address by default for backwards compatibility (also: source-based filtering doesn't make sense for masquerading NAT) * If one wants to restrict traffic (e.g. lan-traffic must only go to wan and not to wan2 or so) he can simply add policy rules through UCI with a higher priority than the default ones (e.g. from lan lookup XYZ + from lan unreachable). Anyway such an intrusive change to IPv4 routing would be needed to be ACKed by more developers. Regards, Steven PS: Also please avoid unrelated changes (interface_write_resolv_conf) or unrelated white-space changes in any follow-up patches. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
