Fix the VBoxManage commands that set up the networks.

diff --git a/README.org b/README.org
index 02a67ea4ee45d03a75a5b282e7674af7f15d91df..821d9fdadd47653c0ffa430e0950eeece904a949 100644 (file)
--- a/README.org
+++ b/README.org
@@ -6793,16 +6793,20 @@ VBoxManage natnetwork add --netname premises \
                           --enable --dhcp on --ipv6 off
 VBoxManage natnetwork start --netname premises
 VBoxManage hostonlyif create # vboxnet0
-VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.56.10 \
-                                       --dhcp off --ipv6 off
+VBoxManage hostonlyif ipconfig vboxnet0 --ip=192.168.56.10
+VBoxManage dhcpserver modify --interface=vboxnet0 --disable
 VBoxManage hostonlyif create # vboxnet1
-VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.57.2 \
-                                       --dhcp off --ipv6 off
+VBoxManage hostonlyif ipconfig vboxnet1 --ip=192.168.57.2
 #+END_SRC
 
 Note that actual ISPs and clouds will provide Gate and Front with
 public network addresses but in this simulation "they" provide
 addresses in the private ~192.168.15.0/24~ network.
+Note that the first host-only network, ~vboxnet0~, gets DHCP service
+by default, but that will interfere with the service being tested on
+~core~, so it must be explicitly disabled.  Only the NAT network
+~premises~ should have a DHCP server enabled.
+
 
 ** The Test Machines