Sent, how many nodes and what kind of time frame are we looking at to be able to hack the nodes that route data to the trix that weren't affected by the emp blast. Other than the one I'm accessing I wanted to put them on a continuous reboot. The one I'm accessing, I want block all comms except ours or mine (whichever is faster to implement)
Assuming you want to hack grid nodes nearby you'll need to find one for this district - simple action, analyze disctrict node (1hit necessary, on autobuy) to find grid node (not hidden, public access)
matrix perception another simple action (if not actively looking) to identify the stats at least
from earlier experince you expect something along the lines of Firewall 4, System 4.
They should not be activelly patrolled by security spiders, but might scramble IC on identified intrusion attempts.
continous reboot would require at least security access level to edit the starting routine.
if you go for admin, then it is a simple reboot action -> System + Response (10, 1 Combat Turn) Extended Test
or you can then crash the node from security action -> Hacking + Exploit (System + Firewall, Complex Action) Extended Test. Keep in mind that the latter will initiate alert and scramble IC.
if you don't care about leaving traces in the access log, hacking is doable within one CT probably rebooting within another 3CT..
single crash is enough to put this distrcit in grid chaos. and it will take a visit by physical repair team to restore order, unless they wake a security spider to log in and repair things in between reboots.
