lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 2 Oct 2012 18:02:46 +0200 From: Nicolas Dichtel <nicolas.dichtel@...nd.com> To: joe@...ches.com Cc: bernat@...fy.cx, netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org, davem@...emloft.net Subject: [PATCH net-next v6 0/1] Add support of ECMPv6 Here is a proposal to add the support of ECMPv6. The previous patch from Vincent against iproute2 can be used, but a little other patch is needed too, see http://patchwork.ozlabs.org/patch/183277/ If the kernel patch is approved, I can submit formally the patch for iproute2. Here is an example of a command to add an ECMP route: $ ip -6 route add 3ffe:304:124:2306::/64 \ nexthop via fe80::230:1bff:feb4:e05c dev eth0 \ nexthop via fe80::230:1bff:feb4:dd4f dev eth0 But note that this command is a shortcut and previous patches are not mandatory to set ECMP routes. The following commands can be used too: $ ip -6 route add 3ffe:304:124:2306::/64 via fe80::230:1bff:feb4:dd4f dev eth0 $ ip -6 route append 3ffe:304:124:2306::/64 via fe80::230:1bff:feb4:e05c dev eth0 Here is an example of a dump: $ ip -6 route | grep 3ffe:304:124:2306::/64 3ffe:304:124:2306::/64 via fe80::230:1bff:feb4:dd4f dev eth0 metric 1024 3ffe:304:124:2306::/64 via fe80::230:1bff:feb4:e05c dev eth0 metric 1024 v6: be more verbose in commitlog add some helpers in ip6_fib.h to avoid to have too many ifdef block in the code invert fc_mp_len and fc_mp in struct fib6_config to avoid a hole on 64bits arch v5: to minimize the patch and ease its integration, remove roundrobin and random algorithms for route selection. It will be possible to add new algorithms through rt6_info_hashfn() when the basic support of ECMP is integrated. v4: remove compilation options to choose multipath algorithm for next hop selection. Now the choice can be done at run time via /proc/sys/net/ipv6/route/multipath_algorithm v3: rebase after updating net-next v2: rename CONFIG_IPV6_MULTIPATH_ROUTE to CONFIG_IPV6_MULTIPATH_HASH use flowlabel in the hash function add reference to RFC fix a small identation issue remove "If unsure, say N." from the help of CONFIG_IPV6_MULTIPATH Comments are welcome. Regards, Nicolas -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists