Professional Documents
Culture Documents
Application-level gateway
In the context of computer networking, an application-level gateway[1]
(also known as ALG or application layer gateway) consists of a
security component that augments a firewall or NAT employed in a
computer network. It allows customized NAT traversal filters to be plugged
into the gateway to support address and port translation for certain
application layer "control/data" protocols such as FTP, BitTorrent, SIP,
RTSP, file transfer in IM applications, etc. In order for these protocols to
work through NAT or a firewall, either the application has to know about
an address/port number combination that allows incoming packets, or the
NAT has to monitor the control traffic and open up port mappings
(firewall pinhole) dynamically as required. Legitimate application data can
thus be passed through the security checks of the firewall or NAT that
would have otherwise restricted the traffic for not meeting its limited filter
criteria.
Functions
Deep packet inspection of all the packets handled by ALGs over a given
network makes this functionality possible. An ALG understands the
protocol used by the specific applications that it supports.
For instance, for Session Initiation Protocol (SIP) Back-to-Back User agent
(B2BUA), an ALG can allow firewall traversal with SIP. If the firewall has
its SIP traffic terminated on an ALG then the responsibility for permitting
SIP sessions passes to the ALG instead of the firewall. An ALG can solve
another major SIP headache: NAT traversal. Basically a NAT with a built-
in ALG can rewrite information within the SIP messages and can hold
address bindings until the session terminates. A SIP ALG will also handle
SDP in the body of SIP messages (which is used ubiquitously in VoIP to set
up media endpoints), since SDP also contains literal IP addresses and ports
that must be translated.
An ALG is very similar to a proxy server, as it sits between the client and
real server, facilitating the exchange. There seems to be an industry
convention that an ALG does its job without the application being
configured to use it, by intercepting the messages. A proxy, on the other
hand, usually needs to be configured in the client application. The client is
then explicitly aware of the proxy and connects to it, rather than the real
server.
ALGs in Linux
Amanda protocol
FTP
IRC
TFTP
SIP
See also
References
External links