LAN - PC版Bloodbowl私家版@ ウィキ

LAN

---

LANへの接続の仕方

必須：

HUD_Connection_Analysis
Bypath_Monitor Ver5.0
Bypath_Proxy Ver5.0
Bypath_Firewall Ver5.0

HUD_LAN_Viewer 50000c
LAN_SCAN Ver3.0
LAN_Probe Ver3.0
LAN_Spoof Ver3.0

Breake_password Ver1.0
Voice_Analaysis Ver1.0
Encypehr Ver3.0

それ相応のChain構成後、LANへ接続

Lan_Scan実行　表層の機器が見える。
Lan_probeで、空白の解析
表層から外せるLockをLan_Spoofで外す
再度、Lan_Probeで解析できる箇所がないか見極める。

LANの構成に応じて、Terminal、AutheticationPC、VaildPCを
Hacking

場合に応じて、Terminalからの再侵入をしつつセキュリティーを解除して
MainServerまで辿り着く。

MainSereverで仕事して終了。

---

LAN_SpoofとLAN_Force

LAN_SpoofとLAN_Forceをどちらを買うべきか
と問われれば迷わず、Spoofです。
気づかれてもなんとかなるは、LAN上では通用しません。
SysAdminが気づいた場合、追跡完了よりも強制切断に
なり、にっちもさっちもいきません。どんなにChain
しようとも、LAN上では、70sec程度で追跡が完了
する場合が多く、作業できる時間はわずか２０秒程度
このことから、気づかれないというのが非常に
重要になってきます。

LANConnect　FAQ

LANのRouter自体に繋いだ時点では、Traceされない。
Probeを打ち込んだだけでも、気づかれない。
一度Probeで探知したネットワーク機器は既知となる。
Smaple　LocalAreaNetwork　127.432.543.123
LAN_SpoofとLAN_Force

---

参考：

Lan Hacking Guide

