comStar Firewall alert - PhaseThrough

Matrix topoloGy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
turn is connected to other nodes, and so on, through to the destination.
These connection processes are hidden to Matrix users;
a persona never “sees” the nodes through which it is routed, nor
is there any possibility to log onto the nodes through which a
connection is routed.
routing
A routing is established every time
data from node A want to access node
B, facilitating other nodes in between
as routers. Due to the mesh-network
nature of the Matrix, every wireless
node can function as a router and will
do so if not in passive or hidden mode
(see PAN modes, p. 211, SR4). Even
peripheral nodes participate in the
mesh network routing, though priority
is given to standard nodes and nexi. A
construct is not aware of the nodes it
is being routed through and cannot access them. However, a
construct can analyze the traffic that is routed through a node
(see Intercept Traffic, p. 224, SR4).
How does a connection know what route it needs to take?
What sequence of nodes it must hop through to reach its destination?
Simply put, the node broadcasts a “routing request”
which is then passed along by all nodes around it, and so on,
leaving backwards pointers at each step along the way, until
actionS HandLed BY
data reQUeStS:
• Audio/video communications
• Database access
• File transfers
• Newsfeeds and updates
• Social networking
• Text/graphic messages
• Website requests
it reaches the target. The destination then follows the route
request trails back, and a connection is established. To help
such routing along, backbone infrastructure nexi maintain
routing databases.
If for any reason a node or group
of nodes is dropped from a network, the
Unwired
remaining available nodes simply route
around the gap, making the network
self-healing.
data requests
In 2070, most of the traffic
through the Matrix is caused by data
requests. People want to read their
favorite website, watch the morning
news, or grab the latest episode of Karl
Kombatmage. AR users want to get the
profile of the person sitting at the bus
station, read the history of an exhibit,
or get the price tag of some item. Nodes want to read pieces
of data out of databases, synchronize timetables with other
nodes, and distribute data. Even phone calls and simsense
broadcasts are packaged into requests.
Nodes send data requests to the Matrix, and other nodes
answer with the needed data package. Most data are protected by
access rights, and requests are only granted if the proper access
rights conditions are met (see Accounts, p. 52).
Simon Wentworth (order #1132857) 9