[Added] XLink Kai

[sairuk]

XLink Kai is now available in a branch, it needs testing. I still haven't received the auth response to my registration with the project so I can only so some limited testing until that comes through. if you already have an account and can test it out that would be helpful

Use the branch switcher from the Updates menu to switch to the xlinkkai branch, the installer is available in the Experimental menu.

Documentation

[s3anami]

I can try and test but does it have any known conflicts with other functions and can I switch branches back without issue?

[s3anami]

that is concerning lol
Anyway for Hyper-V it mostly needs to be done via CLI too (ironic, it being windows based and esxi being linux)
I did the first 8 steps here:
https://docs.tenable.com/nnm/deployment/Content/VM/Hyper-VInternal.htm

[sairuk]

so a little bit more reading and it claims the vswitch/portgroup policy is working but as xlink is working i have my doubts. i'd need to start looking at traffic when I have time but since i have no expectations of running this on a vm motivation is low, I was already planning on dropping esxi.

2022-07-25T20:37:52.046Z cpu5:2100739)cswitch: L2Sec_EnforcePortCompliance:207: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]client  requested promiscuous mode on port 0x200000e, disallowed by vswitch policy

From a RetroNAS perspective we just need to document prom support is required for functionality and move on.

[s3anami]

sounds fine, ill let you know if there is anything else i run into when trying it, only got into 1 latam halo game so far and was swiftly kicked so ill keep trying

[sairuk]

thanks for your help with testing this

[teamxlink-dev]

You'll only need forged transmits for Xbox and Xbox 360 games. For the other platforms we have an internal workaround where it is not required. Promiscuous mode may not be needed for all platforms but Kai will still try to enable it

[sairuk]

When logging out of the webui running as a normal user

kaiengine: /opt/xlink/kaiEngine/references_aarch64/boost_1_76_0/boost/thread/pthread/recursive_mutex.hpp:108: void boost::recursive_mutex::lock(): Assertion `!posix::pthread_mutex_lock(&m)' failed.
Interrupt signal (6) received.
Segmentation fault

[sairuk]

but only if kaiUIClose=1 in the conf otherwise logout will exit the engine cleanly (exit-code 0) which is not the expected behaviour.

So logout from the web-ui is actually an exit action by default, we can probably work around this by using Restart=always
in the systemd service file and then providing an exception for select exit codes

[sairuk]

Played around with Xemu in Bridged mode for this as well,

• Ubuntu install, worked fine with the setcap perms fix from the official doco
• Manjaro aur or flatpak both reporting "Address family not supported by protocol" which I haven't resolved yet

[noz1380]

Just had a play on Halo 2, seemed easy to setup and find a game.

I'll have a play with my PSP and Vita too.

Thank you for all the hard work, this is awesome.

[teamxlink-dev]

Hey there, if you have any questions let us know :)

I've read through your XLink wiki entry and you've hit a few known bugs (erroneous IP incorrect etc)

[sairuk]

Will do, thanks for taking a look at our doco