[Iscs-developers] ISCS/devel-docs/Functions/ResourceGroupFunctions ResourceGroupFunctions.html,1.13,
Status: Beta
Brought to you by:
jsulliva
Menu
▾
▴
[Iscs-developers] ISCS/devel-docs/Functions/ResourceGroupFunctions ResourceGroupFunctions.html,1.13,1.14
|
From: <jsu...@us...> - 2003-12-27 06:17:20
|
Update of /cvsroot/iscs/ISCS/devel-docs/Functions/ResourceGroupFunctions In directory sc8-pr-cvs1:/tmp/cvs-serv26917/devel-docs/Functions/ResourceGroupFunctions Modified Files: ResourceGroupFunctions.html Log Message: Began work on implementing Range Natting Index: ResourceGroupFunctions.html =================================================================== RCS file: /cvsroot/iscs/ISCS/devel-docs/Functions/ResourceGroupFunctions/ResourceGroupFunctions.html,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -d -r1.13 -r1.14 *** ResourceGroupFunctions.html 25 Dec 2003 05:23:49 -0000 1.13 --- ResourceGroupFunctions.html 27 Dec 2003 06:17:15 -0000 1.14 *************** *** 8,12 **** <META NAME="CREATED" CONTENT="20031003;18292000"> <META NAME="CHANGEDBY" CONTENT="John Sullivan"> ! <META NAME="CHANGED" CONTENT="20031223;21541900"> </HEAD> <BODY LANG="en-US"> --- 8,12 ---- <META NAME="CREATED" CONTENT="20031003;18292000"> <META NAME="CHANGEDBY" CONTENT="John Sullivan"> ! <META NAME="CHANGED" CONTENT="20031227;21500"> </HEAD> <BODY LANG="en-US"> *************** *** 97,104 **** rather than a single IP.</P> <P ALIGN=LEFT STYLE="margin-bottom: 0in; font-weight: medium; text-decoration: none"> ! This is different than NATting a range internally. That is handled ! in the PEP configuration. However, if a Range has been internally NATted, we must use the internally NATted addresses as the addresses ! which are translated and not the Server or Service addresses. This translation requirement may be platform dependent so we should move its functionality to the final translation of the policies into --- 97,104 ---- rather than a single IP.</P> <P ALIGN=LEFT STYLE="margin-bottom: 0in; font-weight: medium; text-decoration: none"> ! This is different than NATting a range internally. That is handled in ! the PEP configuration. However, if a Range has been internally NATted, we must use the internally NATted addresses as the addresses ! which are translated and not the Server or Service addresses. This translation requirement may be platform dependent so we should move its functionality to the final translation of the policies into *************** *** 407,410 **** --- 407,414 ---- must make sure that there are no IP address conflicts with any other servers, PEP's or the SNAT addresses used by the PEPs.</P> + <P ALIGN=LEFT STYLE="margin-bottom: 0in; text-decoration: none">If a + NAT address is chosen which is not on one of the protecting PEP's + public networks, we raise a warning that informs the user that they + must specify an interface.</P> <P ALIGN=LEFT STYLE="margin-bottom: 0in; text-decoration: none">The actualippairs field will need to be calculated from the resources_ip |