IPB

Welcome Guest ( Log In | Register )

RunnerPaul
post Dec 13 2006, 09:22 AM
Post #1


Neophyte Runner
*****

Group: Members
Posts: 2,086
Joined: 26-February 02
Member No.: 364



QUOTE (Lord Ben)
A "node" isn't a complete network within a company.

This was said in another thread, but the post was a few days old, and I think the topic can stand by its own.

Node—Any device or network that can be accessed. SR4, p.216

So, by the book, networks can be treated as single nodes. How do you know when to treat a network as a single node, and not a collection of device nodes that are linked together? How do you determine the matrix attributes of a network, especially when it consists of devices of differing ratings?

The core book doesn't say, but I'm hoping it'd be covered in Unwired.

Until then, the house rules that I use are:
  • If a device communicates with the rest of the network via wireless, it counts as a seperate node.
  • If a single account would grant you access to all the devices that are wired together into a network, then the network can be set up to be treated as a single networked node.
  • A device may only be part of one networked node at a time.
  • Devices may be added to or removed from a networked node at any time.
  • The Signal attribute remains treated as per-device.
  • The Firewall attribute of the networked node is equal to the highest Firewall attribute of the devices on the network when the network node is booted up, as long as one device of that Firewall rating or higher remains active on the network. Adding a device with a higher Firewall onto the network will not increase the Firewall rating of the networked node until the networked node is rebooted. If there are no devices on the network that are of the networked node's Firewall rating or higher, the Firewall drops to the Firewall rating of the highest remaining device.
  • The Response attribute of the node is equal to the whatever Response rating the majority of the devices have. In the cases of ties, the higher Response rating wins.
  • The System attribute of the node is also equal to the majority of the devices, however, for the purposes of determining the maximum number of programs running, the sum of all the System ratings of the devices on the network is the maximum.
  • Active subscriptions are still handled per device, using the device's own system rating, and connections to other devices on the network do count against this list.
  • Rebooting a networked node does not cause individual devices to reboot, but it will cause them to perform as individual nodes until the network is rebooted. The networked node may change subscription lists on individual devices as part of the rebooting process, locking certain devices off of the network until the networked node has fully rebooted. Rebooting a networked node requires admin level access.
  • The Crash OS action will only crash a single device on the network. However, this may cause the Matrix attributes of the networked node to fluctuate, or may fragment the network node into smaller nodes if the device crashed is the sole connection between different parts of the network.
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic

 

RSS Lo-Fi Version Time is now: 28th July 2025 - 07:13 AM

Topps, Inc has sole ownership of the names, logo, artwork, marks, photographs, sounds, audio, video and/or any proprietary material used in connection with the game Shadowrun. Topps, Inc has granted permission to the Dumpshock Forums to use such names, logos, artwork, marks and/or any proprietary materials for promotional and informational purposes on its website but does not endorse, and is not affiliated with the Dumpshock Forums in any official capacity whatsoever.