JudasIscariot: Have you tried messing about with LANs yet? Never could get those missions quite right. I know how to get to the actual LAN but after that I get the attack of the derps :D
I did one LAN mission of the "steal files" sort on an easy LAN and just hacked the bad guys' LAN (the admin kicked me out from the server itself) to see whether the following advice holds. It does.
You need the following:
LAN HUD (obviously) - that's the interface you'll be using most of the time
LAN Scan - shows accessible items on the LAN (everything that's not behind locks)
LAN Probe shows what the item being probed is and what it is connected to
LAN Spoof - needed to connect to items in subnets
Voice Spoof (preferably the v2 so there'd be no risk of accidentally closing the program) - the main server on the LAN is under the voice ID
Connection Analysis HUD
Monitor Bypass
Proxy Bypass
Password Breaker
Decypher (the elliptic-quadratic thing)
and whatever you need for the mission itself.
Do prep work: locate the public access server, phone the admin, arrange a long connection, clean up your memory if you're stealing files, clarify the mission (once you connect to the main server, the admin will log in and disconnect you after a very short time).
Connect to the LAN via a long connection, open Connection Analysis HUD, activate Monitor Bypass and Proxy Bypass. Open the LAN HUD.
The LAN HUD displays items on the network. Neighboring items are connected by blue lines (wired connections) or not at all (wireless, which go from transmitter to receiver). The white dotted line shows your current connection route.
You can extend your connection to the next neighboring item by clicking on it (watch the dotted line - it should extend if the connection was successful), go back one item by clicking back, go back to the beginning by clicking reset and connect to the last item on your route by clicking connect. When you connect, you'll see the item's interface (which may as well be a useless wall of text, depending on the item). To go back to the LAN HUD, click on its icon in the bottom panel.
The obstacles:
Lock: prevents you from connecting further. It is possible to bust it with a LAN Force (and it will probably stay busted once the admin disconnects you, you clean up InterNIC logs and log in again), but this is even less fun than backing up savegame data. To open the lock the proper way, connect to the corresponding autentication server, hack into it and press "disable locks".
Authentication server: opens and closes locks. Protected by a password and an elliptic thingy (password beaker and decypher are necessary). When you click on the server, the lock it controls is highlighted.
Wireless router: connects to another wireless router. Connect to it, then set the frequency to start the wireless conntection. (Hack into nearby terminals to find out the necessary frequency.)
Subnets: protect important LAN components; when you click on an item in teh subnet, the other items are highlighted in yellow. To connect to a protected item (usually an authentication server), connect to and hack into an unprotected component on the same subnet (usually a terminal), open the LAN HUD and use LAN Spoof on the hacked item, then go back and connect to the target item.
Terminal: protected by a password (use password breaker). Some terminals contain useful information which will be shown after hacking into it. If there's none, try another terminal.
Main server: protected by voice ID, password and most importantly admin alert. Before connecting to it, prepare the password breaker, load the necessary file into the audioplayer and refresh your knowledge of the mission goals (delete? shutdown? steal? steal what?).
For completeness' sake: Isolation bridge: one authentication server, two locks, only one of which is open at any given time. Never encountered it.
How-to:
- connect to LAN via a long connection
- open connection HUD, use bypasses
- open LAN HUD
- use LAN Scan
- repeat the following until main server is reached:
-- use LAN Probe on everything (note server/lock pairs and subnets)
-- unlock any accessible locks
-- if wireless, hack into every terminal writing down any frequencies you find
-- if subnet, hack into unprotected teminal, spoof
- prepare hacktools
- connect to main server, do your job
- disconnect or get kicked out
- clean logs on InterNIC
If kicked out, connect again, don't forget bypasses. The LAN will most likely stay hacked, but you'll still need to break the server's internal security. Clean logs after every attempt: certain companies (ahem) trace LAN hacks nearly as fast as the feds trace bank jobs.