So, those are the three gunboats we picked up on the approach vector. I’ll tell the team working at the drydock to give them priority.
While we haven’t worked on an Ahoudori-class gunboat before, there should be a blueprint in the database somewhere.
Now, regarding the price for this service, the Guild has instructed me to waive the cost of the materials used in updating the gunboats, and you’ll get new engines as a freebie from me. However, the labor put in by my fellow members will cost one hundred and forty thousand Sirian credits.
The Guildmaster has warned us about a possible large scale conflict going to happen in Inverness between the locals and the LSF. Good luck out there.
With respect
Lya Roche, Singapore Shipyard
¤-¤-¤-¤-¤-¤-¤-¤-¤ End of Transmission ¤-¤-¤-¤-¤-¤-¤-¤-¤
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
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
GRUNDER SOFTWARE GmBH NEURAL NET SUITE
NEURAL NET DATASTREAM SOFTWARE v1.2
USER: SONG, JAE-UN 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.
USER ID: JAE-UN SONG Network DMARC Point: DMARC.UTSUNOMIYA.OUROBOROS.CO.EW Client Relay DMARC Point: ship-nn-datalink-1 VALID ENC CERTIFICATE
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
Thank you for the rapid repairs on our task force's vessels. It's greatly appreciated by me and my men. I'll be sure to bring you and your yardworkers something nice when we bring Tochigi and Utsunomiya in the coming weeks. And give Guildmistress Akibara my thanks for the chat. Was nice to have someone chill to chat with out on the station promenade.
God speed.
Maj. Jae-un Song
Kotetsu Fighter Brigade CO
Fleet Actual, Task Force Shirikunne (Temp)
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
As we had discussed before, the Utsunomiya and Tochigi hve entered dry dock at Singapore Shipyard and the longshoremen and engineers present have reported that extensive work will need to be done and it might take until around the start of December to bring both to functional status. Words do not begin to describe the gratitude that we have towards the IMG for the ability to seek repairs at Singapore.
Furthermore, to.. clarify on questions that I've had to answer for said engineers, the Utsunomiya is equipped with an IMG Nyantse Sensor suite, which we had salvaged from an abandoned IMG Sagarmatha before our departure from Sirius, which according to records had been engaged in conflict with the Gallic Navy and was subsequently lost at some point. The reason for this is straight forward - As mentioned prior, our former flagship, the Abdicant Seraphine, was in poor condition prior to our departure as a result of lack of access to any viable shipyards. As a result, we made last minute modifications to use Utsunomiya as a flagship that would operate away from combat and serve in a C3BM role much like Seraphine had.
I am willing to, in appreciation for the IMG's service, pay whatever the guild sees as justifiable for services rendered, resources used, and the acquisition and use of this hardware without the guild's consent. Had we any other options that would fit in the confines of the radar sub-assembly of the Shukensha, we would have done so - and It is my firm belief that these modifications have helped us navigate the treacherous space on the way back home, and have to this day, allowed us to recieve more than ample warning against potential threats to the fleet.
Please get back to me at your earliest convenience.
Well that is strange we have no records of a Sagarmatha entering combat with the Gallic Navy during the occupation of the Tau sector simply seeing the serial number during the upcoming repairs done on the Utsunomiya. As for the price it should total around two million when calculating all the services the guild provided to the battlegroup. As for the sensor suite we would of course require all of the sensor data your ship collected after installing it. Additionally We would like the location of the abandoned IMG explores and any data you have about it.
With respect
Lya Roche, Singapore Shipyard
¤-¤-¤-¤-¤-¤-¤-¤-¤ End of Transmission ¤-¤-¤-¤-¤-¤-¤-¤-¤
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
Funds have been wired for the maintenance operations as you asked to the account we have on file.
Furthermore, regarding the Nyantse suite's sensor data, I've reached out to Sanzu DEVGRU - our SOF and Intellignece forces, and hopefully we should have the sensor data recovered from the suite from back then. Due to the rapid need to refit the Utsunomiya outside of a dry dock, it wasn't exactly done in a prim and proper manner. I hope you understand.
Though, consulting with Major Kensington, who oversees Sanzu DEVGRU, which Kourindou is a part of - on second analysis of what records we have available, running it through analysis systems again, the IMINT records we have for that ship, the GPV Koncog - the fires that disabled the ship match damage signatures comparable to Nazione Maltesa ships. How we confused them for the Gauls is beyond me.
The Koncog was originally found in Tau-23 but its' orbit was extremely eccentric. Simulations suggest that it's likely somewhere near the Lagrange point between Orkney and Tau-23 at this point, nearing its' apoapsis. Whilst we wait for the archives of that sensor data, Sanzu has compiled an archive of all information about the Koncog that we have on hand, including the simulation we ran, Imagery Intelligence as stated before, after action reports - the only reason we don't have the sensor data is because we didn't properly handle the sensors outside of their extraction from the Koncog until we could bring them back to Maehara for installation, and that's compartmentalized elsewhere as a different operation. I hope you understand.
We should have that data for you by the time we're to depart from Singapore.