2007-12-16 13:29:36 -08:00
/*
* ipv4 in net namespaces
*/
# ifndef __NETNS_IPV4_H__
# define __NETNS_IPV4_H__
2008-01-10 03:27:51 -08:00
2008-01-22 06:02:14 -08:00
# include <net/inet_frag.h>
2007-12-16 13:31:47 -08:00
struct ctl_table_header ;
struct ipv4_devconf ;
2008-01-10 03:27:51 -08:00
struct fib_rules_ops ;
2008-01-10 03:28:24 -08:00
struct hlist_head ;
2008-01-10 03:28:55 -08:00
struct sock ;
2007-12-16 13:31:47 -08:00
2007-12-16 13:29:36 -08:00
struct netns_ipv4 {
2008-01-05 23:08:49 -08:00
# ifdef CONFIG_SYSCTL
2007-12-16 13:31:47 -08:00
struct ctl_table_header * forw_hdr ;
2008-01-22 06:08:36 -08:00
struct ctl_table_header * frags_hdr ;
2008-03-26 01:56:24 -07:00
struct ctl_table_header * ipv4_hdr ;
2008-07-05 19:02:33 -07:00
struct ctl_table_header * route_hdr ;
2008-01-05 23:08:49 -08:00
# endif
2007-12-16 13:31:47 -08:00
struct ipv4_devconf * devconf_all ;
struct ipv4_devconf * devconf_dflt ;
2008-01-10 03:27:51 -08:00
# ifdef CONFIG_IP_MULTIPLE_TABLES
struct fib_rules_ops * rules_ops ;
# endif
2008-01-10 03:28:24 -08:00
struct hlist_head * fib_table_hash ;
2008-01-10 03:28:55 -08:00
struct sock * fibnl ;
2008-01-22 06:02:14 -08:00
2008-02-29 11:19:58 -08:00
struct sock * * icmp_sk ;
2008-04-03 14:31:33 -07:00
struct sock * tcp_sock ;
2008-02-29 11:19:58 -08:00
2008-01-22 06:02:14 -08:00
struct netns_frags frags ;
2008-01-31 04:03:23 -08:00
# ifdef CONFIG_NETFILTER
struct xt_table * iptable_filter ;
struct xt_table * iptable_mangle ;
struct xt_table * iptable_raw ;
2008-01-31 04:05:09 -08:00
struct xt_table * arptable_filter ;
2010-01-18 08:08:37 +01:00
# ifdef CONFIG_SECURITY
2008-06-09 15:57:24 -07:00
struct xt_table * iptable_security ;
2010-01-18 08:08:37 +01:00
# endif
2008-10-08 11:35:10 +02:00
struct xt_table * nat_table ;
2008-10-08 11:35:11 +02:00
struct hlist_head * nat_bysource ;
2010-02-08 11:18:07 -08:00
unsigned int nat_htable_size ;
2008-01-31 04:03:23 -08:00
# endif
2008-03-26 01:55:37 -07:00
int sysctl_icmp_echo_ignore_all ;
int sysctl_icmp_echo_ignore_broadcasts ;
int sysctl_icmp_ignore_bogus_error_responses ;
int sysctl_icmp_ratelimit ;
int sysctl_icmp_ratemask ;
int sysctl_icmp_errors_use_inbound_ifaddr ;
2008-10-27 12:28:25 -07:00
int sysctl_rt_cache_rebuild_count ;
int current_rt_cache_rebuild_count ;
2008-07-05 19:02:59 -07:00
2008-07-05 19:04:32 -07:00
atomic_t rt_genid ;
2011-03-24 17:42:21 -07:00
atomic_t dev_addr_genid ;
2009-01-22 04:56:15 +00:00
# ifdef CONFIG_IP_MROUTE
ipv4: ipmr: 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 MRT_TABLE. The table number is
stored in the raw socket data and affects all following ipmr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT_TABLE_DEFAULT)
is created with a default routing rule pointing to it. Newly created pimreg
devices have the table number appended ("pimregX"), with the exception of
devices created in the default table, which are named just "pimreg" 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, IPPROTO_IP, MRT_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip mrule add iif eth0 lookup 123
# ip mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2010-04-13 05:03:23 +00:00
# ifndef CONFIG_IP_MROUTE_MULTIPLE_TABLES
2010-04-13 05:03:22 +00:00
struct mr_table * mrt ;
ipv4: ipmr: 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 MRT_TABLE. The table number is
stored in the raw socket data and affects all following ipmr setsockopt(),
getsockopt() and ioctl() calls. By default, a single table (RT_TABLE_DEFAULT)
is created with a default routing rule pointing to it. Newly created pimreg
devices have the table number appended ("pimregX"), with the exception of
devices created in the default table, which are named just "pimreg" 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, IPPROTO_IP, MRT_TABLE, &table, sizeof(table));
- create routing rules directing packets to the new table:
# ip mrule add iif eth0 lookup 123
# ip mrule add oif eth0 lookup 123
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
2010-04-13 05:03:23 +00:00
# else
struct list_head mr_tables ;
struct fib_rules_ops * mr_rules_ops ;
# endif
2009-01-22 04:56:15 +00:00
# endif
2007-12-16 13:29:36 -08:00
} ;
# endif
