GRUNDER SOFTWARE GmBH NEURAL NET SUITE
NEURAL NET DATASTREAM SOFTWARE v1.2
USER: HANAMURA, NODOKA ERROR: REGISTRATION EXPIRED 2973 DAYS AGO. NON-FATAL EXCEPTION - NULLPIRATEN.SO NOT FOUND (0X000000AA)
NEURAL UPLINK: ONLINE
CONNECTION STATUS: ONLINE
GATEWAY: tau-ext-23339.tau.nnbackbone.kimidori.co.ku (234.91.11.4)
[DEFINED BY NETWORK POLICY VIA NDHCP]
DMARC POINT: DMARC.UTSUNOMIYA.OUROBOROS.CO.EW
(c49a:99ca:c892:1120:19a3:1dad:feed:9344)
VERIFYING CHECKSUM... OK
DATALINK XMIT DEVICE SLAVED AS /dev/ens4p1.
XMIT TYPE IS SET - BIG ENDIAN.
ENCRYPTION SUITE IS SET - AGEIRA 4098 QUANTUM-RESISTANT HASH W/ PRESHARED KEY
ENCRYPTION DEVICE IS TYPE - EFUSE
EFUSE DEVICE IS /DEV/MODULAR/EFS90E30.
READY FOR DATASTREAM - LISTENING FOR PACKETS ON LOOPBACK DEVICE.
Negotiating security policy from Network Policy Server.. ERROR - NO NETWORK POLICY DEFINED - CONSULT WITH YOUR FACTIONAL NETWORK ADMINISTRATOR.
Continuing with local policy..
Negotiating routing path from Gateway..
Route received from Gateway.
Opening port 42010 on /dev/ens4p1..
Transmitting datastream
We've taken custody of the Tochigi from the yardmaster as of Monday, and she has departed following completion of repairs.
Furthermore, we've managed to get a copy of the Koncog's radar data from our records before we took it into our custody - the data package is enclosed. According to last records the track file associated with the ship that fired upon the Koncog was apparently the MNS Solaria, a Sarissa-class Battleship.
However, I wanted to relay something if they had not done so already - it seems the reactor and some of the fuel lines aboard the Utsunomiya needs replacement, which explains some of the fire control and targeting issues we've had since coming back to Sirius. Whilst the Utsunomiya's by no means a direct fire vessel, we do need the CIWS functional to protect the vessel from enemy torpedo and snubcraft fires.
We're willing to pay for the additional repairs needed for this, and are open to buying a reactor from the IMG directly if possible.
