Lines Matching refs:the
6 It sets the always mode drop rate, which is used in the mode 3
7 of the drop_rate defense.
12 It sets the available memory threshold (in pages), which is
13 used in the automatic modes of defense. When there is no
14 enough available memory, the respective strategy will be
15 enabled and the variable is automatically set to 2, otherwise
16 the strategy is disabled and the variable is set to 1.
22 If set, disable the director function while the server is
29 port reuse. It is a bitmap, with the values being:
32 connection will be delivered to the same real server that was
33 servicing the previous connection. This will effectively
38 the connection is in TIME_WAIT state (which is only possible if
42 are in FIN_WAIT state, as this is the last state seen by load
58 Connections handled by the IPVS FTP application module
67 If it is enabled, forward packets to the original destination
89 Higher debugging levels include the messages for lower debugging
91 messages. Thus, logging becomes more and more verbose the higher
92 the level.
97 The drop_entry defense is to randomly drop entries in the
99 memory for new connections. In the current code, the
101 randomly scans 1/32 of the whole and drops entries that are in
102 the SYN-RECV/SYNACK state, which should be effective against
107 modes (when there is no enough available memory, the strategy
108 is enabled and the variable is automatically set to 2,
109 otherwise the strategy is disabled and the variable is set to
110 1), and 3 means that that the strategy is always enabled.
116 before forwarding them to real servers. If the rate is 1, then
117 drop all the incoming packets.
119 The value definition is the same as that of the drop_entry. In
120 the automatic mode, the rate is determined by the follow
122 when available memory is less than the available memory
123 threshold. When the mode 3 is set, the always mode drop rate
124 is controlled by the /proc/sys/net/ipv4/vs/am_droprate.
130 The default value is 0, the load balancer will silently drop
132 be useful, when user-space monitoring program deletes the
134 detection) and add back the server later, and the connections
135 to the server can continue.
137 If this feature is enabled, the load balancer will expire the
139 destination server is not available, then the client program
140 will be notified that the connection is closed. This is
141 equivalent to the feature some people requires to flush
148 When set to a non-zero value, the load balancer will expire
149 persistent templates when the destination server is quiescent.
156 If this feature is enabled, the load balancer will expire the
158 connection and the destination server is quiescent.
164 If set, ipvs will set the ipvs_property on all packets which are of
167 packets that have been tunneled to the ipvs host (i.e. to prevent
175 for VS/NAT when the load balancer receives packets from real
176 servers but the connection entries don't exist.
182 transition table. For VS/NAT, it also delays entering the
183 TCP ESTABLISHED state until the three way handshake is completed.
185 The value definition is the same as that of drop_entry and
191 It sets synchronization threshold, which is the minimum number
193 the connection will be synchronized. A connection will be
194 synchronized, every time the number of its incoming packets
195 modulus 50 equals the threshold. The range of the threshold is
202 If enabled, recalculate the route of SNATed packets from
203 realservers so that they are routed as if they originate from the
204 director. Otherwise they are routed as if they are forwarded by the
207 If policy routing is in effect then it is possible that the route
209 packet being forwarded by the director.
211 If policy routing is not in effect then the recalculated route will
212 always be the same as the original route so it is an optimisation
213 to disable snat_reroute and avoid the recalculation.
218 Controls the synchronisation of connections when using persistence
221 1: Attempt to reduce the synchronisation traffic depending on
222 the connection type. For persistent services avoid synchronisation
231 The version of the synchronisation protocol used when sending
234 0 selects the original synchronisation protocol (version 0). This
236 system that only understands the original synchronisation protocol.
238 1 selects the current synchronisation protocol (version 1). This
242 of both version 1 and version 2 of the synchronisation protocol.