aboutsummaryrefslogtreecommitdiffstats
path: root/src/23/part2
diff options
context:
space:
mode:
authorLouis Burda <quent.burda@gmail.com>2023-04-07 17:18:18 -0400
committerLouis Burda <quent.burda@gmail.com>2023-04-07 17:19:39 -0400
commit87ab487d59fa85dbe2afa55cc841b02805ae42ca (patch)
treecd90ab715e1b5b5803674045dbafd6d51d27ac90 /src/23/part2
parent1bcc82c5bfbde87edd03c01ffdf9ee5934681592 (diff)
downloadaoc2018-python-87ab487d59fa85dbe2afa55cc841b02805ae42ca.tar.gz
aoc2018-python-87ab487d59fa85dbe2afa55cc841b02805ae42ca.zip
Reorder days into src
Diffstat (limited to 'src/23/part2')
-rw-r--r--src/23/part222
1 files changed, 22 insertions, 0 deletions
diff --git a/src/23/part2 b/src/23/part2
new file mode 100644
index 0000000..f0f8db0
--- /dev/null
+++ b/src/23/part2
@@ -0,0 +1,22 @@
+--- Part Two ---
+
+Packets sent to address 255 are handled by a device called a NAT (Not Always Transmitting). The NAT
+is responsible for managing power consumption of the network by blocking certain packets and
+watching for idle periods in the computers.
+
+If a packet would be sent to address 255, the NAT receives it instead. The NAT remembers only the
+last packet it receives; that is, the data in each packet it receives overwrites the NAT's packet
+memory with the new packet's X and Y values.
+
+The NAT also monitors all computers on the network. If all computers have empty incoming packet
+queues and are continuously trying to receive packets without sending packets, the network is
+considered idle.
+
+Once the network is idle, the NAT sends only the last packet it received to address 0; this will
+cause the computers on the network to resume activity. In this way, the NAT can throttle power
+consumption of the network when the ship needs power in other areas.
+
+Monitor packets released to the computer at address 0 by the NAT. What is the first Y value
+delivered by the NAT to the computer at address 0 twice in a row?
+
+