summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/sync/alarm/node1/conntrackd.conf9
-rw-r--r--doc/sync/alarm/node2/conntrackd.conf9
-rw-r--r--doc/sync/ftfw/node1/conntrackd.conf9
-rw-r--r--doc/sync/ftfw/node2/conntrackd.conf9
-rw-r--r--doc/sync/notrack/node1/conntrackd.conf9
-rw-r--r--doc/sync/notrack/node2/conntrackd.conf9
6 files changed, 0 insertions, 54 deletions
diff --git a/doc/sync/alarm/node1/conntrackd.conf b/doc/sync/alarm/node1/conntrackd.conf
index c3c4da4..ff86918 100644
--- a/doc/sync/alarm/node1/conntrackd.conf
+++ b/doc/sync/alarm/node1/conntrackd.conf
@@ -66,15 +66,6 @@ Sync {
# Enable/Disable message checksumming
Checksum on
- # Uncomment this if you want to replicate just certain TCP states.
- # This option introduces a tradeoff in the replication: it reduces
- # CPU consumption and lost messages rate at the cost of having
- # backup replicas that don't contain the current state that the active
- # replica holds. TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
- # FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSE, LISTEN.
- #
- # Replicate ESTABLISHED TIME_WAIT for TCP
-
# If you have a multiprimary setup (active-active) without connection
# persistency, ie. you can't know which firewall handles a packet
# that is part of a connection, then you need direct commit of
diff --git a/doc/sync/alarm/node2/conntrackd.conf b/doc/sync/alarm/node2/conntrackd.conf
index e61e76a..ab34f70 100644
--- a/doc/sync/alarm/node2/conntrackd.conf
+++ b/doc/sync/alarm/node2/conntrackd.conf
@@ -66,15 +66,6 @@ Sync {
# Enable/Disable message checksumming
Checksum on
- # Uncomment this if you want to replicate just certain TCP states.
- # This option introduces a tradeoff in the replication: it reduces
- # CPU consumption and lost messages rate at the cost of having
- # backup replicas that don't contain the current state that the active
- # replica holds. TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
- # FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSE, LISTEN.
- #
- # Replicate ESTABLISHED TIME_WAIT for TCP
-
# If you have a multiprimary setup (active-active) without connection
# persistency, ie. you can't know which firewall handles a packet
# that is part of a connection, then you need direct commit of
diff --git a/doc/sync/ftfw/node1/conntrackd.conf b/doc/sync/ftfw/node1/conntrackd.conf
index 98ad581..e256f67 100644
--- a/doc/sync/ftfw/node1/conntrackd.conf
+++ b/doc/sync/ftfw/node1/conntrackd.conf
@@ -61,15 +61,6 @@ Sync {
# Enable/Disable message checksumming
Checksum on
- # Uncomment this if you want to replicate just certain TCP states.
- # This option introduces a tradeoff in the replication: it reduces
- # CPU consumption and lost messages rate at the cost of having
- # backup replicas that don't contain the current state that the active
- # replica holds. TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
- # FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSE, LISTEN.
- #
- # Replicate ESTABLISHED TIME_WAIT for TCP
-
# If you have a multiprimary setup (active-active) without connection
# persistency, ie. you can't know which firewall handles a packet
# that is part of a connection, then you need direct commit of
diff --git a/doc/sync/ftfw/node2/conntrackd.conf b/doc/sync/ftfw/node2/conntrackd.conf
index 2fab830..b22ab06 100644
--- a/doc/sync/ftfw/node2/conntrackd.conf
+++ b/doc/sync/ftfw/node2/conntrackd.conf
@@ -60,15 +60,6 @@ Sync {
# Enable/Disable message checksumming
Checksum on
- # Uncomment this if you want to replicate just certain TCP states.
- # This option introduces a tradeoff in the replication: it reduces
- # CPU consumption and lost messages rate at the cost of having
- # backup replicas that don't contain the current state that the active
- # replica holds. TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
- # FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSE, LISTEN.
- #
- # Replicate ESTABLISHED TIME_WAIT for TCP
-
# If you have a multiprimary setup (active-active) without connection
# persistency, ie. you can't know which firewall handles a packet
# that is part of a connection, then you need direct commit of
diff --git a/doc/sync/notrack/node1/conntrackd.conf b/doc/sync/notrack/node1/conntrackd.conf
index 724183a..6c5ec3d 100644
--- a/doc/sync/notrack/node1/conntrackd.conf
+++ b/doc/sync/notrack/node1/conntrackd.conf
@@ -54,15 +54,6 @@ Sync {
# Enable/Disable message checksumming
Checksum on
- # Uncomment this if you want to replicate just certain TCP states.
- # This option introduces a tradeoff in the replication: it reduces
- # CPU consumption and lost messages rate at the cost of having
- # backup replicas that don't contain the current state that the active
- # replica holds. TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
- # FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSE, LISTEN.
- #
- # Replicate ESTABLISHED TIME_WAIT for TCP
-
# If you have a multiprimary setup (active-active) without connection
# persistency, ie. you can't know which firewall handles a packet
# that is part of a connection, then you need direct commit of
diff --git a/doc/sync/notrack/node2/conntrackd.conf b/doc/sync/notrack/node2/conntrackd.conf
index cbf5cee..ba83e5a 100644
--- a/doc/sync/notrack/node2/conntrackd.conf
+++ b/doc/sync/notrack/node2/conntrackd.conf
@@ -53,15 +53,6 @@ Sync {
# Enable/Disable message checksumming
Checksum on
- # Uncomment this if you want to replicate just certain TCP states.
- # This option introduces a tradeoff in the replication: it reduces
- # CPU consumption and lost messages rate at the cost of having
- # backup replicas that don't contain the current state that the active
- # replica holds. TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
- # FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSE, LISTEN.
- #
- # Replicate ESTABLISHED TIME_WAIT for TCP
-
# If you have a multiprimary setup (active-active) without connection
# persistency, ie. you can't know which firewall handles a packet
# that is part of a connection, then you need direct commit of