1. Have LAN_Scan, LAN_Probe, and LAN_Spoof. Also required (these should be obvious, but I'll list just in case), are The highest versions of Password_Breaker (for terminals and pretty much everything else), Decypher (For Elliptic-Curve on Authentication Comps, and I belive Isolation Bridges), Monitor/Proxy Bypass to keep the admin off your butt while you are hacking everything except the main server, IP_Lookup for any modem numbers you run accrss, and have the Administrators voice-print ready for playback on your voice-analyzer if you plan on hitting the Main server.

2. After Logging in to the LAN (the bounce right before the LAN should be a "trusted" connection, basically one that is the same company as the LAN), run your LAN_Scan program adn click the scan button on teh program to Scan as many Devices as you can.

3. After Scanning, go through and LAN_Probe every device you see, or every black box with white outline. Start with the ones closest to your connection and move outward.

4. Now is a good time to slap on your Monitor and Proxy bypasses, just in case.

5. Connect step by step to each device. For example, click on the hub, hit connect, click on the terminal, hit connect. THere may be a faster way, this is just the way I do it.

6. Hubs/Routers/Switches - Look like boxes with a bunch of light sand buttons on them, no security just connections.

7. Terminals - Look lik elittle computers, Password-Required Security. Make sure to note any Radio frequencies or Modem Numbers on any Terminals you hack, be sure to write them down.

8. Locks - Look like small blue diamonds with a Padlock icon on them. By default they are enabled, so they well block LAN_Probes until they are disabled. The status of these are controlled by Authentication Comps and Isolation Bridges.

9. Authentication Comps - Look like big computers, with a padlock icon on them. Password and Elliptic-Curve Security. When clicking on them, the lock it controls is highlighted by a yellow box (one lock per Authentication Comp). Locks are enabled on Authentication Comps by default, but once disabled, will remain disabled (unless you re-enable them) after you log off (or even quit Uplink).

10. Isolation Bridges - Look like small blue boxes with three computer icons on them. To be honest I can't remeber the security on these, its either Password and Elliptic-Curve or none (Will check tomorrow morning). Isolation bridges contro the status of two locks. Here's the trick. Isolation Bridges are DISABLED by default. FOr them to have an affect, you have to ENABLE them (took me awhile to get that. . When enabled, it will switch the status of the two locks. For example, if LOCK1 is enabled and LOCK2 is disabled, enabling the Isolation Bridge will cause LOCK1 to become disabled and LOCK2 to become enabled.

11. Modems - Looks liek a telephone, allows external access of LAN. Often, phone numbers are found on computers for Modems. RUn IP_Lookup adn typ teh phone number in (*****-******), and click go. This will add the LAN to your bookmarks, and accessing form the new location will connect you to the phone. This is often used to access areas of the LAN not accessible from the main switch.

12. Wireless Networking Transmitters (or just Radio Transmitters) - Looks like a radio transmitter, can't get much mroe experienced than that. . Used to connect different areas of the LAN without wires. Frequencies for these transmitters are often found on Terminals. Just enter the frequency and click connect.

13. Main Server - Looks like a computer with a tower. Password Security, plus requires the Administrators Voice Authorization. Here comes the fun part. No matter what bypasses you have on, upon connecting to teh Main Server, the SysAdmin smells something fishy. He will log on shortly after accessing the Main Server (you will hear an alarm if you have your sound on), and he will start a trace shortly after. While some peopel say its a good idea to hit reset now, it generally semms like the trace starts and continues anyway, so I just keep going. (Don't close your Voice-Analyzer after using it the first time, you may need to log into the LAN again to finish the job). Onc eyou are in, the Main Server is basically any Mainframe you hack into. But be quick, the SysAdmin will not wait for th etrace to complete before booting you. The most time you can hope for is 30-40 or before being kicked, the least 2 or 3 seconds (At least this was my experience on the ARC LAN, the trac started with 120 seconds remaining, I was often booted before it hit 100).

14. Yellow Boxes:
Contoller - ANy item listed as a Controller governs the status of the item you have selected; generally found on Authorization Comps or Isolation Bridges when you have a Lock selected.

Locks/Unlocks, Locks, Unlocks - THese boxes generally appear on Locks when you have an Authentication Comp or an Isolation Bridge Selected; it describes what functions they can perform on the locks.

Valid Subnet - These often appear around Terminals when you have an item slected that performs some function (Authentication Comp, Isolation Bridge, Main Server, could be anumber of things). Anythign and everything listed as a valid subnet must be spoofed using LAN_Spoof. Be sure to leave LAN_Spoof open after spoofing each terminal. After you are done with whatever item required the Valid Subnets to be spoofed, you can close the LAN_Spoofs.

Guarded by - I first noticed this whiel hacking the ARC LAN when I clicked the Main Server, the Guarded By box showed up on the three locks surroundign the Main Server. Basically it means you have to disable every lock before accessing the Main Server.

15. Other tips:

If for any reason you cannont connect to some item, such as a lock, terminal, Authentication Comp or whatever, check a few things. IF a lock is not disabled, you will not be able to connect to it. If you do not have all of an item's Valid Subnet's spoofed (make sure all of the LAN_Spoofs are still open), you also will no tbe able to connect.

Items in the LAN you can't seem to get to:

GO step by step through each item in the LAN. Everytime you disable a LOCK, run LAN_Probe on it again to make sure you've foun dall the paths. Also, IP_Probe only workes if you have awire connection to the item, so reuse LAN_Probe on the items tou can conenct to by wire to check for new openings. Also, if you have aradio transmitter o rmodem but no numbers, hack every terminal you can access adn write down anything you can find.

If for some reason you are booted or have to disconnect, don't worry. All locks you disabled will still be disabled. Also, if fo rexample you had time to hack teh passwor don the Main Server (for example), but not the Voice-Print, upon loggin back on you will have the Passowrd already done (once both are completed they will reset after disconnecting).
"

On the question about the dead agent's e-mail, you have to connect to ARC's central mainframe through another ARC server (search for "ARC" on Internic). You don't have to worry about going through anything special, you can just make the bounce path look like "ARC Access Terminal->ARC Central Mainframe". Next, you'd go into the user/password screen. Try logging in as the dead agent (his name and password will appear in the known password list) and disconnect. In exactly three days, ARC will send you the e-mail.

On the "how to destroy a mainframe" question, the "cd log; delete" is unnecessary, as the active trace would have passed that point already. Skipping that saves about five seconds.

I know how to set Uplink up for multimonitor, also, so you can complete the "multiplayer" question. What you have to do is start multiple copies of Uplink (you'll probably have to run them in seperate windows; full screen doesn't let you assign one instance to a display) with the main play window set up as the server. The other one or two windows should be set up as clients connecting to 127.0.0.1 (or localhost). From there, the two client windows should be set for either of the two status modes available.

Finally, on the "disavowed" question, it's impossible to get your agent back. The second you are disavowed, your agent file is reduced to an extremely small file (usually less than 500 bytes) that only contain the reasons for your failure. Because of this, it's impossible to get back your agent file. Isn't Chris a bastard?