Manual Pages  — NG_NAT

• SYNOPSIS
• DESCRIPTION
• HOOKS
• CONTROL MESSAGES
• SHUTDOWN
• EXAMPLES
• SEE ALSO
• HISTORY
• AUTHORS

struct ng_nat_mode {
        uint32_t        flags;
        uint32_t        mask;
};
/* Supported flags: */
#define NG_NAT_LOG                      0x01
#define NG_NAT_DENY_INCOMING            0x02
#define NG_NAT_SAME_PORTS               0x04
#define NG_NAT_UNREGISTERED_ONLY        0x10
#define NG_NAT_RESET_ON_ADDR_CHANGE     0x20
#define NG_NAT_PROXY_ONLY               0x40
#define NG_NAT_REVERSE                  0x80
#define NG_NAT_UNREGISTERED_CGN         0x100

The corresponding libalias flags can be found by replacing the NG_NAT prefix with PKT_ALIAS.

#define NG_NAT_DESC_LENGTH      64
struct ng_nat_redirect_port {
        struct in_addr  local_addr;
        struct in_addr  alias_addr;
        struct in_addr  remote_addr;
        uint16_t        local_port;
        uint16_t        alias_port;
        uint16_t        remote_port;
        uint8_t         proto;
        char            description[NG_NAT_DESC_LENGTH];
};

Redirection is assigned an unique ID which is returned as response to this message, and information about redirection added to list of static redirects which later can be retrieved by NGM_NAT_LIST_REDIRECTS message.

struct ng_nat_redirect_addr {
        struct in_addr  local_addr;
        struct in_addr  alias_addr;
        char            description[NG_NAT_DESC_LENGTH];
};

Unique ID for this redirection is returned as response to this message.

struct ng_nat_redirect_proto {
        struct in_addr  local_addr;
        struct in_addr  alias_addr;
        struct in_addr  remote_addr;
        uint8_t         proto;
        char            description[NG_NAT_DESC_LENGTH];
};

Unique ID for this redirection is returned as response to this message.

struct ng_nat_add_server {
        uint32_t        id;
        struct in_addr  addr;
        uint16_t        port;
};

First, the redirection is set up by NGM_NAT_REDIRECT_PORT or NGM_NAT_REDIRECT_ADDR. Then, ID of that redirection is used in multiple NGM_NAT_ADD_SERVER messages to add necessary number of servers. For redirections created by NGM_NAT_REDIRECT_ADDR, the port is ignored and could have any value. Original redirection's parameters local_addr and local_port are also ignored after NGM_NAT_ADD_SERVER was used (they are effectively replaced by server pool).

struct ng_nat_listrdrs_entry {
        uint32_t        id;             /* Anything except zero */
        struct in_addr  local_addr;
        struct in_addr  alias_addr;
        struct in_addr  remote_addr;
        uint16_t        local_port;
        uint16_t        alias_port;
        uint16_t        remote_port;
        uint16_t        proto;          /* Valid proto or NG_NAT_REDIRPROTO_ADDR */
        uint16_t        lsnat;          /* LSNAT servers count */
        char            description[NG_NAT_DESC_LENGTH];
};
struct ng_nat_list_redirects {
        uint32_t                total_count;
        struct ng_nat_listrdrs_entry redirects[];
};
#define NG_NAT_REDIRPROTO_ADDR  (IPPROTO_MAX + 3)

Entries of the redirects array returned in the unified format for all redirect types. Ports are meaningful only if protocol is either TCP or UDP and static NAT redirection (created by NGM_NAT_REDIRECT_ADDR) is indicated by proto set to NG_NAT_REDIRPROTO_ADDR. If lsnat servers counter is greater than zero, then local_addr and local_port are also meaningless.

struct ng_nat_libalias_info {
        uint32_t        icmpLinkCount;
        uint32_t        udpLinkCount;
        uint32_t        tcpLinkCount;
        uint32_t        sctpLinkCount;
        uint32_t        pptpLinkCount;
        uint32_t        protoLinkCount;
        uint32_t        fragmentIdLinkCount;
        uint32_t        fragmentPtrLinkCount;
        uint32_t        sockCount;
};