About: Application-level gateway is a research topic. Over the lifetime, 64 publications have been published within this topic receiving 1033 citations. The topic is also known as: Application Layer Gateway & bn¨sdbnag.
TL;DR: In this paper, a preferred Application Level Gateway is provided for firewall and NAT implementations to enhance network security, provided the gateway received the data packet at an input port exceeding 1023, and at least one internal network component of the area network indicates willingness to receive the packet.
Abstract: For an Internet Access Gateway operative between an area network and a public network, managing dynamic network sessions therebetween whereby a primary server on the public network in a primary session with a client of the area network initiates an additional session with an additional server on the public network, for which an unexpected data packet received at the gateway from the additional server is associated with the primary session, and accordingly allowed access to the area network through the gateway, provided the gateway received the data packet at an input port exceeding 1023, the additional session comprises a pre-defined Session Triggering Event, and at least one internal network component of the area network indicates willingness to receive the data packet. Wherefore, a preferred Application Level Gateway is thereby provided for firewall and NAT implementations to enhance network security.
Abstract: A structure for coupling together addressably disparate nodes, such as IPv4 nodes and IPv6 nodes, without the use of an application level gateway. Instead, the system includes two executable applications, HEART and ECHO, that avoid the necessity of an application level gateway. In general, HEART and ECHO cooperate with each other through a network address translator-protocol translator (NAT-PT) to cause the NAT-PT to temporarily assign an IPv4 address to a control session between the IPv4 and IPv6 nodes and also prevent the control session from timing out due to lack of timely communications between the IPv4 and IPv6 nodes.
TL;DR: In this article, the authors present mechanisms for facilitating FTP sessions between devices utilizing different protocols, such as IPv4 and IPv6, by translating control packets between two different protocol devices when required, e.g., from an IPv6 to an IPv4 format or visa versa.
Abstract: Disclosed are methods and apparatus for handling FTP (file transfer protocol) control packets. In general terms, mechanisms are provided for facilitating FTP sessions between devices utilizing different protocols, such as IPv4 and IPv6. For example, FTP control packets from an IPv6 client to an IPv4 server are handled to facilitate such communication. Likewise, FTP control packets from an IPv4 client to an IPv6 server are handled to facilitate such communication. Communication is also facilitated when either or both of the client or server is in the form of a dual-stack device. To facilitate FTP session between devices having different protocols, FTP control packets between two different protocol devices are translated from one protocol to another protocol when required, e.g., from an IPv6 to an IPv4 format or visa versa.
TL;DR: The architecture of a Jini-based Application Level Gateway (ALGW) which avoids manual reconfiguration of a mobile device every time the user changes the host network is presented.
Abstract: In the near future we expect a widespread deployment of mobile computational resources including network-enabled end devices like Laptops and PDAs. An interesting problem then and today is the transparent change of locality. Traditionally several manual actions are necessary to reconfigure the device and to rebind client-applications to services available in the host network. This paper presents the architecture of a Jini-based Application Level Gateway (ALGW) which avoids manual reconfiguration of a mobile device every time the user changes the host network. To do so, the ALGW makes use of key technologies provided by Jini. Jini is used for dynamic looking up and binding to services needed by the user and located in the host network. Moreover, Jini can be used for value-added services like our authenticating SMTP-Service.
TL;DR: In this paper, the authors present a method and apparatus for validating application level gateway (ALG) files or firewall rulsets or firewall rulesets (200) using a bi-directional communications device.
Abstract: Method (300) and apparatus (100) for validating application level gateway (ALG) files or firewall rulsets (200). The method and apparatus include receiving (304), at a bi-directional communications device (130), an application level gateway (ALG) file (200), and comparing (308, 310, 314, 320, 326, 332, 336) at least one compatibility parameter of said ALG file with features of said bi-directional communications device. In an instance where all of the compatibility parameters compare favorably, the ALG file is stored (340) at the bi-directional communications device.