Abstract: An accessory system for a pontoon boat includes a support comprising longitudinal members and at least one support crosspiece connected between the longitudinal members, where the support can be attached to a structural component of a pontoon boat and move between a stowed position and a deployed position. An accessory component includes one or more hangers with a hook constructed to engage the support. A support portion is connected to the accessory component and extends transversely away from the one or more hangers. In use, the support can be deployed along a side of a pontoon with the accessory component removably attached to the support. The accessory component can be used to support a platform, a grill, a cooler or other accessory alongside the pontoon boat.

Abstract: An accessory system for a pontoon boat includes a support comprising longitudinal members and at least one support crosspiece connected between the longitudinal members, where the support can be attached to a structural component of a pontoon boat and move between a stowed position and a deployed position. An accessory component includes one or more hangers with a hook constructed to engage the support. A support portion is connected to the accessory component and extends transversely away from the one or more hangers. In use, the support can be deployed along a side of a pontoon with the accessory component removably attached to the support. The accessory component can be used to support a platform, a grill, a cooler or other accessory alongside the pontoon boat.

Abstract: An accessory system for a pontoon boat includes a support comprising longitudinal members and at least one support crosspiece connected between the longitudinal members, where the support can be attached to a structural component of a pontoon boat and move between a stowed position and a deployed position. An accessory component includes one or more hangers with a hook constructed to engage the support. A support portion is connected to the accessory component and extends transversely away from the one or more hangers. In use, the support can be deployed along a side of a pontoon with the accessory component removably attached to the support. The accessory component can be used to support a platform, a grill, a cooler or other accessory alongside the pontoon boat.

Abstract: An accessory system for a pontoon boat includes a support comprising longitudinal members and at least one support crosspiece connected between the longitudinal members, where the support can be attached to a structural component of a pontoon boat and move between a stowed position and a deployed position. An accessory component includes one or more hangers with a hook constructed to engage the support. A support portion is connected to the accessory component and extends transversely away from the one or more hangers. In use, the support can be deployed along a side of a pontoon with the accessory component removably attached to the support. The accessory component can be used to support a platform, a grill, a cooler or other accessory alongside the pontoon boat.

Abstract: A technique for synchronizing NAT information stored on different network devices. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device causing that device to modify its respective NAT data structure using information from the first NAT transaction message. In this way, synchronization of NAT information stored on each of the network devices may be achieved.

Abstract: A technique for synchronizing NAT information stored on different network devices. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device causing that device to modify its respective NAT data structure using information from the first NAT transaction message. In this way, synchronization of NAT information stored on each of the network devices may be achieved.

Abstract: A technique is disclosed for synchronizing NAT information stored on different network devices that have been configured to implement a network address translation protocol. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device to thereby cause that device to modify its respective NAT data structure using information from the first NAT transaction message.

Abstract: A technique is disclosed for synchronizing NAT information stored on different network devices that have been configured to implement a network address translation protocol. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device to thereby cause that device to modify its respective NAT data structure using information from the first NAT transaction message.

Abstract: A technique is disclosed for synchronizing NAT information stored on different network devices that have been configured to implement a network address translation protocol. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device to thereby cause that device to modify its respective NAT data structure using information from the first NAT transaction message.

Abstract: Methods and apparatus for initiating the release of an IP address allocated for use by a Mobile Node supporting Mobile IP are disclosed. The IP address may be a collocated care-of address or a dynamically assigned home address. The release of the IP address may be initiated by the Home Agent based upon information it has received in a registration request or, alternatively, may be initiated by the Home Agent in response to a de-registration request. In this manner, a Home Agent may initiate the release of an IP address that is no longer in use by a Mobile Node.

Abstract: Methods and apparatus for initiating the release of an IP address allocated for use by a Mobile Node supporting Mobile IP are disclosed. The IP address may be a collocated care-of address or a dynamically assigned home address. The release of the IP address may be initiated by the Home Agent based upon information it has received in a registration request or, alternatively, may be initiated by the Home Agent in response to a de-registration request. In this manner, a Home Agent may initiate the release of an IP address that is no longer in use by a Mobile Node.

Abstract: A technique is disclosed for synchronizing NAT information stored on different network devices that have been configured to implement a network address translation protocol. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device to thereby cause that device to modify its respective NAT data structure using information from the first NAT transaction message.

Abstract: A technique is disclosed for synchronizing NAT information stored on different network devices that have been configured to implement a network address translation protocol. Each of the network devices includes a respective NAT data structure configured to store NAT information. The NAT information includes at least one NAT entry relating to a network node engaged in a communication session with at least one other network node. At least one NAT entry in a first NAT data structure is modified. The first NAT data structure is associated with a first NAT network device. A first NAT transaction message is generated which includes information relating to the modifications performed on the first NAT data structure. The first NAT transaction message is transmitted to at least one other NAT network device to thereby cause that device to modify its respective NAT data structure using information from the first NAT transaction message.

Abstract: The distribution of traffic flows in a load-sharing redundancy group that includes a first gateway device and a second gateway device includes assigning a first set of forwarding addresses to the first gateway device and a second set of forwarding addresses to the second gateway device. The redundancy group distributes forwarding addresses to hosts which in turn use the distributed forwarding addresses to send packets to the redundancy group. The traffic flow for each of the assigned forwarding addresses is measured and may be compared to a target traffic flow. The traffic flow is adjusted to close in on the target traffic flow. Adjustment of the traffic flow can be accomplished either by changing the existing measured traffic flow by re-assigning a forwarding address originally assigned to one gateway device to a different gateway device or by altering future distribution of forwarding addresses so that additional traffic is sent to one or more forwarding addresses having lower measured traffic.

Abstract: A new directory service is established for a peer router receiving a data packet from an end station on a local area network connected to a port of the peer router, the peer router hereinafter being referred to as the source router. The data packet is addressed to a destination address. The source router determines that the data packet is to be encapsulated as an encapsulated packet, and the encapsulated packet routed by a peer-to-peer protocol to a destination router. The destination router then transmits the packet onto a local area network to the destination address. The source router locates the proper peer destination router by use of a database. The database is maintained on a server, where the database has entries for destination address, and an entry for a particular destination address gives the address of a peer router capable of routing a packet to that particular destination address.

Abstract: A complete management system for specialized routers such as, for example, DLSw routers is provided. The management system uses a server to maintain a DLSw Directory, for example an LDAP directory. Whenever a DLSw router is booted, the DLSw router sends a registration message to the Server giving the network address of the DLSw router. The Server then maintains a directory of all DLSw routers in the network (the DLSw Directory). The information maintained in the DLSw Directory has the network address of each DLSw router, as received when the router is booted up. Also, at later times, the DLSw router sends a message to the DLSw Directory giving further information about the DLSw router. The further information comprises data such as: the types of encapsulation being received and routed by the router, etc.

Abstract: A new directory service is established for a peer router receiving a data packet from an end station on a local area network connected to a port of the peer router, the peer router hereinafter being referred to as the source router. The data packet is addressed to a destination address. The source router determines that the data packet is to be encapsulated as an encapsulated packet, and the encapsulated packet routed by a peer-to-peer protocol to a destination router. The destination router then transmits the packet onto a local area network to the destination address. The source router locates the proper peer destination router by use of a database. The database is maintained on a server, where the database has entries for destination address, and an entry for a particular destination address gives the address of a peer router capable of routing a packet to that particular destination address.