updates to NOTEs in documentation

This commit is contained in:
Blake Harnden 2020-04-09 21:33:20 -07:00
parent 0d490344fc
commit 36b3243a4b
6 changed files with 19 additions and 19 deletions

View file

@ -30,11 +30,11 @@ new sessions will use by default. To simultaneously run multiple sessions with
control networks, the session option should be used instead of the *core.conf*
default.
> :warning: If you have a large scenario with more than 253 nodes, use a control
> **NOTE:** If you have a large scenario with more than 253 nodes, use a control
network prefix that allows more than the suggested */24*, such as */23* or
greater.
> :warning: Running a session with a control network can fail if a previous
> **NOTE:** Running a session with a control network can fail if a previous
session has set up a control network and the its bridge is still up. Close
the previous session first or wait for it to complete. If unable to, the
*core-daemon* may need to be restarted and the lingering bridge(s) removed
@ -52,7 +52,7 @@ for cb in $ctrlbridges; do
done
```
> :bulb: If adjustments to the primary control network configuration made in
> **NOTE:** If adjustments to the primary control network configuration made in
*/etc/core/core.conf* do not seem to take affect, check if there is anything
set in the *Session Menu*, the *Options...* dialog. They may need to be
cleared. These per session settings override the defaults in
@ -120,7 +120,7 @@ assign *ctrl1* to the OTA manager device and *ctrl2* to the Event Service
device in the EMANE Options dialog box and leave *ctrl0* for CORE control
traffic.
> :warning: *controlnet0* may be used in place of *controlnet* to configure
> **NOTE:** *controlnet0* may be used in place of *controlnet* to configure
>the primary control network.
Unlike the primary control network, the auxiliary control networks will not
@ -139,7 +139,7 @@ controlnetif2 = eth2
controlnetif3 = eth3
```
> :warning: There is no need to assign an interface to the primary control
> **NOTE:** There is no need to assign an interface to the primary control
>network because tunnels are formed between the master and the slaves using IP
>addresses that are provided in *servers.conf*.