···866extern int xfrm_init_state(struct xfrm_state *x);867extern int xfrm4_rcv(struct sk_buff *skb);868extern int xfrm4_output(struct sk_buff *skb);869-extern int xfrm4_output_finish(struct sk_buff *skb);870extern int xfrm4_tunnel_register(struct xfrm_tunnel *handler);871extern int xfrm4_tunnel_deregister(struct xfrm_tunnel *handler);872extern int xfrm6_rcv_spi(struct sk_buff **pskb, u32 spi);
···866extern int xfrm_init_state(struct xfrm_state *x);867extern int xfrm4_rcv(struct sk_buff *skb);868extern int xfrm4_output(struct sk_buff *skb);0869extern int xfrm4_tunnel_register(struct xfrm_tunnel *handler);870extern int xfrm4_tunnel_deregister(struct xfrm_tunnel *handler);871extern int xfrm6_rcv_spi(struct sk_buff **pskb, u32 spi);
···126 tristate '"CONNMARK" target support'127 depends on NETFILTER_XTABLES128 depends on IP_NF_MANGLE || IP6_NF_MANGLE129- depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK_IPV4)130 help131 This option adds a `CONNMARK' target, which allows one to manipulate132 the connection mark value. Similar to the MARK target, but···187config NETFILTER_XT_MATCH_CONNBYTES188 tristate '"connbytes" per-connection counter match support'189 depends on NETFILTER_XTABLES190- depends on (IP_NF_CONNTRACK && IP_NF_CT_ACCT) || NF_CT_ACCT191 help192 This option adds a `connbytes' match, which allows you to match the193 number of bytes and/or packets for each direction within a connection.···198config NETFILTER_XT_MATCH_CONNMARK199 tristate '"connmark" connection mark match support'200 depends on NETFILTER_XTABLES201- depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || NF_CONNTRACK_MARK202 help203 This option adds a `connmark' match, which allows you to match the204 connection mark value previously set for the session by `CONNMARK'.
···126 tristate '"CONNMARK" target support'127 depends on NETFILTER_XTABLES128 depends on IP_NF_MANGLE || IP6_NF_MANGLE129+ depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK)130 help131 This option adds a `CONNMARK' target, which allows one to manipulate132 the connection mark value. Similar to the MARK target, but···187config NETFILTER_XT_MATCH_CONNBYTES188 tristate '"connbytes" per-connection counter match support'189 depends on NETFILTER_XTABLES190+ depends on (IP_NF_CONNTRACK && IP_NF_CT_ACCT) || (NF_CT_ACCT && NF_CONNTRACK)191 help192 This option adds a `connbytes' match, which allows you to match the193 number of bytes and/or packets for each direction within a connection.···198config NETFILTER_XT_MATCH_CONNMARK199 tristate '"connmark" connection mark match support'200 depends on NETFILTER_XTABLES201+ depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK)202 help203 This option adds a `connmark' match, which allows you to match the204 connection mark value previously set for the session by `CONNMARK'.
+5
net/netfilter/nf_conntrack_core.c
···1556{1557 int i;1558001559 /* This makes sure all current packets have passed through1560 netfilter framework. Roll on, two-stage module1561 delete... */···1716 for (i = 0; i < PF_MAX; i++)1717 nf_ct_l3protos[i] = &nf_conntrack_generic_l3proto;1718 write_unlock_bh(&nf_conntrack_lock);00017191720 /* Set up fake conntrack:1721 - to never be deleted, not in any hashes */
···1556{1557 int i;15581559+ ip_ct_attach = NULL;1560+1561 /* This makes sure all current packets have passed through1562 netfilter framework. Roll on, two-stage module1563 delete... */···1714 for (i = 0; i < PF_MAX; i++)1715 nf_ct_l3protos[i] = &nf_conntrack_generic_l3proto;1716 write_unlock_bh(&nf_conntrack_lock);1717+1718+ /* For use by REJECT target */1719+ ip_ct_attach = __nf_conntrack_attach;17201721 /* Set up fake conntrack:1722 - to never be deleted, not in any hashes */