Ticket #581 (closed enhancement: fixed)

Opened 10 years ago

Last modified 10 years ago

Integrate NATLayer with nodemanager

Reported by: kimbrl Owned by: kimbrl
Priority: major Milestone:
Component: node manager Version: 0.1l
Severity: Medium Keywords:
Cc: Blocking:
Blocked By:

Description

This ticket is replacing an outdated ticekt #227

In order to bring nat traversal into the node manager I will:

Move NAT traversal library and its dependencies into seattlelib

update nmmain.py to use the natlayer
update nmclient.repy to use the natlayer
deploy nat forwarders on a distributed set of nodes
add integration tests to ensure that the forwarders remain functional

Change History

Changed 10 years ago by kimbrl

  • status changed from new to accepted

Changed 10 years ago by kimbrl

Added local cache to nat_openconn to improve performance, minor other bug fixes r2562

Forwarder changed to use only one port to ease deployment onto geni nodes r2563

Still need to do further tests and check in changes to nmclient.repy and nmmain.py

Changed 10 years ago by kimbrl

r2581 Corrected bugs in the Multiplexer and forwarder.

r2582 Made changes to nmclient.repy and nmmain.py to add nat traversal to the node manager.

Remaining actions on this ticket are to deploy natforwarders programatically and add integration tests to ensure the remain up and running. NAt forwarders are currently being manually deployed onto geni nodes, so nat traversal should be up and working.

Changed 10 years ago by kimbrl

r2583 Added an integration test to ensure natservers are running and responsive

Changed 10 years ago by kimbrl

r2585, all nmtests will now pass when connected via a forwarder

Changed 10 years ago by kimbrl

  • status changed from accepted to closed
  • resolution set to fixed

This is an old ticket conerning integration with the first generation of Nat Forwarding on the node manager. This has been done for quite awhile, and the second version of Nat Forwarding will be out soon so I am closing this ticket. -Eric Kimbrel

Note: See TracTickets for help on using tickets.