Sets up a related established connection. This can be used with protocols that parse information out of a control connection and then establish a data connection based on information that was exchanged in the control connection, or in SNAT situations where the clientside and serverside flows may have different flow keys.


relate_server {
    proto <ip_proto>
    clientflow <vlan> <local_addr> <local_port> <rmt_addr> <rmt_port>
    serverflow <vlan> <local_addr> <local_port> <rmt_addr> <rmt_port>

relate_server { proto <ip_proto> clientflow <vlan><local_addr> <local_port> <rmt_addr> <rmt_port> serverflow <vlan> <local_addr> <local_port> <rmt_addr> <rmt_port> }

  • Sets up a related established connection.


# Taken from
        # Pre-establish the UDP connection to allow RTP from Server -> Client (and vice versa)
        relate_server {
            proto 17
            clientflow $source_VLAN $destination_RTP $destination_RTP_port $source_inside $source_RTP_port
            serverflow $destination_VLAN $source_outside $source_RTP_port $destination_RTP $destination_RTP_port