From c233bac5088d70e63b6dea7d12bb52454466ee01 Mon Sep 17 00:00:00 2001 From: Matt Birkholz Date: Fri, 23 Feb 2024 21:23:41 -0700 Subject: [PATCH] Fix the VBoxManage commands that set up the networks. --- README.org | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/README.org b/README.org index 02a67ea..821d9fd 100644 --- 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 -- 2.25.1