update demo docs to match default time change
@@ -27,7 +27,7 @@ Faucet logs will show L2 learned records like the following:
Jul 12 16:00:11 faucet.valve INFO DPID 1 (0x1) switch-1 L2 learned 00:00:00:00:00:02 (L2 type 0x0800, L3 src None, L3 dst None) on Port 2 on VLAN 8 (1 hosts total)
Jul 12 16:00:11 faucet.valve INFO DPID 1 (0x1) switch-1 L2 learned 00:00:00:00:00:01 (L2 type 0x0800, L3 src None, L3 dst None) on Port 1 on VLAN 8 (2 hosts total)
-The Poseidon logs should start picking up the 2 hosts and begin capturing traffic. Once the hosts are moved into the mirroring section of the Poseidon logs you can look at the faucet.yaml file again and see that it got updated to start mirroring traffic. Additionally if you do `docker ps` you still start to see ncapture containers running which are creating the PCAP files of the mirrored traffic. You can find those PCAP files in '/opt/vent_files'. Eventually after the captures have been processed and analyzed by the machine learning portion of Poseidon (about 15 minutes), you'll see results of the machine learning classification in the poseidon logs.
+The Poseidon logs should start picking up the 2 hosts and begin capturing traffic. Once the hosts are moved into the mirroring section of the Poseidon logs you can look at the faucet.yaml file again and see that it got updated to start mirroring traffic. Additionally if you do `docker ps` you still start to see ncapture containers running which are creating the PCAP files of the mirrored traffic. You can find those PCAP files in '/opt/vent_files'. Eventually after the captures have been processed and analyzed by the machine learning portion of Poseidon (about 5 minutes), you'll see results of the machine learning classification in the poseidon logs.
While Poseidon is capturing, you'll want to generate some meaningful traffic. To do this, we'll download a large file from the webserver like so:
