Changes between Version 4 and Version 5 of Internal/SharedNAT

Timestamp:

Sep 24, 2014 5:30:26 PM (10 years ago)

Author:

sklower

Comment:

In response to questions and misunderstandings that lawler and bks had.

Internal/SharedNAT

@@ -7 +7 @@
 the previous Risky Experiment mechanism, but gives some additional capabilites.
 
+== Caveats and testing ==
+
+Please note that like the risky experiment facility that it extends, '''you cannot use ping (icmp) to verify that the access is functioning'''.
+
+The system gives specific access with different port sets to TCP and UDP and does not support ICMP at all.
+
 == Dynamic modification/access ==
 
-If you have an an existing experiment, and you want to grant it external    access, you can do so , even if it is already swapped in, without restarting the experiment.
+If you have an an existing experiment, and you want to grant it external access, you can do so , even if it is already swapped in, without restarting the experiment.
 
 You use a web page {{{https://<testbed>/expcxa.php?pid=<pid>&eid=<eid>}}} and fill out the same form that is used by the "Make Experiment Risky" page, parsed with almost the same rules.
@@ -24 +30 @@
 for "Experiment need outside connetctivity" even if you've already
 granted it.
+
+To dynamically '''remove''' access granted either by using the CXA webpage, or as a result of the NS File extensions described
+below, us the CXA webpage again, and delete the entries in the boxes as you would for modifying a risky experiment.
 
 If your experiment already has specified nodes with external
@@ -88 +97 @@
 the HTTP port on the experiment node named "web" and to the daytime UDP port on the experiment host called "othernode".
 
+For any experiment having a tb-allow-external call in the ns file (even with no parameters), a swap-modify will '''overrule''' any changes
+instituted using the dynamic CXA webpage above.
+
 
 == DNS stuff ==