2008-01-10 03:49:06 -07:00
|
|
|
/*
|
|
|
|
|
* ipv6 in net namespaces
|
|
|
|
|
*/
|
|
|
|
|
|
2008-01-10 03:56:03 -07:00
|
|
|
#include <net/inet_frag.h>
|
|
|
|
|
|
2008-01-10 03:49:06 -07:00
|
|
|
#ifndef __NETNS_IPV6_H__
|
|
|
|
|
#define __NETNS_IPV6_H__
|
2009-08-28 19:34:49 -06:00
|
|
|
#include <net/dst_ops.h>
|
2008-01-10 03:49:06 -07:00
|
|
|
|
2008-01-10 03:53:43 -07:00
|
|
|
struct ctl_table_header;
|
|
|
|
|
|
|
|
|
|
struct netns_sysctl_ipv6 {
|
|
|
|
|
#ifdef CONFIG_SYSCTL
|
2012-04-19 07:37:09 -06:00
|
|
|
struct ctl_table_header *hdr;
|
|
|
|
|
struct ctl_table_header *route_hdr;
|
|
|
|
|
struct ctl_table_header *icmp_hdr;
|
2008-01-22 07:08:36 -07:00
|
|
|
struct ctl_table_header *frags_hdr;
|
2013-02-06 02:46:33 -07:00
|
|
|
struct ctl_table_header *xfrm6_hdr;
|
2008-01-10 03:53:43 -07:00
|
|
|
#endif
|
2008-01-10 03:54:53 -07:00
|
|
|
int bindv6only;
|
2008-01-10 04:01:01 -07:00
|
|
|
int flush_delay;
|
|
|
|
|
int ip6_rt_max_size;
|
|
|
|
|
int ip6_rt_gc_min_interval;
|
|
|
|
|
int ip6_rt_gc_timeout;
|
|
|
|
|
int ip6_rt_gc_interval;
|
|
|
|
|
int ip6_rt_gc_elasticity;
|
|
|
|
|
int ip6_rt_mtu_expires;
|
|
|
|
|
int ip6_rt_min_advmss;
|
2014-01-17 09:15:05 -07:00
|
|
|
int flowlabel_consistency;
|
2014-07-01 22:33:10 -06:00
|
|
|
int auto_flowlabels;
|
2008-01-10 04:02:40 -07:00
|
|
|
int icmpv6_time;
|
2014-01-13 07:59:01 -07:00
|
|
|
int anycast_src_echo_reply;
|
2015-07-08 17:58:22 -06:00
|
|
|
int ip_nonlocal_bind;
|
2014-05-13 11:17:33 -06:00
|
|
|
int fwmark_reflect;
|
2015-03-23 16:36:05 -06:00
|
|
|
int idgen_retries;
|
|
|
|
|
int idgen_delay;
|
ipv6: Flow label state ranges
This patch divides the IPv6 flow label space into two ranges:
0-7ffff is reserved for flow label manager, 80000-fffff will be
used for creating auto flow labels (per RFC6438). This only affects how
labels are set on transmit, it does not affect receive. This range split
can be disbaled by systcl.
Background:
IPv6 flow labels have been an unmitigated disappointment thus far
in the lifetime of IPv6. Support in HW devices to use them for ECMP
is lacking, and OSes don't turn them on by default. If we had these
we could get much better hashing in IPv6 networks without resorting
to DPI, possibly eliminating some of the motivations to to define new
encaps in UDP just for getting ECMP.
Unfortunately, the initial specfications of IPv6 did not clarify
how they are to be used. There has always been a vague concept that
these can be used for ECMP, flow hashing, etc. and we do now have a
good standard how to this in RFC6438. The problem is that flow labels
can be either stateful or stateless (as in RFC6438), and we are
presented with the possibility that a stateless label may collide
with a stateful one. Attempts to split the flow label space were
rejected in IETF. When we added support in Linux for RFC6438, we
could not turn on flow labels by default due to this conflict.
This patch splits the flow label space and should give us
a path to enabling auto flow labels by default for all IPv6 packets.
This is an API change so we need to consider compatibility with
existing deployment. The stateful range is chosen to be the lower
values in hopes that most uses would have chosen small numbers.
Once we resolve the stateless/stateful issue, we can proceed to
look at enabling RFC6438 flow labels by default (starting with
scaled testing).
Signed-off-by: Tom Herbert <tom@herbertland.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2015-04-29 16:33:21 -06:00
|
|
|
int flowlabel_state_ranges;
|
2008-01-10 03:53:43 -07:00
|
|
|
};
|
|
|
|
|
|
2008-01-10 03:49:06 -07:00
|
|
|
struct netns_ipv6 {
|
2008-01-10 03:53:43 -07:00
|
|
|
struct netns_sysctl_ipv6 sysctl;
|
2008-01-10 18:42:55 -07:00
|
|
|
struct ipv6_devconf *devconf_all;
|
|
|
|
|
struct ipv6_devconf *devconf_dflt;
|
2012-06-07 19:20:41 -06:00
|
|
|
struct inet_peer_base *peers;
|
2008-01-22 07:02:14 -07:00
|
|
|
struct netns_frags frags;
|
2008-01-31 05:04:13 -07:00
|
|
|
#ifdef CONFIG_NETFILTER
|
|
|
|
|
struct xt_table *ip6table_filter;
|
|
|
|
|
struct xt_table *ip6table_mangle;
|
|
|
|
|
struct xt_table *ip6table_raw;
|
2010-01-18 00:08:37 -07:00
|
|
|
#ifdef CONFIG_SECURITY
|
2008-06-09 16:58:05 -06:00
|
|
|
struct xt_table *ip6table_security;
|
2010-01-18 00:08:37 -07:00
|
|
|
#endif
|
2012-08-26 11:14:12 -06:00
|
|
|
struct xt_table *ip6table_nat;
|
2008-03-04 00:25:27 -07:00
|
|
|
#endif
|
2008-03-04 14:48:30 -07:00
|
|
|
struct rt6_info *ip6_null_entry;
|
2008-03-04 00:34:17 -07:00
|
|
|
struct rt6_statistics *rt6_stats;
|
2008-07-22 15:33:45 -06:00
|
|
|
struct timer_list ip6_fib_timer;
|
2008-03-04 00:25:27 -07:00
|
|
|
struct hlist_head *fib_table_hash;
|
|
|
|
|
struct fib6_table *fib6_main_tbl;
|
2016-03-08 06:44:35 -07:00
|
|
|
struct list_head fib6_walkers;
|
2009-08-28 19:34:49 -06:00
|
|
|
struct dst_ops ip6_dst_ops;
|
2016-03-08 06:44:35 -07:00
|
|
|
rwlock_t fib6_walker_lock;
|
2016-03-08 06:44:45 -07:00
|
|
|
spinlock_t fib6_gc_lock;
|
2008-03-04 14:49:47 -07:00
|
|
|
unsigned int ip6_rt_gc_expire;
|
|
|
|
|
unsigned long ip6_rt_last_gc;
|
2008-03-04 00:25:27 -07:00
|
|
|
#ifdef CONFIG_IPV6_MULTIPLE_TABLES
|
2017-08-08 12:23:49 -06:00
|
|
|
bool fib6_has_custom_rules;
|
2008-03-04 14:48:30 -07:00
|
|
|
struct rt6_info *ip6_prohibit_entry;
|
|
|
|
|
struct rt6_info *ip6_blk_hole_entry;
|
2008-03-04 00:25:27 -07:00
|
|
|
struct fib6_table *fib6_local_tbl;
|
2008-03-04 00:33:08 -07:00
|
|
|
struct fib_rules_ops *fib6_rules_ops;
|
2008-01-31 05:04:13 -07:00
|
|
|
#endif
|
2008-02-29 12:21:22 -07:00
|
|
|
struct sock **icmp_sk;
|
2008-03-07 12:15:34 -07:00
|
|
|
struct sock *ndisc_sk;
|
2008-03-07 12:16:02 -07:00
|
|
|
struct sock *tcp_sk;
|
2008-03-07 12:16:55 -07:00
|
|
|
struct sock *igmp_sk;
|
2015-02-25 10:58:35 -07:00
|
|
|
struct sock *mc_autojoin_sk;
|
2008-12-10 17:07:08 -07:00
|
|
|
#ifdef CONFIG_IPV6_MROUTE
|
ipv6: ip6mr: support multiple tables
This patch adds support for multiple independant multicast routing instances,
named "tables".
Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT6_TABLE. The table number is
stored in the raw socket data and affects all following ip6mr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT6_TABLE_DFLT)
is created with a default routing rule pointing to it. Newly created pim6reg
devices have the table number appended ("pim6regX"), with the exception of
devices created in the default table, which are named just "pim6reg" for
compatibility reasons.
Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.
Example usage:
- bind pimd/xorp/... to a specific table:
uint32_t table = 123;
setsockopt(fd, SOL_IPV6, MRT6_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip -6 mrule add iif eth0 lookup 123
# ip -6 mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
2010-05-11 06:40:55 -06:00
|
|
|
#ifndef CONFIG_IPV6_MROUTE_MULTIPLE_TABLES
|
2010-05-11 06:40:53 -06:00
|
|
|
struct mr6_table *mrt6;
|
ipv6: ip6mr: support multiple tables
This patch adds support for multiple independant multicast routing instances,
named "tables".
Userspace multicast routing daemons can bind to a specific table instance by
issuing a setsockopt call using a new option MRT6_TABLE. The table number is
stored in the raw socket data and affects all following ip6mr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT6_TABLE_DFLT)
is created with a default routing rule pointing to it. Newly created pim6reg
devices have the table number appended ("pim6regX"), with the exception of
devices created in the default table, which are named just "pim6reg" for
compatibility reasons.
Packets are directed to a specific table instance using routing rules,
similar to how regular routing rules work. Currently iif, oif and mark
are supported as keys, source and destination addresses could be supported
additionally.
Example usage:
- bind pimd/xorp/... to a specific table:
uint32_t table = 123;
setsockopt(fd, SOL_IPV6, MRT6_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip -6 mrule add iif eth0 lookup 123
# ip -6 mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
2010-05-11 06:40:55 -06:00
|
|
|
#else
|
|
|
|
|
struct list_head mr6_tables;
|
|
|
|
|
struct fib_rules_ops *mr6_rules_ops;
|
|
|
|
|
#endif
|
2008-12-10 17:07:08 -07:00
|
|
|
#endif
|
2013-03-22 00:28:43 -06:00
|
|
|
atomic_t dev_addr_genid;
|
2014-10-06 11:58:37 -06:00
|
|
|
atomic_t fib6_sernum;
|
2016-11-08 06:57:40 -07:00
|
|
|
struct seg6_pernet_data *seg6_data;
|
2017-08-03 05:28:16 -06:00
|
|
|
struct fib_notifier_ops *notifier_ops;
|
2008-01-10 03:49:06 -07:00
|
|
|
};
|
2012-09-18 10:50:08 -06:00
|
|
|
|
|
|
|
|
#if IS_ENABLED(CONFIG_NF_DEFRAG_IPV6)
|
|
|
|
|
struct netns_nf_frag {
|
|
|
|
|
struct netns_sysctl_ipv6 sysctl;
|
|
|
|
|
struct netns_frags frags;
|
|
|
|
|
};
|
|
|
|
|
#endif
|
|
|
|
|
|
2008-01-10 03:49:06 -07:00
|
|
|
#endif
|