[
https://issues.apache.org/jira/browse/VCL-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149662#comment-14149662
]
Josh Thompson commented on VCL-174:
-----------------------------------
Andy and I discussed this yesterday. We realized it would be good to be able to
have various nodes act as the NAT host and also that it would be useful to be
able to enable/disable NAT on a per computer basis. We came up with the
following plan.
Create a nathost table:
id
resourceid
natIP - IP on NAT node to which users will be connecting
Create a natmap table:
computerid
nathostid
Change the name of the 'nat' table from this patch to 'natports' and alter the
structure a little:
reservationid (instead of computerid)
publicport
connectmethodportid
Split out the ports from the connectmethod table into a new table named
connectmethodport (part of VCL-706, affects natport table structure, so we
dicided to go ahead with this part):
id
connectmethodid
port
protocol
The natports table gets dynamically updated at start/end of reservations. The
manage computers page is used to enable/disable NAT for a node and to set the
NAT host.
For this release, the nathost table will directly correspond to entries in the
management node table. In the next release, a section will be added to the site
for managing NAT hosts and will allow any computer or management node to act as
a NAT host.
Comments/suggestions welcome.
> NAT - support for sites that have small IP address ranges
> ---------------------------------------------------------
>
> Key: VCL-174
> URL: https://issues.apache.org/jira/browse/VCL-174
> Project: VCL
> Issue Type: New Feature
> Components: database, vcld (backend), web gui (frontend)
> Reporter: Aaron Peeler
> Priority: Minor
> Fix For: 2.4
>
> Attachments: vcl_nat_patch.diff
>
>
> Add the support for Network Address Translation so smaller sites can provide
> many resources with a small number of IP addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
