<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://gentoo-zh.org/extern.php?action=feed&amp;tid=10&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Gentoo中文社区 / Networking support]]></title>
		<link>http://www.gentoo-zh.org/viewtopic.php?id=10</link>
		<description><![CDATA[Networking support 最近发表的帖子。]]></description>
		<lastBuildDate>Wed, 03 Aug 2022 14:32:40 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Networking support]]></title>
			<link>http://www.gentoo-zh.org/viewtopic.php?pid=10#p10</link>
			<description><![CDATA[<p>Networking support<br />网络支持</p><p>Networking options<br />&#160; &#160; 网络选项<br />&#160; &#160; Packet socket<br />&#160; &#160; CONFIG_PACKET<br />&#160; &#160; &#160; &#160; 链路层PF_PACKET套接字支持.可以让应用程序(比如:抓包工具tcpdump,<br />&#160; &#160; &#160; &#160; DHCP客户端dhclient)直接与网络设备通讯,而无需使用内核中的其它中介协议.不确定的选&quot;Y&quot;或&quot;M&quot;.<br />&#160; &#160; &#160; &#160; Packet: sockets monitoring interface<br />&#160; &#160; &#160; &#160; CONFIG_PACKET_DIAG<br />&#160; &#160; &#160; &#160; &#160; &#160; PF_PACKET套接字监控接口,ss这样的诊断工具需要它.<br />&#160; &#160; Unix domain sockets<br />&#160; &#160; CONFIG_UNIX<br />&#160; &#160; &#160; &#160; Unix domain sockets 支持.许多程序都使用它在操作系统内部进行进程间通信(IPC),<br />&#160; &#160; &#160; &#160; 比如: X Window, syslog, udev 等等.选&quot;Y&quot;,除非你确实知道自己在做什么.<br />&#160; &#160; &#160; &#160; UNIX: socket monitoring interface<br />&#160; &#160; &#160; &#160; CONFIG_UNIX_DIAG<br />&#160; &#160; &#160; &#160; &#160; &#160; UNIX套接字监控接口,ss这样的工具需要它.<br />&#160; &#160; Transport Layer Security support<br />&#160; &#160; &#160; &#160; 传输层安全支持<br />&#160; &#160; Transformation user configuration interface<br />&#160; &#160; CONFIG_XFRM_USER<br />&#160; &#160; &#160; &#160; 为IPsec相关的工具提供Transformation(XFRM)用户配置接口<br />&#160; &#160; Transformation sub policy support<br />&#160; &#160; CONFIG_XFRM_SUB_POLICY<br />&#160; &#160; &#160; &#160; XFRM子策略支持,不确定的选&quot;N&quot;.<br />&#160; &#160; Transformation migrate database<br />&#160; &#160; CONFIG_XFRM_MIGRATE<br />&#160; &#160; &#160; &#160; 用于动态的更新 IPsec SA(security association) 的定位器(locator).<br />&#160; &#160; &#160; &#160; 这个特性对于手机这类移动设备来讲至关重要,<br />&#160; &#160; &#160; &#160; 因为它需要在不同的基站之间迁移.不确定的选&quot;N&quot;.<br />&#160; &#160; Transformation statistics<br />&#160; &#160; CONFIG_XFRM_STATISTICS<br />&#160; &#160; &#160; &#160; 转换统计,这不是SNMP/MIB规范的内容.用于调试目的.不确定的选&quot;N&quot;.<br />&#160; &#160; PF_KEY sockets<br />&#160; &#160; CONFIG_NET_KEY<br />&#160; &#160; &#160; &#160; PF_KEYv2 套接字支持(与KAME兼容).PF_KEY协议族主要用来处理SA(安全关联),<br />&#160; &#160; &#160; &#160; 对SADB(SA数据库)进行管理,主要用在IPsec协议中.PF_KEY_v2的编程API在RFC2367中定义.<br />&#160; &#160; &#160; &#160; PF_KEY MIGRATE<br />&#160; &#160; &#160; &#160; CONFIG_NET_KEY_MIGRATE<br />&#160; &#160; &#160; &#160; &#160; &#160; 向PF_KEYv2套接字中添加一个 PF_KEY MIGRATE 消息. 、<br />&#160; &#160; &#160; &#160; &#160; &#160; PF_KEY MIGRATE 消息可用于动态的更新 IPsec SA(security association) 的定位器(locator).<br />&#160; &#160; &#160; &#160; &#160; &#160; 这个特性对于手机这类移动设备来讲至关重要,因为它需要在不同的基站之间迁移.不确定的选&quot;N&quot;.<br />&#160; &#160; SMC socket protocol family<br />&#160; &#160; &#160; &#160; SMC套接字协议族<br />&#160; &#160; TCP/IP networking<br />&#160; &#160; CONFIG_INET<br />&#160; &#160; &#160; &#160; TCP/IP协议,必选!<br />&#160; &#160; &#160; &#160; IP: multicasting<br />&#160; &#160; &#160; &#160; CONFIG_IP_MULTICAST<br />&#160; &#160; &#160; &#160; &#160; &#160; IP组播(IP multicasting)支持.指的是一个发送者向一组特定的接收者发送数据,<br />&#160; &#160; &#160; &#160; &#160; &#160; 但只需发送一份数据副本.实际应用的场合很少,MBONE算是其中之一,<br />&#160; &#160; &#160; &#160; &#160; &#160; 与RTP等音视频协议相结合也算一种.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; IP: advanced router<br />&#160; &#160; &#160; &#160; CONFIG_IP_ADVANCED_ROUTER<br />&#160; &#160; &#160; &#160; &#160; &#160; 高级路由支持,需要开启内核的IP转发功能(echo 1 &gt; /proc/sys/net/ipv4/ip_forward)才能正常工作.<br />&#160; &#160; &#160; &#160; &#160; &#160; 如果这个Linux系统用作专业的路由器就选上,选上之后还需要按需选择其下的子项.一般的主机不需要这个.<br />&#160; &#160; &#160; &#160; &#160; &#160; FIB TRIE statistics<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_FIB_TRIE_STATS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 主要用于测试TRIE性能<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: policy routing<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_MULTIPLE_TABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 策略路由<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: equal cost multipath<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_ROUTE_MULTIPATH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于基于目的地址的负载均衡<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: verbose route monitoring<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_ROUTE_VERBOSE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 显示冗余的路由监控信息<br />&#160; &#160; &#160; &#160; IP: kernel level autoconfiguration<br />&#160; &#160; &#160; &#160; CONFIG_IP_PNP<br />&#160; &#160; &#160; &#160; &#160; &#160; 在内核启动时自动配置网卡的ip地址/路由表,配置信息来自于以下途径:内核引导参数,<br />&#160; &#160; &#160; &#160; &#160; &#160; 自举协议(BOOTP),反向地址转换协议(RARP),动态主机配置协议(DHCP).通常,<br />&#160; &#160; &#160; &#160; &#160; &#160; 需要从网络启动的无盘工作站才需要这个东西(此时还需要开启CONFIG_ROOT_NFS),<br />&#160; &#160; &#160; &#160; &#160; &#160; 一般的发行版都通过启动脚本(dhcpcd/dhclient/ifconfig)配置网络.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: DHCP support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_PNP_DHCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; DHCP协议支持<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: BOOTP support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_PNP_BOOTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; BOOTP协议支持<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: RARP support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_PNP_RARP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; RARP协议支持<br />&#160; &#160; &#160; &#160; IP: tunneling<br />&#160; &#160; &#160; &#160; CONFIG_NET_IPIP<br />&#160; &#160; &#160; &#160; &#160; &#160; IP隧道,主要目的是为了在TCP/IP网络中传输其他协议的数据包,当然也包括IP数据包(例如用于实现VPN).<br />&#160; &#160; &#160; &#160; IP: GRE demultiplexer<br />&#160; &#160; &#160; &#160; CONFIG_NET_IPGRE_DEMUX<br />&#160; &#160; &#160; &#160; &#160; &#160; GRE demultiplexer 支持.被CONFIG_NET_IPGRE和CONFIG_PPTP所依赖.<br />&#160; &#160; &#160; &#160; IP: GRE tunnels over IP<br />&#160; &#160; &#160; &#160; CONFIG_NET_IPGRE<br />&#160; &#160; &#160; &#160; &#160; &#160; 基于IP的通用路由封装(Generic Routing Encapsulation)隧道支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; 该驱动主要用于对端是Cisco路由器的场合,因为Cisco的路由器特别偏好GRE隧道<br />&#160; &#160; &#160; &#160; &#160; &#160; (而不是CONFIG_NET_IPIP),并且GRE还允许通过隧道对组播进行再分发.<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: broadcast GRE over IP<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NET_IPGRE_BROADCAST<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; GRE/IP的一种应用是构建一个广播WAN(Wide Area Network),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 而其看上去却很像一个跑在互联网上的LAN(Local Area Network).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 如果你想要创建这样的网络,那么就选&quot;Y&quot;(还要加上CONFIG_IP_MROUTE).<br />&#160; &#160; &#160; &#160; IP: multicast routing<br />&#160; &#160; &#160; &#160; CONFIG_IP_MROUTE<br />&#160; &#160; &#160; &#160; &#160; &#160; 组播路由支持.实际应用的场合很少,MBONE算是其中之一,不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: multicast policy routing<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_MROUTE_MULTIPLE_TABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通常,组播路由器上会运行一个单独的用户态守护进程,根据源地址和目的地址来处理数据包.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 开启此项后,将能同时考虑数据包所带的标记(mark)和所通过的网络接口,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并可在用户空间同时运行多个守护进程,每一个进程处理一张路由表.<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: PIM-SM version 1 support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_PIMSM_V1<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Sparse Mode PIM (Protocol Independent Multicast) version 1 支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;该协议被Cisco路由器广泛支持,你需要特定的软件(pimd-v1)才能使用它.<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: PIM-SM version 2 support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_PIMSM_V2<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Sparse Mode PIM (Protocol Independent Multicast) version 2 支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;该协议的使用并不广泛,你需要特定的软件(pimd 或 gated-5)才能使用它.<br />&#160; &#160; &#160; &#160; IP: ARP daemon support<br />&#160; &#160; &#160; &#160; CONFIG_ARPD<br />&#160; &#160; &#160; &#160; &#160; &#160; 通常情况下,内核自身会使用ARP协议解析本地网络中的IP地址与MAC地址的对应关系,<br />&#160; &#160; &#160; &#160; &#160; &#160; 并进行缓存.开启此项后,内核将使用用户空间的守护进程进行ARP解析.<br />&#160; &#160; &#160; &#160; &#160; &#160; 这主要是为了使用其他的替代解析协议(比如mGRE隧道中的NHRP),或调试目的.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; IP: TCP syncookie support<br />&#160; &#160; &#160; &#160; CONFIG_SYN_COOKIES<br />&#160; &#160; &#160; &#160; &#160; &#160; TCP syncookie 支持,这是抵抗SYN flood攻击的好东西.此特性的开关可以通过<br />&#160; &#160; &#160; &#160; &#160; &#160; &quot;/proc/sys/net/ipv4/tcp_syncookies&quot;文件控制,写入&quot;1&quot;表示开启,写入&quot;0&quot;表示关闭.<br />&#160; &#160; &#160; &#160; &#160; &#160; 建议服务器环境开启此项.<br />&#160; &#160; &#160; &#160; Virtual (secure) IP: tunneling<br />&#160; &#160; &#160; &#160; CONFIG_NET_IPVTI<br />&#160; &#160; &#160; &#160; &#160; &#160; 虚拟IP隧道.可以和xfrm隧道一起使用,以实现IPSEC安全隧道,并在其上使用路由协议.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; IP: Foo (IP protocols) over UDP<br />&#160; &#160; &#160; &#160; &#160; &#160; IP：Foo（IP协议）通过UDP<br />&#160; &#160; &#160; &#160; IP: FOU encapsulation of IP tunnels<br />&#160; &#160; &#160; &#160; &#160; &#160; IP：IP隧道的FOU封装<br />&#160; &#160; &#160; &#160; IP: AH transformation<br />&#160; &#160; &#160; &#160; CONFIG_INET_AH<br />&#160; &#160; &#160; &#160; &#160; &#160; IPsec AH 支持.IPsec验证头(AH)可对整个数据包(IP报头与数据)提供身份验证/完整性/抗重播保护.<br />&#160; &#160; &#160; &#160; &#160; &#160; 但是它不提供保密性,即它不对数据进行加密.由于这个原因,AH头正在慢慢被ESP头取代.<br />&#160; &#160; &#160; &#160; IP: ESP transformation<br />&#160; &#160; &#160; &#160; CONFIG_INET_ESP<br />&#160; &#160; &#160; &#160; &#160; &#160; IPsec ESP 支持.IPsec封装安全负载(ESP)不仅为IP负载提供身份验证/完整性/抗重播保护,还提供保密性,<br />&#160; &#160; &#160; &#160; &#160; &#160; 也就是还对数据进行加密.ESP有两种使用模式:传输模式(ESP不对整个数据包进行签名,<br />&#160; &#160; &#160; &#160; &#160; &#160; 只对IP负载(不含IP报头)进行保护)和隧道模式(将原始IP包封装进新的带有ESP头的IP包内,<br />&#160; &#160; &#160; &#160; &#160; &#160; 可提供完整的保护).ESP可以独立使用,也可与AH组合使用(越来越少).<br />&#160; &#160; &#160; &#160; &#160; &#160; IP: ESP transformation offload<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IP：ESP转换卸载<br />&#160; &#160; &#160; &#160; IP: IPComp transformation<br />&#160; &#160; &#160; &#160; CONFIG_INET_IPCOMP<br />&#160; &#160; &#160; &#160; &#160; &#160; IP静荷载压缩协议(IP Payload Compression Protocol)(RFC3173)支持.用于支持IPsec<br />&#160; &#160; &#160; &#160; IP: IPsec transport mode<br />&#160; &#160; &#160; &#160; CONFIG_INET_XFRM_MODE_TRANSPORT<br />&#160; &#160; &#160; &#160; &#160; &#160; IPsec传输模式.常用于对等通信,用以提供内网安全.数据包经过了加密但IP头没有加密,<br />&#160; &#160; &#160; &#160; &#160; &#160; 因此任何标准设备或软件都可查看和使用IP头<br />&#160; &#160; &#160; &#160; IP: IPsec tunnel mode<br />&#160; &#160; &#160; &#160; CONFIG_INET_XFRM_MODE_TUNNEL<br />&#160; &#160; &#160; &#160; &#160; &#160; IPsec隧道模式.用于提供外网安全(包括虚拟专用网络).整个数据包(数据头和负载)<br />&#160; &#160; &#160; &#160; &#160; &#160; 都已经过加密处理且分配有新的ESP头/IP头/验证尾,从而能够隐藏受保护站点的拓扑结构<br />&#160; &#160; &#160; &#160; IP: IPsec BEET mode<br />&#160; &#160; &#160; &#160; CONFIG_INET_XFRM_MODE_BEET<br />&#160; &#160; &#160; &#160; &#160; &#160; IPsec BEET模式.<br />&#160; &#160; &#160; &#160; Large Receive Offload (ipv4/tcp)<br />&#160; &#160; &#160; &#160; CONFIG_INET_LRO<br />&#160; &#160; &#160; &#160; &#160; &#160; LRO(Large Receive Offload) (ipv4/tcp) 支持.它通过将多个TCP数据整合在一个skb结构中,<br />&#160; &#160; &#160; &#160; &#160; &#160; 并在稍后的某个时刻作为一个大的数据包交付给上层的网络协议栈,<br />&#160; &#160; &#160; &#160; &#160; &#160; 以减少上层协议栈处理skb的开销,提高Linux系统接收TCP数据包的能力.<br />&#160; &#160; &#160; &#160; &#160; &#160; 目前,主流网卡驱动都已支持此特性.建议开启.不过,LRO不应该在路由器上开启,<br />&#160; &#160; &#160; &#160; &#160; &#160; 因为它破坏了end-to-end原则,并会对路由性能造成显著的不利影响.<br />&#160; &#160; &#160; &#160; INET: socket monitoring interface<br />&#160; &#160; &#160; &#160; CONFIG_INET_DIAG<br />&#160; &#160; &#160; &#160; &#160; &#160; INET(TCP,DCCP,...) socket 监视接口,一些Linux本地工具(如:包含ss的iproute2)需要使用它<br />&#160; &#160; &#160; &#160; &#160; &#160; UDP: socket monitoring interface<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET_UDP_DIAG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; UDP socket 监视接口,一些Linux本地工具(如:包含ss的iproute2)需要使用它<br />&#160; &#160; &#160; &#160; &#160; &#160; RAW: socket monitoring interface<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; RAW:套接字监控接口<br />&#160; &#160; &#160; &#160; &#160; &#160; INET: allow privileged process to administratively close sockets<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; INET:允许特权进程以管理方式关闭套接字<br />&#160; &#160; &#160; &#160; TCP: advanced congestion control<br />&#160; &#160; &#160; &#160; CONFIG_TCP_CONG_ADVANCED<br />&#160; &#160; &#160; &#160; &#160; &#160; 高级拥塞控制,子项提供多种拥塞控制算法供选用.如果没有特殊需求就别选了,<br />&#160; &#160; &#160; &#160; &#160; &#160; 内核会自动将默认的拥塞控制设为&quot;CUBIC&quot;并将&quot;new Reno&quot;作为候补.<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅在你确实知道自己需要的情况下选&quot;Y&quot;.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; TCP: MD5 Signature Option support (RFC2385)<br />&#160; &#160; &#160; &#160; CONFIG_TCP_MD5SIG<br />&#160; &#160; &#160; &#160; &#160; &#160; RFC2385中描述了一种对TCP会话进行MD5签名的保护机制.<br />&#160; &#160; &#160; &#160; &#160; &#160; 目前仅用于保护互联网运营商骨干路由器间的BGP会话.一般的路由器/服务器等设备根本不需要这个.<br />&#160; &#160; &#160; &#160; The IPv6 protocol<br />&#160; &#160; &#160; &#160; CONFIG_IPV6<br />&#160; &#160; &#160; &#160; &#160; &#160; 引领未来的IPv6支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: Privacy Extensions (RFC 3041) support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_PRIVACY<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6利用&quot;Stateless Address Autoconfiguration&quot;在无DHCP服务器的情况下,产生可用的&quot;临时IPv6地址&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 而本选项则为这个机制增加&quot;隐私扩展&quot;(RFC4941)保护.默认状态下,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 内核并不生产&quot;临时地址&quot;,需要&quot;echo 2 &gt;/proc/sys/net/ipv6/conf/all/use_tempaddr&quot;才能开启<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: Router Preference (RFC 4191) support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_ROUTER_PREF<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 主机连上IPv6网络后,会发出路由器邀请包(Router Solicitation),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 路由器则应答路由器公告包(Router Advertisement),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 其中包含网关地址/IPv6前缀/DNS地址,这样主机就能取得IPv6地址,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并连接到互联网上,这就是无状态地址自动分配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; (StateLess Address AutoConfiguration).&quot;Router Preference&quot;是&quot;Router Advertisement&quot;包的可选扩展.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 它可以改进主机选中路由器的能力,特别是在多归属(multi-homed)网络中.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: Route Information (RFC 4191) support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_ROUTE_INFO<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 对&quot;Route Information&quot;的实验性支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: Enable RFC 4429 Optimistic DAD<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_OPTIMISTIC_DAD<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 乐观重复地址检测(Optimistic Duplicate Address Detection)的实验性支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 可以更快的进行自动地址配置.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: AH transformation<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_AH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPsec AH 支持.不确定的选&quot;Y&quot;或&quot;M&quot;.AH头正在慢慢被ESP头取代.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: ESP transformation<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_ESP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPsec ESP 支持.不确定的选&quot;Y&quot;或&quot;M&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: ESP transformation offload<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;IPv6：ESP转换卸载<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: IPComp transformation<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_IPCOMP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6静荷载压缩协议(IP Payload Compression Protocol)(RFC3173)支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于支持IPsec.不确定的选&quot;Y&quot;或&quot;M&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: Mobility<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_MIP6<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 移动IPv6(RFC3775)支持.主要用于移动设备.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: Identifier Locator Addressing (ILA)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6：标识符定位器寻址(ILA)<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: IPsec transport mode<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_XFRM_MODE_TRANSPORT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPsec传输模式.常用于对等通信,用以提供内网安全.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 数据包经过了加密但IP头没有加密,因此任何标准设备或软件都可查看和使用IP头.不确定的选&quot;Y&quot;或&quot;M&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: IPsec tunnel mode<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_XFRM_MODE_TUNNEL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPsec隧道模式.用于提供外网安全(包括虚拟专用网络).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 整个数据包(数据头和负载)都已经过加密处理且分配有新的ESP头/IP头/验证尾,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 从而能够隐藏受保护站点的拓扑结构.不确定的选&quot;Y&quot;或&quot;M&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: IPsec BEET mode<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_XFRM_MODE_BEET<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPsec BEET模式.不确定的选&quot;Y&quot;或&quot;M&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: MIPv6 route optimization mode<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 移动IPv6(Mobile IPv6)路由优化模式.主要用于移动设备.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; Virtual (secure) IPv6: tunneling<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 虚拟（安全）IPv6：隧道<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: IPv6-in-IPv4 tunnel (SIT driver)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_SIT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 在IPv4网络上建立IPv6隧道.如果你希望可以通过IPv4网络接入一个IPv6网络,可以选&quot;Y&quot;或&quot;M&quot;,否则选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: IPv6 Rapid Deployment (6RD)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_SIT_6RD<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6快速部署(6RD)支持.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: IP-in-IPv6 tunnel (RFC2473)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_TUNNEL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6-in-IPv6/IPv4-in-IPv6 隧道(RFC2473)支持.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: GRE tunnel<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_GRE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于IPv6的通用路由封装(Generic Routing Encapsulation)隧道支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 该驱动主要用于对端是Cisco路由器的场合,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 因为Cisco的路由器特别偏好GRE隧道(而不是CONFIG_IPV6_TUNNEL),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并且GRE还允许通过隧道对组播进行再分发.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: Multiple Routing Tables<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_MULTIPLE_TABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 多重路由表(Multiple Routing Tables)支持.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IIPv6: source address based routing<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_SUBTREES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据源地址或前缀进行路由.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; IPv6: multicast routing<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_MROUTE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 测试性的IPv6组播路由支持.实际应用的场合很少,不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: multicast policy routing<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_MROUTE_MULTIPLE_TABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通常,组播路由器上会运行一个单独的用户态守护进程,根据源地址和目的地址来处理数据包.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 开启此项后,将能同时考虑数据包所带的标记(mark)和所通过的网络接口,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并可在用户空间同时运行多个守护进程,每一个进程处理一张路由表.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: PIM-SM version 2 support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IPV6_PIMSM_V2<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6 PIM multicast routing protocol PIM-SMv2 支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: Segment Routing Header encapsulation support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6：段路由头封装支持<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6: Segment Routing HMAC support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv6：段路由HMAC支持<br />&#160; &#160; &#160; &#160; NetLabel subsystem support<br />&#160; &#160; &#160; &#160; CONFIG_NETLABEL<br />&#160; &#160; &#160; &#160; &#160; &#160; NetLabel子系统支持.NetLabel子系统为诸如CIPSO与RIPSO之类能够在分组信息上添加标签的协议提供支持,<br />&#160; &#160; &#160; &#160; &#160; &#160; 看不懂就别选了.<br />&#160; &#160; &#160; &#160; Security Marking<br />&#160; &#160; &#160; &#160; CONFIG_NETWORK_SECMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; 对网络包进行安全标记,类似于nfmark,但主要是为安全目的而设计.看不懂的就别选了<br />&#160; &#160; &#160; &#160;Timestamping in PHY devices<br />&#160; &#160; &#160; &#160;CONFIG_NETWORK_PHY_TIMESTAMPING<br />&#160; &#160; &#160; &#160; &#160; &#160; 允许在硬件支持的前提下,为物理层(PHY)数据包打上时间戳.这会略微增加发送与接收的开销.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160;Network packet filtering framework (Netfilter)<br />&#160; &#160; &#160; &#160;CONFIG_NETFILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter可以对数据包进行过滤和修改,可以作为防火墙(&quot;packet filter&quot;或&quot;proxy-based&quot;)<br />&#160; &#160; &#160; &#160; &#160; &#160; 或网关(NAT)或代理(proxy)或网桥使用.<br />&#160; &#160; &#160; &#160; Network packet filtering debugging<br />&#160; &#160; &#160; &#160; CONFIG_NETFILTER_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供开发者调试Netfilter使用<br />&#160; &#160; &#160; &#160; Advanced netfilter configuration<br />&#160; &#160; &#160; &#160; CONFIG_NETFILTER_ADVANCED<br />&#160; &#160; &#160; &#160; &#160; &#160; 选&quot;Y&quot;将会显示所有模块供用户选择,选&quot;N&quot;则会隐藏一些不常用的模块,并自动将常用模块设为&quot;M&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; Bridged IP/ARP packets filtering<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_BRIDGE_NETFILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 如果你希望使用桥接防火墙就打开它.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; Core Netfilter Configuration<br />&#160; &#160; &#160; &#160; &#160; &#160; 核心Netfilter配置(当包流过Chain时如果match某个规则那么将由该规则的target来处理,<br />&#160; &#160; &#160; &#160; &#160; &#160; 否则将由同一个Chain中的下一个规则进行匹配,若不match所有规则那么最终将由该Chain的policy进行处理)<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter NFACCT over NFNETLINK interface<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_NETLINK_ACCT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许通过NFNETLINK接口支持NFACCT(记账).<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter NFQUEUE over NFNETLINK interface<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_NETLINK_QUEUE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许通过NFNETLINK接口支持NFQUEUE(排队).<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter LOG over NFNETLINK interface<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_NETLINK_LOG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许通过NFNETLINK接口支持&quot;LOG&quot;(日志).该选项废弃了ipt_ULOG和ebg_ulog机制,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并打算在将来废弃基于syslog的ipt_LOG和ip6t_LOG模块.<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter connection tracking support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 连接追踪(connection tracking)支持,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 连接跟踪把所有连接都保存在一个表格内,并将每个包关联到其所属的连接.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 可用于报文伪装或地址转换,也可用于增强包过滤能力.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection mark tracking support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_MARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对连接进行标记,与针对单独的包进行标记的不同之处在于它是针对连接流的.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;CONNMARK target 和 connmark match 需要它的支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking security mark support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_SECMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对连接进行安全标记,通常这些标记包(SECMARK)复制到其所属连接(CONNSECMARK),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 再从连接复制到其关联的包(SECMARK).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking zones<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_ZONES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;conntrack zones&quot;支持.通常,每个连接需要一个全局唯一标示符,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 而&quot;conntrack zones&quot;允许在不同zone内的连接使用相同的标识符.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Supply CT list in procfs (OBSOLETE)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_PROCFS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 已被废弃,选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking events<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_EVENTS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 连接跟踪事件支持.如果启用这个选项,连接跟踪代码将提供一个&quot;notifier&quot;链,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 它可以被其它内核代码用来获知连接跟踪状态的改变<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking timeout<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_TIMEOUT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 连接跟踪&quot;timeout&quot;扩展.这样你就可以在网络流上通过 CT target 附加超时策略.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking timestamping<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_TIMESTAMP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 时间戳支持.这样你就能在连接建立和断开时打上时间戳.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; DCCP protocol connection tracking support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CT_PROTO_DCCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; DCCP协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SCTP protocol connection tracking support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CT_PROTO_SCTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SCTP协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; UDP-Lite protocol connection tracking support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CT_PROTO_UDPLITE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; UDP-Lite支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Amanda backup protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_AMANDA<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Amanda备份协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; FTP protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_FTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 文件传输协议(FTP)支持.跟踪FTP连接需要额外的帮助程序.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; H.323 protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_H323<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; H.323协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IRC protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_IRC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IRC扩展协议DCC(Direct Client-to-Client Protocol)支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 该协议允许用户之间绕开服务器直接聊天和传输文件.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; NetBIOS name service protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_NETBIOS_NS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; NetBIOS协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SNMP service protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_SNMP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SNMP协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; PPtP protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_PPTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; RFC2637 点对点隧道协议(Point to Point Tunnelling Protocol)协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SANE protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_SANE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SANE协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SIP protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_SIP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SIP协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; TFTP protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_TFTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; TFTP协议支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking netlink interface<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CT_NETLINK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于netlink的用户接口支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking timeout tuning via Netlink<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CT_NETLINK_TIMEOUT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通过Netlink机制支持对连接追踪超时进行细粒度的调节:允许为特定的网络流指定超时策略,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 而不是使用统一的全局超时策略.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Connection tracking helpers in user-space via Netlink<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CT_NETLINK_HELPER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通过Netlink机制为用户空间的连接追踪帮助程序提供基础框架.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; NFQUEUE integration with Connection Tracking<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_NETLINK_QUEUE_CT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 开启此项后,即使网络包已经在队列(NFQUEUE)中,它依然可以包含连接追踪信息.<br />&#160; &#160; &#160; &#160; &#160; &#160; Transparent proxying support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_TPROXY<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 透明代理支持,也就是可以处理非本地的 IPv4 TCP/UDP 套接字.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 此功能需要配合一些iptables规则和策略路由才能工作.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 详见&quot;Documentation/networking/tproxy.txt&quot;文档.<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter Xtables support (required for ip_tables)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XTABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 如果你打算使用 ip_tables, ip6_tables, arp_tables 之一就必须选上</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; nfmark target and match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;nfmark&quot;是用户给包打上的一个自定义标记.用于match时,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许基于&quot;nfmark&quot;值对包进行匹配.用于target时,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许在&quot;mangle&quot;表中创建规则以改变包的&quot;nfmark&quot;值.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; ctmark target and match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_CONNMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;ctmark&quot;是用户以连接为组,给同一连接中的所有包打上的自定义标记.用法与&quot;nfmark&quot;相似.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; set target and match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_SET<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;set&quot;是ipset工具创建的IP地址集合.使用match可以对IP地址集合进行匹配,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 使用target可以对集合中的项进行增加和删除.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; AUDIT target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_AUDIT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为被drop/accept的包创建审计记录.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CHECKSUM target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_CHECKSUM<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于&quot;mangle&quot;表,为缺少校验和的包添加checksum字段的值.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 主要是为了兼容一些老旧的网络程序(例如某些dhcp客户端).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;CLASSIFY&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_CLASSIFY<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许为包设置优先级,一些qdiscs排队规则(atm,cbq,dsmark,pfifo_fast,htb,prio)需要使用它<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;CONNMARK&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_CONNMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_CONNMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;CONNSECMARK&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_CONNSECMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 针对链接进行安全标记,同时还会将连接上的标记还原到包上<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; (如果链接中的包尚未进行安全标记),通常与 SECMARK target 联合使用<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;CT&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_CT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许为包加上连接追踪相关的参数,比如&quot;event&quot;和&quot;helper&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;DSCP&quot; and &quot;TOS&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_DSCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; DSCP target 允许对IPv4/IPv6包头部的DSCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; (Differentiated Services Codepoint)字段(常用于Qos)进行修改.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; TOS target 允许在&quot;mangle&quot;表创建规则以修改IPv4包头的<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; TOS(Type Of Service)字段或IPv6包头的Priority字段.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;HL&quot; hoplimit target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_HL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; HL(IPv6)/TTL(IPv4) target 允许更改包头的 hoplimit/time-to-live 值.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;HMARK&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_HMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许在&quot;raw&quot;和&quot;mangle&quot;表中创建规则,以根据特定范围的哈希计算结果设置&quot;skbuff&quot;标记.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IDLETIMER target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_IDLETIMER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 每个被匹配的包的定时器都会被强制指定为规则指定的值,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 当超时发生时会触发一个sysfs文件系统的通知.剩余时间可以通过sysfs读取.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;LED&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_LED<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许在满足特定条件的包通过的时候,触发LED灯闪烁.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 比如可以用于控制网卡的状态指示灯仅在有SSH活动的时候才闪烁.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; LOG target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_LOG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许向syslog中记录包头信息.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;MARK&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_MARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_MARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;NETMAP&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_NETMAP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; NETMAP用于实现一对一的静态NAT(地址转换).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;NFLOG&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_NFLOG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通过nfnetlink_log记录日志.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;NFQUEUE&quot; target Support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_NFQUEUE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于替代老旧的 QUEUE target. 因为NFQUEUE能支持最多65535个队列,而QUEUE只能支持一个.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;NOTRACK&quot; target support (DEPRECATED)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_NOTRACK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 已被废弃,勿选.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;RATEEST&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_RATEEST<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; RATEEST target 允许测量网络流的传输速率.[注: rateest match 允许根据速率进行匹配.]<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; REDIRECT target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_REDIRECT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; REDIRECT是一种特别的NAT:所有进入的连接都被映射到其入口网卡的地址,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这样这些包就会&quot;流入&quot;本机而不是&quot;流过&quot;本机.这主要用于实现透明代理.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;TEE&quot; - packet cloning to alternate destination<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_TEE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 对包进行克隆,并将克隆的副本路由到另一个临近的路由器(Next Hop).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;TPROXY&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_TPROXY<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 类似于REDIRECT,但并不依赖于连接追踪和NAT,也只能用于&quot;mangle&quot;表,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于将网络流量重定向到透明代理.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;TRACE&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_TRACE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对包打标记,这样内核就可以记录每一个匹配到的规则.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;SECMARK&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_SECMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对包进行安全标记,用于安全子系统<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;TCPMSS&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_TCPMSS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许更改 TCP SYN 包的MSS(Maximum Segment Size)值,通常=MTU-40.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;TCPOPTSTRIP&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许从TCP包头中剥离所有TCP选项.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;addrtype&quot; address type match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_ADDRTYPE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 根据地址类型进行匹配: UNICAST, LOCAL, BROADCAST, ...<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;bpf&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_BPF<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; BPF(BSD Packet Filter)是一个强大的包匹配模块,用于匹配那些让过滤器返回非零值的包.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;cluster&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CLUSTER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这个模块可以用于创建网络服务器/防火墙集群,而无需借助价格昂贵的负载均衡设备.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通常,在包必须被本节点处理的条件下,这个match返回&quot;true&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这样,所有节点都可以看到所有的包,但只有匹配的节点才需要进行处理,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这样就将负载进行了分摊.而分摊算法是基于对源地址的哈希值.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;comment&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_COMMENT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这是一个&quot;伪match&quot;,目的是允许你在iptables规则集中加入注释<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;connbytes&quot; per-connection counter match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CONNBYTES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许针对单个连接内部每个方向(进/出)匹配已经传送的字节数/包数<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;connlabel&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CONNLABEL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许向连接分配用户自定义的标签名.内核仅存储bit值,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 而名称和bit之间的对应关系由用户空间处理.与&quot;connmark&quot;的不同之处在于:<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 可以同时为一个连接分配32个标志位(flag bit).<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;connlimit&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CONNLIMIT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据每一个客户端IP地址(或每一段客户端IP地址段)持有的并发连接数进行匹配.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;connmark&quot; connection mark match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CONNMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_CONNMARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;conntrack&quot; connection tracking match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CONNTRACK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 通用连接跟踪匹配,是&quot;state&quot;的超集,它允许额外的链接跟踪信息,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 在需要设置一些复杂的规则(比如网关)时很有用<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;cpu&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_CPU<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 根据处理包所使用的CPU是哪个进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;dccp&quot; protocol match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_DCCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; DCCP是打算取代UDP的新传输协议,它在UDP的基础上增加了流控和拥塞控制机制,面向实时业务<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;devgroup&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_DEVGROUP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据网卡所属的&quot;设备组&quot;进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;dscp&quot; and &quot;tos&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_DSCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; dscp match 允许根据IPv4/IPv6包头的DSCP字段进行匹配,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; tos match 允许根据IPv4包头的TOS字段进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;ecn&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_ECN<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据IPv4 TCP包头的ECN字段进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;esp&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_ESP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对IPSec包的ESP头中的SPI(安全参数序列)范围进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hashlimit&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_HASHLIMIT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 此项的目的是取代&quot;limit&quot;,它基于你选定的源/目的地址和/或端口动态创建&quot;limit bucket&quot;哈希表.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这样你就可以迅速创建类似这样的匹配规则:(1)为给定的目的地址以每秒10k个包的速度进行<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 匹配;(2)为给定的源地址以每秒500个包的速率进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;helper&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_HELPER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 加载特定协议的连接跟踪辅助模块,由该模块过滤所跟踪的连接类型的包,比如ip_conntrack_ftp模块<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hl&quot; hoplimit/TTL match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_HL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于IPv6包头的hoplimit字段,或IPv4包头的time-to-live字段进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;iprange&quot; address range match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_IPRANGE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 根据IP地址范围进行匹配,而普通的iptables只能根据&quot;IP/mask&quot;的方式进行匹配.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;ipvs&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_IPVS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据包的IPVS属性进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;length&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_LENGTH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对包的长度进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;limit&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_LIMIT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据包的进出速率进行规则匹配,常和&quot;LOG target&quot;配合使用以抵抗某些Dos攻击<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;mac&quot; address match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_MAC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据以太网的MAC地址进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;mark&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_MARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_MARK<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;multiport&quot; Multiple port match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_MULTIPORT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对TCP或UDP包同时匹配多个不连续的端口(通常情况下只能匹配单个端口或端口范围)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;nfacct&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_NFACCT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许通过nfnetlink_acct使用扩展记账<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;osf&quot; Passive OS fingerprint match<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_OSF<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 开启Passive OS Fingerprinting模块,以允许通过进入的TCP SYN包被动匹配远程操作系统.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 规则和加载程序可以从这里获取:http://www.ioremap.net/projects/osf<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;owner&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_OWNER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于创建套接字的本地进程身份(user/group)进行匹配,还可以用于检查一个套接字是否确实存在<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPsec &quot;policy&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_POLICY<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于IPsec policy进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;physdev&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_PHYSDEV<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对进入或离开所经过的物理网口进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;pkttype&quot; packet type match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_PKTTYPE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对封包目的地址类别(广播/组播/直播)进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;quota&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_QUOTA<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对总字节数的限额值进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;rateest&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_RATEEST<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 根据 RATEEST target 评估的速率值进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;realm&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_REALM<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据iptables中的路由子系统中的realm值进行匹配.它与tc中的CONFIG_NET_CLS_ROUTE4非常类似.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;recent&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_RECENT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; recent match 用于创建一个或多个最近使用过的地址列表,然后又可以根据这些列表再进行匹配.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;sctp&quot; protocol match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_SCTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 支持根据流控制传输协议(SCTP)源/目的端口和&quot;chunk type&quot;进行匹配.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;socket&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_SOCKET<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; can be used to match packets for which a TCP or UDP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; socket lookup finds a valid socket. It can be used in<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; combination with the MARK target and policy routing to<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; implement full featured non-locally bound sockets.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;state&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_STATE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这是对包进行分类的有力工具,它允许利用连接跟踪信息对连接中处于特定状态的包进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;statistic&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_STATISTIC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据一个给定的百分率对包进行周期性的或随机性的匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;string&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_STRING<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据包所承载的数据中包含的特定字符串进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;tcpmss&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_TCPMSS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许根据TCP SYN包头中的MSS(最大分段长度)选项的值进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;time&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_TIME<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 根据包的到达时刻(外面进入的包)或者离开时刻(本地生成的包)进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;u32&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NETFILTER_XT_MATCH_U32<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;u32&quot;允许从包中提取拥有特定mask的最多4字节数据,将此数据移动(shift)特定的位数,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 然后测试其结果是否位于特定的集合范围内.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 更多细节可以直接参考内核源码(net/netfilter/xt_u32.c)<br />&#160; &#160; &#160; &#160; IP set support<br />&#160; &#160; &#160; &#160; CONFIG_IP_SET<br />&#160; &#160; &#160; &#160; &#160; &#160; 为内核添加IP集(IP set)支持,然后就可以使用CONFIG_NETFILTER_XT_SET功能.此<br />&#160; &#160; &#160; &#160; &#160; &#160; 特性必须配合用户态工具ipset一起使用.<br />&#160; &#160; &#160; &#160; &#160; &#160; Maximum number of IP sets<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_MAX<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 默认的最大&quot;set&quot;数,取值范围是[2,65534].此值也可以由ip_set模块的max_sets参数设置.<br />&#160; &#160; &#160; &#160; &#160; &#160; bitmap:ip set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_BITMAP_IP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;bitmap:ip&quot;集合类型.根据IP地址范围设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; bitmap:ip,mac set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_BITMAP_IPMAC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;bitmap:ip,mac&quot;集合类型.根据IP/MAC地址对范围设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; bitmap:port set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_BITMAP_PORT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;bitmap:port&quot;集合类型.根据端口范围设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:ip set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_IP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:ip&quot;集合类型.为多个离散的IP地址设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:ip,port set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_IPPORT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:ip,port&quot;集合类型.为多个离散的IP/MAC地址对设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:ip,port,ip<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_IPPORTIP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:ip,port,ip&quot;集合类型.为多个离散的IP/端口/IP三元组设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:ip,port,net set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_IPPORTNET<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:ip,port,net&quot;集合类型.为多个离散的IP/端口/网段三元组设定集合.<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:net set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_NET<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:net&quot;集合类型.为多个离散的网段设定集合<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:net,port set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_NETPORT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:net,port&quot;集合类型.为多个离散的网段/端口对设定集合<br />&#160; &#160; &#160; &#160; &#160; &#160; hash:net,iface set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_HASH_NETIFACE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;hash:net,iface&quot;集合类型.为多个离散的网段/网卡接口对设定集合<br />&#160; &#160; &#160; &#160; &#160; &#160; list:set set support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_SET_LIST_SET<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;list:set&quot;集合类型.将多个集合组成一个更大的集合</p><p>&#160; &#160; &#160; &#160; IP virtual server support<br />&#160; &#160; &#160; &#160; CONFIG_IP_VS<br />&#160; &#160; &#160; &#160; &#160; &#160; IPVS(IP Virtual Server)支持.IPVS可以帮助LVS基于多个后端真实服务器创建一个高性能的虚拟服务器.<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以使用三种具体的方法实现:NAT,隧道,直接路由(使用较广).</p><p>&#160; &#160; &#160; &#160; &#160; &#160; IPv6 support for IPVS<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_IPV6<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为IPVS添加IPv6支持<br />&#160; &#160; &#160; &#160; &#160; &#160; IP virtual server debugging<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为IPVS添加调试支持<br />&#160; &#160; &#160; &#160; &#160; &#160; IPVS connection table size (the Nth power of 2)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_TAB_BITS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 设置IPVS连接哈希表的大小(2CONFIG_IP_VS_TAB_BITS),取值范围是[8,20],<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 默认值12的意思是哈希表的大小是212=4096项.IPVS连接哈希表使用链表来处理哈希碰撞.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 使用大的哈希表能够显著减少碰撞几率,特别是哈希表中有成千上万连接的时候.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 比较恰当的值差不多等于每秒的新建连接数乘以每个连接的平均持续秒数.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 太小的值会造成太多碰撞,从而导致性能大幅下降;太大的值又会造成占用太多不必要的内存<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; (每个表项8字节+每个连接128字节).该值也可以通过ip_vs模块的conn_tab_bits参数进行设置.<br />&#160; &#160; &#160; &#160; &#160; &#160; TCP load balancing support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_PROTO_TCP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; TCP传输协议负载均衡支持<br />&#160; &#160; &#160; &#160; &#160; &#160; UDP load balancing support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_PROTO_UDP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; UDP传输协议负载均衡支持<br />&#160; &#160; &#160; &#160; &#160; &#160; ESP load balancing support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_PROTO_ESP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPSec ESP(Encapsulation Security Payload)传输协议负载均衡支持<br />&#160; &#160; &#160; &#160; &#160; &#160; AH load balancing support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_PROTO_AH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPSec AH(Authentication Header)传输协议负载均衡支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; SCTP load balancing support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_PROTO_SCTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SCTP传输协议负载均衡支持<br />&#160; &#160; &#160; &#160; &#160; &#160; round-robin scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_RR<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 循环分散算法:最简单的调度算法,将连接简单的循环分散到后端服务器上<br />&#160; &#160; &#160; &#160; &#160; &#160; weighted round-robin scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_WRR<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于权重的循环分散算法:在循环分散的基础上,权重较高的后端服务器接纳较多的连接<br />&#160; &#160; &#160; &#160; &#160; &#160; least-connection scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_LC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 最少连接算法:将连接优先分配到活动连接最少的后端服务器<br />&#160; &#160; &#160; &#160; &#160; &#160; weighted least-connection scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_WLC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于权重的最少连接算法:结合考虑活动连接数与服务器权重<br />&#160; &#160; &#160; &#160; &#160; &#160; locality-based least-connection scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_LBLC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于目的IP的最少连接算法(常用于缓存集群):<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 优先根据目的IP地址将连接分配到特定的后端,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 仅在这些后端过载时(活动连接数大于其权重)才分散到其他后端.<br />&#160; &#160; &#160; &#160; &#160; &#160; locality-based least-connection with replication scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_LBLCR<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 与LBLC类似,不同之处在于:前端负载均衡器会像NAT一样同时记住客户端IP与后端的<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 对应关系,并在新的连接到来的时候,复用这个对应关系.<br />&#160; &#160; &#160; &#160; &#160; &#160; destination hashing scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_DH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 目标地址哈希表算法:简单的根据静态设定的目标IP地址哈希表将连接分发到后端<br />&#160; &#160; &#160; &#160; &#160; &#160; source hashing scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_SH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 源地址哈希表算法:简单的根据静态设定的源IP地址哈希表将连接分发到后端<br />&#160; &#160; &#160; &#160; &#160; &#160; shortest expected delay scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_SED<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 最小期望延迟算法:将连接分配到根据期望延迟公式((Ci+1)/Ui)算得的延迟最小的后端.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;i&quot;是后端服务器编号,&quot;Ci&quot;是该服务器当前的连接数,&quot;Ui&quot;是该服务器的权重.<br />&#160; &#160; &#160; &#160; &#160; &#160; never queue scheduling<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_NQ<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 无排队算法:这是一个两阶段算法,如果有空闲服务器,就直接分发到空闲服务器<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; (而不是等待速度最快的服务器),如果没有空闲服务器,就分发到期望延迟最小的服务器(SED算法).<br />&#160; &#160; &#160; &#160; &#160; &#160; IPVS source hashing table size (the Nth power of 2)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_SH_TAB_BITS<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 将源IP地址映射到后端服务器所使用的哈希表的大小(2CONFIG_IP_VS_SH_TAB_BITS),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 取值范围是[4,20],默认值8的意思是哈希表的大小是28=256项.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 理想的大小应该是所有后端的权重乘以后端总数?<br />&#160; &#160; &#160; &#160; &#160; &#160; FTP protocol helper<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_FTP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; FTP协议连接追踪帮助<br />&#160; &#160; &#160; &#160; &#160; &#160; Netfilter connection tracking<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_NFCT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Netfilter连接追踪支持<br />&#160; &#160; &#160; &#160; &#160; &#160; SIP persistence engine<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_VS_PE_SIP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于SIP Call-ID提供持久连接支持</p><p>&#160; &#160; &#160; &#160; IP: Netfilter Configuration<br />&#160; &#160; &#160; &#160; &#160; &#160; 针对IPv4的Netfilter配置</p><p>&#160; &#160; &#160; &#160; &#160; &#160; IPv4 connection tracking support (required for NAT)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_IPV4<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv4链接跟踪.可用于包伪装或地址转换,也可用于增强包过滤能力</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; proc/sysctl compatibility with old connection tracking<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_CONNTRACK_PROC_COMPAT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于兼容老旧的连接追踪用户态程序</p><p>&#160; &#160; &#160; &#160; &#160; &#160; IP tables support (required for filtering/masq/NAT)<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_IPTABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 要用iptables就肯定要选上</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;ah&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_MATCH_AH<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对IPSec包头的AH字段进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;ecn&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_MATCH_ECN<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_MATCH_ECN<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;rpfilter&quot; reverse path filter match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_MATCH_RPFILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 对进出都使用同一个网络接口的包进行匹配<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;ttl&quot; match support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_MATCH_TTL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_MATCH_HL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Packet filtering<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_FILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 定义filter表,以允许对包进行过滤</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; REJECT target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_REJECT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许返回一个ICMP错误包而不是简单的丢弃包</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; ULOG target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_ULOG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 反对使用该选项,因为它已经被CONFIG_NETFILTER_NETLINK_LOG代替<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; IPv4 NAT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_NAT_IPV4<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许进行伪装/端口转发以及其它的NAT功能,仅在你需要使用iptables中的nat表时才需要选择</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; MASQUERADE target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_MASQUERADE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SNAT是指在数据包从网卡发送出去的时候,把数据包中的源地址部分替换为指定的IP,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这样,接收方就认为数据包的来源是被替换的那个IP的主机.伪装(MASQUERADE)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 是一种特殊类型的SNAT:MASQUERADE是用发送数据的网卡上的IP来替换源IP,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于那些IP不固定的场合(比如拨号或者通过DHCP分配)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; NETMAP target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_NETMAP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_TARGET_NETMAP.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; REDIRECT target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_REDIRECT<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_TARGET_REDIRECT.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Basic SNMP-ALG support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NF_NAT_SNMP_BASIC<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为SNMP荷载实现ALG(Application Layer Gateway)支持(RFC2962).</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Packet mangling<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_MANGLE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 在iptables中启用mangle表以便对包进行各种修改,常用于改变包的路由</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CLUSTERIP target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_CLUSTERIP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CLUSTERIP target 允许你无需使用昂贵的负载均衡设备也能创建廉价的负载均衡集群<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; ECN target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_ECN<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 用于mangle表,可以去除IPv4包头的ECN(Explicit Congestion Notification)位,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 主要用于在保持ECN功能的前提下,去除网络上的&quot;ECN黑洞&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &quot;TTL&quot; target support<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_TARGET_TTL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 这只是一个兼容旧配置的选项,等价于CONFIG_NETFILTER_XT_TARGET_HL.</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; raw table support (required for NOTRACK/TRACE)<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_RAW<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 在iptables中添加一个raw表,该表在netfilter框架中非常靠前,<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并在PREROUTING和OUTPUT链上有钩子,从而可以对收到的数据包在连接跟踪前进行处理<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Security table<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_SECURITY<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 在iptables中添加一个security表,以支持强制访问控制(Mandatory Access Control)策略</p><p>&#160; &#160; &#160; &#160; &#160; &#160; ARP tables support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_ARPTABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; arptables支持</p><p>&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; ARP packet filtering<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_ARPFILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; ARP包过滤.对于进入和离开本地的ARP包定义一个filter表,在桥接的情况下还可以应用于<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 被转发的ARP包<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; ARP payload mangling<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CONFIG_IP_NF_ARP_MANGLE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许对ARP包的荷载部分进行修改,比如修改源和目标物理地址</p><p>&#160; &#160; &#160; &#160; IPv6: Netfilter Configuration<br />&#160; &#160; &#160; &#160; &#160; &#160; 针对IPv6的Netfilter配置.其子项内容类似于IPv4,需要的话可以参考前面IPv4的Netfilter配置进行选择<br />&#160; &#160; &#160; &#160; DECnet: Netfilter Configuration<br />&#160; &#160; &#160; &#160; &#160; &#160; 针对DECnet的Netfilter配置<br />&#160; &#160; &#160; &#160; Ethernet Bridge tables (ebtables) support<br />&#160; &#160; &#160; &#160; CONFIG_BRIDGE_NF_EBTABLES<br />&#160; &#160; &#160; &#160; &#160; &#160; 针对以太网桥的ebtables Netfilter配置</p><p>&#160; &#160; The DCCP Protocol<br />&#160; &#160; CONFIG_IP_DCCP<br />&#160; &#160; &#160; &#160; 数据报拥塞控制协议(Datagram Congestion Control Protocol)在UDP的基础上增加了流控和拥塞控制机制,<br />&#160; &#160; &#160; &#160; 使数据报协议能够更好地用于流媒体业务的传输<br />&#160; &#160; The SCTP Protocol<br />&#160; &#160; CONFIG_IP_SCTP<br />&#160; &#160; &#160; &#160; 流控制传输协议(Stream Control Transmission Protocol)是一种新兴的传输层协议.<br />&#160; &#160; &#160; &#160; TCP协议一次只能连接一个IP地址而在SCTP协议一次可以连接多个IP地址且<br />&#160; &#160; &#160; &#160; 可以自动平衡网络负载,一旦某一个IP地址失效会自动将网络负载转移到其他IP地址上<br />&#160; &#160; The RDS Protocol<br />&#160; &#160; CONFIG_RDS<br />&#160; &#160; &#160; &#160; 可靠数据报套接字(Reliable Datagram Sockets)协议支持.<br />&#160; &#160; The TIPC Protocol<br />&#160; &#160; CONFIG_TIPC<br />&#160; &#160; &#160; &#160; 透明内部进程间通信协议(Transparent Inter Process Communication),<br />&#160; &#160; &#160; &#160; 以共享内存为基础实现任务和资源的调度,专门用于集群内部通信<br />&#160; &#160; Asynchronous Transfer Mode (ATM)<br />&#160; &#160; CONFIG_ATM<br />&#160; &#160; &#160; &#160; 异步传输模式(ATM)支持.主要用于高速LAN和WAN.目前已经日薄西山了.<br />&#160; &#160; Layer Two Tunneling Protocol (L2TP)<br />&#160; &#160; CONFIG_L2TP<br />&#160; &#160; &#160; &#160; 第二层隧道协议(RFC2661)支持<br />&#160; &#160; 802.1d Ethernet Bridging<br />&#160; &#160; CONFIG_BRIDGE<br />&#160; &#160; &#160; &#160; 802.1d以太网桥<br />&#160; &#160; 802.1Q/802.1ad VLAN Support<br />&#160; &#160; CONFIG_VLAN_8021Q<br />&#160; &#160; &#160; &#160; 802.1Q虚拟局域网<br />&#160; &#160; DECnet Support<br />&#160; &#160; CONFIG_DECNET<br />&#160; &#160; &#160; &#160; DECnet协议<br />&#160; &#160; ANSI/IEEE 802.2 LLC type 2 Support<br />&#160; &#160; CONFIG_LLC2<br />&#160; &#160; &#160; &#160; PF_LLC类型套接字支持.也就是IEEE 802.2 LLC 2<br />&#160; &#160; The IPX protocol<br />&#160; &#160; CONFIG_IPX<br />&#160; &#160; &#160; &#160; IPX协议是由Novell公司提出的运行于OSI模型第三层的协议,具有可路由的特性,<br />&#160; &#160; &#160; &#160; IPX的地址分为网络地址和主机地址,网络地址由管理员分配,主机地址为MAC地址.<br />&#160; &#160; &#160; &#160; 由于IP协议的广泛使用,IPX的应用早已日薄西山.<br />&#160; &#160; Appletalk protocol support<br />&#160; &#160; CONFIG_ATALK<br />&#160; &#160; &#160; &#160; Appletalk是苹果公司创建的一组网络协议,仅用于苹果系列计算机.<br />&#160; &#160; CCITT X.25 Packet Layer<br />&#160; &#160; CONFIG_X25<br />&#160; &#160; &#160; &#160; CCITT X.25协议集支持.<br />&#160; &#160; LAPB Data Link Driver<br />&#160; &#160; CONFIG_LAPB<br />&#160; &#160; &#160; &#160; LAPB协议支持.<br />&#160; &#160; Phonet protocols family<br />&#160; &#160; CONFIG_PHONET<br />&#160; &#160; &#160; &#160; PhoNet是Nokia开发的面相数据包的通信协议,仅用于Nokia maemo/meego产品.<br />&#160; &#160; IEEE Std 802.15.4 Low-Rate Wireless Personal Area Networks support<br />&#160; &#160; CONFIG_IEEE802154<br />&#160; &#160; &#160; &#160; IEEE Std 802.15.4 定义了一个低速率/低功耗/低复杂度的短距离个人无线网络规范.<br />&#160; &#160; &#160; &#160; 主要用于物联网中的传感器/交换器之类设备之间的互联.</p><p>&#160; &#160; &#160; &#160; 6lowpan support over IEEE 802.15.4<br />&#160; &#160; &#160; &#160; CONFIG_IEEE802154_6LOWPAN<br />&#160; &#160; &#160; &#160; &#160; &#160; 在IEEE 802.15.4上支持IPv6压缩.<br />&#160; &#160; &#160; &#160; Generic IEEE 802.15.4 Soft Networking Stack (mac802154)<br />&#160; &#160; &#160; &#160; CONFIG_MAC802154<br />&#160; &#160; &#160; &#160; &#160; &#160; 为SoftMAC设备(仅实现了PHY层)实现硬件独立的IEEE Std 802.15.4协议栈.使用HardMAC设备的用户应该选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; [注意]这里的实现既未经过认证,也未进行充分的兼容性测试.</p><p>&#160; &#160; QoS and/or fair queueing<br />&#160; &#160; CONFIG_NET_SCHED<br />&#160; &#160; &#160; &#160; QoS(Quality of Service)支持.当内核有多个包需要通过网络发送的时候,它需要决定哪个包先发,那个包后发,<br />&#160; &#160; &#160; &#160; 哪个包丢弃.这就是包调度算法.关闭此项表示内核使用最简单的FIFO算法,<br />&#160; &#160; &#160; &#160; 开启此项后就可以使用多种不同的调度算法(需要配合用户层工具iproute2+tc).<br />&#160; &#160; &#160; &#160; QoS还用于支持diffserv(Differentiated Services)和RSVP(Resource Reservation Protocol)功能.<br />&#160; &#160; &#160; &#160; 包调度的状态信息可以从&quot;/proc/net/psched&quot;文件中获取.仅在你确实需要的时候选&quot;Y&quot;.<br />&#160; &#160; Data Center Bridging support<br />&#160; &#160; CONFIG_DCB<br />&#160; &#160; &#160; &#160; DCB(Data Center Bridging)支持.<br />&#160; &#160; &#160; &#160; 数据中心桥接是一组可增强传统以太网功能,以管理通信的功能,尤其适用于网络通信流量和传输率都很高的环境中.<br />&#160; &#160; &#160; &#160; 光纤通道可专用于承载此类型的通信.但是,如果使用专用链路来仅提供光纤通道通信,<br />&#160; &#160; &#160; &#160; 则成本可能会很高.因此,更多情况下使用以太网光纤通道.<br />&#160; &#160; &#160; &#160; DCB功能可满足光纤通道对遍历以太网时包丢失的敏感度要求.<br />&#160; &#160; &#160; &#160; DCB允许对等方基于优先级区分通信.通过区分优先级,可确保在主机之间发生拥塞时,<br />&#160; &#160; &#160; &#160; 保持较高优先级通信的包完整性.使用DCB交换协议,<br />&#160; &#160; &#160; &#160; 通信主机可以交换会影响高速网络通信的配置信息.然后,对等方可对公用配置进行协商,<br />&#160; &#160; &#160; &#160; 确保通信流不中断,同时防止高优先级包出现包丢失.这些功能都需要底层的网卡支持.<br />&#160; &#160; &#160; &#160; 一般网卡都是不支持的.所以不确定的可以选&quot;N&quot;.<br />&#160; &#160; DNS Resolver support<br />&#160; &#160; CONFIG_DNS_RESOLVER<br />&#160; &#160; &#160; &#160; 内核DNS解析支持.用于支持CONFIG_AFS_FS/CONFIG_CIFS/CONFIG_CIFS_SMB2模块.<br />&#160; &#160; &#160; &#160; 此功能需要用户态程序&quot;/sbin/dns.resolve&quot;和配置文件&quot;/etc/request-key.conf&quot;的支持.<br />&#160; &#160; &#160; &#160; 更多信息参见&quot;Documentation/networking/dns_resolver.txt&quot;文档,不确定的选&quot;N&quot;.<br />&#160; &#160; B.A.T.M.A.N. Advanced Meshing Protocol<br />&#160; &#160; CONFIG_BATMAN_ADV<br />&#160; &#160; &#160; &#160; B.A.T.M.A.N.(更好的移动无线网络方案)是一种用于 multi-hop ad-hoc mesh 网络的路由协议.<br />&#160; &#160; &#160; &#160; 它是一种去中心化分布式无线Adhoc模式,特别适用于自然灾害等紧急情况下,创建临时的无线网络.不确定的选&quot;N&quot;.<br />&#160; &#160; Open vSwitch<br />&#160; &#160; CONFIG_OPENVSWITCH<br />&#160; &#160; &#160; &#160; Open vSwitch 是一个多层虚拟交换标准.此选项提供了内核级的高速转发功能<br />&#160; &#160; &#160; &#160; (需要配合用户态守护进程ovs-vswitchd来实现).<br />&#160; &#160; Virtual Socket protocol<br />&#160; &#160; CONFIG_VSOCKETS<br />&#160; &#160; &#160; &#160; 这是一个类似于TCP/IP的协议,用于虚拟机之间以及虚拟机与宿主之间的通信.<br />&#160; &#160; &#160; &#160; 开启此项后,还需要从子项中选择适用于特定虚拟化技术的传输协议.</p><p>&#160; &#160; &#160; &#160; VMware VMCI transport for Virtual Sockets<br />&#160; &#160; &#160; &#160; CONFIG_VMWARE_VMCI_VSOCKETS<br />&#160; &#160; &#160; &#160; &#160; &#160; 适用于VMware虚拟化技术的VMCI传输协议支持.</p><p>&#160; &#160; NETLINK: mmaped IO<br />&#160; &#160; CONFIG_NETLINK_MMAP<br />&#160; &#160; &#160; &#160; 基于内存映射机制的 netlink IO 支持.<br />&#160; &#160; &#160; &#160; 这样可以避免在用户空间与内存空间之间复制数据,从而提升操作速度.建议开启.<br />&#160; &#160; NETLINK: socket monitoring interface<br />&#160; &#160; CONFIG_NETLINK_DIAG<br />&#160; &#160; &#160; &#160; NETLINK socket 监视接口.ss这样的诊断工具需要它.<br />&#160; &#160; Network priority cgroup<br />&#160; &#160; CONFIG_NETPRIO_CGROUP<br />&#160; &#160; &#160; &#160; Cgroup子系统支持:基于每个网络接口为每个进程分配网络使用优先级.<br />&#160; &#160; enable BPF Just In Time compiler<br />&#160; &#160; CONFIG_BPF_JIT<br />&#160; &#160; &#160; &#160; BPF(Berkeley Packet Filter)的过滤功能通常由一个解释器(interpreter)解释执行BPF虚拟机指令的方式工作.<br />&#160; &#160; &#160; &#160; 开启此项,内核在加载过滤指令后,会将其编译为本地指令,以加快执行速度.<br />&#160; &#160; &#160; &#160; 网络嗅探程序(libpcap/tcpdump)可以从中受益.<br />&#160; &#160; &#160; &#160; 注意:需要&quot;echo 1 &gt; /proc/sys/net/core/bpf_jit_enable&quot;之后才能生效.<br />&#160; &#160; Network testing<br />&#160; &#160; &#160; &#160; 网络测试,仅供调试使用</p><p>Amateur Radio support<br />CONFIG_HAMRADIO<br />&#160; &#160; 业余无线电支持.供无线电爱好者进行自我训练/相互通讯/技术研究<br />&#160; &#160;<br />CAN bus subsystem support<br />CONFIG_CAN<br />&#160; &#160; CAN(Controller Area Network)是一个低速串行通信协议.<br />&#160; &#160; 被广泛地应用于工业自动化/船舶/医疗设备/工业设备等嵌入式领域.<br />&#160; &#160; 更多信息参见&quot;Documentation/networking/can.txt&quot;文件.<br />&#160; &#160;<br />IrDA (infrared) subsystem support<br />CONFIG_IRDA<br />&#160; &#160; 红外线通讯技术支持,主要用于嵌入式环境,某些老旧的笔记本上也可能会有红外接口.<br />&#160; &#160;<br />Bluetooth subsystem support<br />CONFIG_BT<br />&#160; &#160; 蓝牙支持.蓝牙目前已经基本取代红外线,成为嵌入式设备/智能设备/笔记本的标配近<br />&#160; &#160; 距离(小于10米)通信设备.在Linux上通常使用来自BlueZ的hciconfig和bluetoothd工具操作蓝牙通信.<br />&#160; &#160; Bluetooth Classic (BR/EDR) features<br />&#160; &#160;<br />&#160; &#160; RFCOMM protocol support<br />&#160; &#160; CONFIG_BT_RFCOMM<br />&#160; &#160; &#160; &#160; 虚拟串口协议(RFCOMM)是一个面向连接的流传输协议,提供RS232控制和状态信号,<br />&#160; &#160; &#160; &#160; 从而模拟串口的功能.它被用于支持拨号网络,OBEX(Object Exchange),以及某些蓝牙程序(例如文件传输).<br />&#160; &#160; &#160; &#160; RFCOMM TTY support<br />&#160; &#160; &#160; &#160; CONFIG_BT_RFCOMM_TTY<br />&#160; &#160; &#160; &#160; &#160; &#160; 允许在RFCOMM通道上模拟TTY终端<br />&#160; &#160; BNEP protocol support<br />&#160; &#160; CONFIG_BT_BNEP<br />&#160; &#160; &#160; &#160; 蓝牙网络封装协议(Bluetooth Network Encapsulation Protocol)可以在蓝牙上运行<br />&#160; &#160; &#160; &#160; 其他网络协议(TCP/IP). Bluetooth PAN(Personal Area Network)需要它的支持.<br />&#160; &#160; &#160; &#160; Multicast filter support<br />&#160; &#160; &#160; &#160; CONFIG_BT_BNEP_MC_FILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; 组播支持<br />&#160; &#160; &#160; &#160; Protocol filter support<br />&#160; &#160; &#160; &#160; CONFIG_BT_BNEP_PROTO_FILTER<br />&#160; &#160; &#160; &#160; &#160; &#160; 协议过滤器支持<br />&#160; &#160; CMTP protocol support<br />&#160; &#160; CONFIG_BT_CMTP<br />&#160; &#160; &#160; &#160; CMTP(CAPI消息传输协议)用于支持已在上世纪被淘汰的ISDN设备.不确定的选&quot;N&quot;.<br />&#160; &#160; HIDP protocol support<br />&#160; &#160; CONFIG_BT_HIDP<br />&#160; &#160; &#160; &#160; 人机接口设备协议(Human Interface Device Protocol)用于支持各种人机接口设备(比如鼠标/键盘/耳机等).<br />&#160; &#160; Bluetooth High Speed (HS) features<br />&#160; &#160; &#160; &#160; &#160;蓝牙高速（HS）功能<br />&#160; &#160; Bluetooth Low Energy (LE) features<br />&#160; &#160; &#160; &#160; &#160;蓝牙低功耗（LE）功能<br />&#160; &#160; Enable LED triggers<br />&#160; &#160; &#160; &#160; &#160;启用LED触发器<br />&#160; &#160; Bluetooth self testing support<br />&#160; &#160; &#160; &#160; &#160;蓝牙自检支持<br />&#160; &#160; Export Bluetooth internals in debugfs<br />&#160; &#160; &#160; &#160; &#160;在debugfs中导出蓝牙内部<br />&#160; &#160; Bluetooth device drivers<br />&#160; &#160; &#160; &#160; 各种蓝牙设备驱动<br />&#160; &#160; &#160; &#160; HCI USB driver<br />&#160; &#160; &#160; &#160; CONFIG_BT_HCIBTUSB<br />&#160; &#160; &#160; &#160; &#160; &#160; 使用USB接口的蓝牙设备支持<br />&#160; &#160; &#160; &#160; HCI SDIO driver<br />&#160; &#160; &#160; &#160; CONFIG_BT_HCIBTSDIO<br />&#160; &#160; &#160; &#160; &#160; &#160; 使用SDIO接口的蓝牙设备支持<br />&#160; &#160; &#160; &#160; HCI UART driver<br />&#160; &#160; &#160; &#160; CONFIG_BT_HCIUART<br />&#160; &#160; &#160; &#160; &#160; &#160; 使用串口的蓝牙设备支持.此外,基于UART的蓝牙PCMCIA和CF设备也需要此模块的支持.<br />&#160; &#160; &#160; &#160; &#160; &#160; UART (H4) protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_BT_HCIUART_H4<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 大多数使用UART接口的蓝牙设备(包括PCMCIA和CF卡)都使用这个协议.<br />&#160; &#160; &#160; &#160; &#160; &#160; BCSP protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_BT_HCIUART_BCSP<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于CSR(Cambridge Silicon Radio)公司的BlueCore系列芯片的蓝牙设备(包括PCMCIA和CF卡)支持<br />&#160; &#160; &#160; &#160; &#160; &#160; Atheros AR300x serial support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_BT_HCIUART_ATH3K<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于Atheros AR300x系列芯片的蓝牙设备支持<br />&#160; &#160; &#160; &#160; &#160; &#160; HCILL protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_BT_HCIUART_LL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 基于Texas Instruments公司的BRF芯片的蓝牙设备支持<br />&#160; &#160; &#160; &#160; &#160; &#160; Three-wire UART (H5) protocol support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_BT_HCIUART_3WIRE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Three-wire UART (H5) 协议假定UART通信可能存在各种错误,从而使得CTS/RTS引脚线变得可有可无.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 看不懂就可以不选.</p><p>&#160; &#160; &#160; &#160; HCI VHCI (Virtual HCI device) driver<br />&#160; &#160; &#160; &#160; CONFIG_BT_HCIVHCI<br />&#160; &#160; &#160; &#160; &#160; &#160; 模拟蓝牙设备支持.主要用于开发<br />&#160; &#160; &#160; &#160; {大多数蓝牙设备并不需要特定的独立驱动,此处省略的独立驱动仅是为了驱动那些不严格遵守蓝牙规范的芯片}</p><p>RxRPC session sockets<br />CONFIG_AF_RXRPC<br />&#160; &#160; RxRPC会话套接字支持(仅包括传输部分,不含表示部分).CONFIG_AFS_FS依赖于它.<br />&#160; &#160; 不确定的选&quot;N&quot;.详情参见&quot;Documentation/networking/rxrpc.txt&quot;文档.<br />Wireless<br />CONFIG_WIRELESS<br />&#160; &#160; 无线网络支持.</p><p>&#160; &#160; cfg80211 - wireless configuration API<br />&#160; &#160; CONFIG_CFG80211<br />&#160; &#160; &#160; &#160; cfg80211是Linux无线局域网(802.11)配置接口,是使用WiFi的前提.<br />&#160; &#160; &#160; &#160; 注意:&quot;WiFi&quot;是一个无线网路通信技术的品牌,由WiFi联盟所持有.<br />&#160; &#160; &#160; &#160; 目的是改善基于IEEE 802.11标准的无线网路产品之间的互通性.<br />&#160; &#160; &#160; &#160; 现时一般人会把WiFi及IEEE 802.11混为一谈,甚至把WiFi等同于无线网路<br />&#160; &#160; &#160; &#160; (WiFi只是无线网络的一种).</p><p>&#160; &#160; &#160; &#160; nl80211 testmode command<br />&#160; &#160; &#160; &#160; CONFIG_NL80211_TESTMODE<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试和特殊目的使用.<br />&#160; &#160; &#160; &#160; enable developer warnings<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_DEVELOPER_WARNINGS<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试开发使用<br />&#160; &#160; &#160; &#160; cfg80211 regulatory debugging<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_REG_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试开发使用<br />&#160; &#160; &#160; &#160; cfg80211 certification onus<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_CERTIFICATION_ONUS<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅在你确实明白此项含义的情况下,才考虑选&quot;Y&quot;,否则请选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; enable powersave by default<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_DEFAULT_PS<br />&#160; &#160; &#160; &#160; &#160; &#160; 默认开启省电模式.可能会导致某些设计拙劣的网络程序掉线.建议开启.<br />&#160; &#160; &#160; &#160; &#160; &#160; 详情参见&quot;Documentation/power/pm_qos_interface.txt&quot;文档.<br />&#160; &#160; &#160; &#160; cfg80211 DebugFS entries<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_DEBUGFS<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试<br />&#160; &#160; &#160; &#160; use statically compiled regulatory rules database<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_INTERNAL_REGDB<br />&#160; &#160; &#160; &#160; &#160; &#160; 由于绝大多数发行版都含有CRDA软件包,所以绝大多数人应该选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; 如果你确实需要选&quot;Y&quot;,那么请认真阅读&quot;net/wireless/db.txt&quot;文件.<br />&#160; &#160; &#160; &#160; cfg80211 wireless extensions compatibility<br />&#160; &#160; &#160; &#160; CONFIG_CFG80211_WEXT<br />&#160; &#160; &#160; &#160; &#160; &#160; 为那些老旧的用户空间程序提供兼容性,建议关闭.</p><p>&#160; &#160; lib80211 debugging messages<br />&#160; &#160; CONFIG_LIB80211_DEBUG<br />&#160; &#160; &#160; &#160; 仅供调试<br />&#160; &#160; Generic IEEE 802.11 Networking Stack (mac80211)<br />&#160; &#160; CONFIG_MAC80211<br />&#160; &#160; &#160; &#160; 独立于硬件的通用IEEE 802.11协议栈模块(mac80211).它是驱动开发者用来编写softMAC无线设备驱动的框架,<br />&#160; &#160; &#160; &#160; softMAC设备允许用软件实现帧的管理(包括解析和产生80211无线帧),<br />&#160; &#160; &#160; &#160; 从而让系统能更好的控制硬件,现在大多数的无线网卡都是softMAC设备.<br />&#160; &#160; &#160; &#160; 不确定的选&quot;Y&quot;.<br />&#160; &#160; PID controller based rate control algorithm<br />&#160; &#160; CONFIG_MAC80211_RC_PID<br />&#160; &#160; &#160; &#160; 基于比例-积分-微分控制器(PID controller)的发送速率(TX rate)控制算法.用于CONFIG_MAC80211模块.不确定的选&quot;N&quot;.<br />&#160; &#160; Minstrel<br />&#160; &#160; CONFIG_MAC80211_RC_MINSTREL<br />&#160; &#160; &#160; &#160; minstrel发送速率(TX rate)控制算法.用于CONFIG_MAC80211模块.<br />&#160; &#160; &#160; &#160; 这是首选的算法,不确定的选&quot;Y&quot;.</p><p>&#160; &#160; &#160; &#160; Minstrel 802.11n support<br />&#160; &#160; &#160; &#160; CONFIG_MAC80211_RC_MINSTREL_HT<br />&#160; &#160; &#160; &#160; &#160; &#160; minstrel_ht发送速率(TX rate)控制算法.适用于802.11n规范.不确定的选&quot;Y&quot;.</p><p>&#160; &#160; Default rate control algorithm<br />&#160; &#160; &#160; &#160; 默认发送速率(TX rate)控制算法.相当于mac80211模块&quot;ieee80211_default_rc_algo&quot;参数的值.<br />&#160; &#160; &#160; &#160; 建议选择&quot;Minstrel&quot;算法.<br />&#160; &#160; Enable mac80211 mesh networking (pre-802.11s) support<br />&#160; &#160; CONFIG_MAC80211_MESH<br />&#160; &#160; &#160; &#160; 802.11s草案是无线网状网络(Mesh Networking)的延伸与增补标准(amendment).<br />&#160; &#160; &#160; &#160; 它扩展了IEEE 802.11 MAC(介质访问控制)标准,定义了利用自我组态的多点跳跃拓朴<br />&#160; &#160; &#160; &#160; (multi-hop topologies),进行无线感知(radio-aware metrics),<br />&#160; &#160; &#160; &#160; 以支援广播/组播/单播传送网络封包的架构与协定.不确定的选&quot;N&quot;.<br />&#160; &#160; Enable LED triggers<br />&#160; &#160; CONFIG_MAC80211_LEDS<br />&#160; &#160; &#160; &#160; 允许在接受/发送数据时触发无线网卡的LED灯闪烁.<br />&#160; &#160; Export mac80211 internals in DebugFS<br />&#160; &#160; CONFIG_MAC80211_DEBUGFS<br />&#160; &#160; &#160; &#160; 在DebugFS中显示mac80211模块内部状态的扩展信息,仅用于调试目的.<br />&#160; &#160; Trace all mac80211 debug messages<br />&#160; &#160; CONFIG_MAC80211_MESSAGE_TRACING<br />&#160; &#160; &#160; &#160; 跟踪所有mac80211模块的调试信息,仅用于调试目的.<br />&#160; &#160; Select mac80211 debugging features<br />&#160; &#160; CONFIG_MAC80211_DEBUG_MENU<br />&#160; &#160; &#160; &#160; 仅供调试</p><p>WiMAX Wireless Broadband support<br />CONFIG_WIMAX<br />&#160; &#160; WiMAX(IEEE 802.16)协议支持.随着2010年英特尔放弃WiMAX以及LTE在4G市场成了唯一的主流标准,<br />&#160; &#160; WiMAX的电信运营商也逐渐向LTE转移,WiMAX论坛也于2012年将TD-LTE纳入WiMAX2.1规范,<br />&#160; &#160; 一些WiMAX运营商也开始将设备升级为TD-LTE.</p><p>&#160; &#160; WiMAX debug level<br />&#160; &#160; CONFIG_WIMAX_DEBUG_LEVEL<br />&#160; &#160; &#160; &#160; 设置允许使用的最大调试信息详细等级,推荐使用默认值&quot;8&quot;,<br />&#160; &#160; &#160; &#160; 设为&quot;0&quot;表示允许使用所有调试信息.运行时默认禁止使用调试信息,<br />&#160; &#160; &#160; &#160; 但可通过sysfs文件系统中的debug-levels文件开启调试信息.</p><p>RF switch subsystem support<br />CONFIG_RFKILL<br />&#160; &#160; 为了节约电力,很多无线网卡和蓝牙设备都有内置的射频开关(RF switche)用于开启和关闭设备(通过rfkill命令).<br />&#160; &#160; 建议选&quot;Y&quot;.更多详情参见&quot;Documentation/rfkill.txt&quot;文档</p><p>&#160; &#160; RF switch input support<br />&#160; &#160; CONFIG_RFKILL_INPUT<br />&#160; &#160; &#160; &#160; 这是个反对使用的特性,一般情况下建议关闭.<br />&#160; &#160; &#160; &#160; 但是某些笔记本无线网卡的开关是由按钮控制的,在这些笔记本上建议开启.<br />&#160; &#160; Generic rfkill regulator driver<br />&#160; &#160; CONFIG_RFKILL_REGULATOR<br />&#160; &#160; &#160; &#160; 通用射频开关驱动.这是最通用的驱动,其射频开关连接在电压调节器(voltage regulator)上.<br />&#160; &#160; &#160; &#160; 依赖于CONFIG_REGULATOR框架.<br />&#160; &#160; GPIO RFKILL driver<br />&#160; &#160; CONFIG_RFKILL_GPIO<br />&#160; &#160; &#160; &#160; 通用GPIO射频开关驱动.仅用于嵌入式环境,其射频开关连接在GPIO总线上,<br />&#160; &#160; &#160; &#160; 比如NVIDIA的Tegra和三星的Exynos 4智能手机SoC芯片.</p><p>Plan 9 Resource Sharing Support (9P2000)<br />CONFIG_NET_9P<br />&#160; &#160; 实验性的支持Plan 9的9P2000协议.<br />&#160; &#160;<br />CAIF support<br />CONFIG_CAIF<br />&#160; &#160; 除非你为Android/MeeGo系统编译内核,并且需要使用PF_CAIF类型的socket,否则请选&quot;N&quot;.<br />&#160; &#160;<br />Ceph core library<br />CONFIG_CEPH_LIB<br />&#160; &#160; 仅在你需要使用Ceph分布式文件系统,或者rados块设备(rbd)时选&quot;Y&quot;.否则应选&quot;N&quot;.<br />&#160; &#160;<br />NFC subsystem support<br />CONFIG_NFC<br />&#160; &#160; NFC(近场通信)子系统.这些设备主要用于智能手机之类的嵌入式领域.</p><p>Packet-sampling netlink channel<br />&#160; &#160; 分组采样netlink信道<br />Inter-FE based on IETF ForCES InterFE LFB<br />&#160; &#160; 基于IETF ForCES InterFE LFB的Inter-FE<br />Network light weight tunnels<br />&#160; &#160; 网络轻量级隧道<br />Network physical/parent device Netlink interface<br />&#160; &#160; 网络物理/父设备Netlink接口</p>]]></description>
			<author><![CDATA[dummy@example.com (batsom)]]></author>
			<pubDate>Wed, 03 Aug 2022 14:32:40 +0000</pubDate>
			<guid>http://www.gentoo-zh.org/viewtopic.php?pid=10#p10</guid>
		</item>
	</channel>
</rss>
