Furious 0.4.7 Tun2socks problem.

[OlroxIX]

Windows 11, Furious-0.4.7-windows10-amd64, vless connection Tun2socks stopped unexpectedly with exitcode 2. Furious 0.4.6 working without any issues.
Furious Log:
[Furious.QtFramework.CoreProcess] [INFO] Xray-core 1.8.23 started
[Furious.QtFramework.CoreProcess] [INFO] no core daemon for Xray-core in power save mode
[Furious.Utility.SystemRoutingTable] [INFO] delete rule 0.0.0.0->10.0.68.1 from routing table success. {'returncode': 0, 'stdout': '', 'stderr': 'The route deletion failed: Element not found.'}
[Furious.Utility.SystemRoutingTable] [INFO] get default gateway success. [('192.168.62.2', '192.168.62.128')]
[Furious.QtFramework.CoreProcess] [INFO] Tun2socks 2.5.2.1 started
[Furious.QtFramework.CoreProcess] [ERROR] Tun2socks stopped unexpectedly with exitcode 2
[Furious.Utility.SystemProxy] [INFO] turn off proxy success
[Furious.QtFramework.CoreProcess] [INFO] Xray-core terminated with exitcode -15

[furrycoding]

Had the same issue
First I tried different wintun versions - installing 0.11 and 0.13 made tun2socks return exitcode 1 instead

Then, after reinstalling wintun 0.14.1, I tried running tun2socks module manually like this:
(Python 3.11 running as admin, cd = where Furious.exe is)

>>> proxy = 'socks5://127.0.0.1:10809'
>>> import tun2socks.tun2socks
>>> tun2socks.tun2socks.startFromArgs('tun://test_tun', '', 'debug', proxy, '')

and got the following log file

It seems that the relevant part is

runtime: newstack at runtime.printlock+0x55 sp=0xc0000475f8 stack=[0xc000044000, 0xc000048000]

...

syscall.SyscallN(...?, {...?, 0x3?, ...?})
        runtime/syscall_windows.go:544 +0x107 fp=0xc0000477e8 sp=0xc000047770 pc=..
syscall.Syscall(...?, 0x68?, ...?, ...?, ...?)
        runtime/syscall_windows.go:482 +0x35 fp=0xc000047830 sp=0xc0000477e8 pc=...
golang.zx2c4.com/wintun.CreateAdapter({...?, 0x2c?}, {..., 0x9}, 0x0)
        golang.zx2c4.com/[email protected]/wintun.go:95 +0xf9 fp=0xc0000478b8 sp=0xc000047830 pc=...
golang.zx2c4.com/wireguard/tun.CreateTUNWithRequestedGUID({..., 0x8}, ...?, 0x0)
        golang.zx2c4.com/[email protected]/tun/tun_windows.go:69 +0x45 fp=0xc000047928 sp=0xc0000478b8 pc=...
golang.zx2c4.com/wireguard/tun.CreateTUN(...)

...

fatal error: runtime: stack split at bad time

Also, running tun2socks v2.5.2 downloaded manually (tun2socks-windows-amd64-v3.exe to be precise) works flawlessly

[LorenEteval]

@OlroxIX @furrycoding Please try Furious 0.4.8 with updated tun2socks library.

[OlroxIX]

Unfortunately with 0.48 result is the same as was with 0.47.

[somebodywashere]

Yes, I can confirm that 0.4.7 and 0.4.8 clean installations still not working with TUN mode.

0.4.6 works well