Saving settings ultra slow via VPN?

[highend]

This is not a bug report^^

I have the following situation:

A MacBook with an ARM64 Win 11 instance in Parallels Desktop.
The XY version doesn't matter as it happens with all I've tried, but using the current beta atm.

The MacBook is connected solely via WLAN to the local home network.
Running XY, startup time, shutdown time (with saving settings) is totally fine.
It's a fresh instance, the profile is redirected to a samba share on the local lan via the Startup.ini file.

Now I'm doing the following:
I connect to the local hotspot of my iPhone, it's on the table right beside the notebook.
The phone is connected via LTE, good signal strength, no data rate limits.

Now I'm connecting from the VM via Wireguard VPN to my local network.
The Wireguard server is a Fritz!Box 7590 AX.

This is the profile:

Code: Select all

[Interface]
PrivateKey = uKk4rFq...rtHBB6G1I=
Address = 192.168.0.241/24
MTU = 1420

[Peer]
PublicKey = 440Qnf...gRqgI=
PresharedKey = IgGTafF...Nfb6A=
AllowedIPs = 192.168.0.0/24
Endpoint = xxx.myfritz.net:59516
PersistentKeepalive = 25

And now I'm using this little script:

Code: Select all

$start = now("msecs");
    #186; // Save catalog
    text "Time: " . now("msecs") - $start . " msecs";

Again, this is a fresh instance, so the catalog is 3 KB in size^^

It takes ~15 seconds for the script to finish...

15 seconds for writing only 3 KB^^

XY goes into a non-responing mode during that time (but there is not multi-threading so this is kind to be expected)...

Can anyone explain how this can take so long?
And probably more important: What to do to get it running properly?

Thanks!

[admin]

Have you tried other types of writing? Same slowness?

[highend]

Each write of a config file from XY to the share while connected via VPN is ultra slow, yes.

But again, this is not an issue of XY^^

[jupe]

Maybe try Wireshark, and compare the differences between shutdown saving and scripting saving.

[highend]

Thanks for the suggestion jupe.

Decrypting WG traffic doesn't seem to be that easy when trying to do that on a Windows box :/

The Wireshark wiki supposes to do that on a linux box, optimally on the vpn server itself.
Not that easy on a FritzBox...

Maybe I'll setup a WG server on the debian box (same server than contains the samba server), do the port forwarding and try it there.
Can take a bit of time though...