Does Wireguard + OpenVPN affect Samba?

Hello, today I noticed some strange behavior with Samba.

A problem:
When playing a video on AndroidTV (or phone), after a few minutes the playback stops and skips to the next video with the message “playback from this location is not possible” (or something similar). This behavior is repeated for multiple videos.

Attempt to solve:
I tried restarting Omnia and TV, reinstalling VLC and clearing its data. Nothing helped.
At first I thought it was some sort of VLC or Samba update, but there haven’t been any recent complaints anywhere on the internet.
Looking through the Omnia syslog I found this:

Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' is enabled
Apr  3 17:54:08 turris netifd: Network device 'tun_turris' link is up
Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' has link connectivity 
Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' is setting up now
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: TUN/TAP device tun_turris opened
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: net_iface_mtu_set: mtu 1500 for tun_turris
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: net_iface_up: set tun_turris up
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: net_addr_v4_add: 10.111.111.1/24 dev tun_turris
Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' is now up
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: /usr/libexec/openvpn-hotplug up server_turris tun_turris 1500 1621 10.111.111.1 255.255.255.0 init
Apr  3 17:54:08 turris samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: Could not determine IPv4/IPv6 protocol. Using AF_INET
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: Socket Buffers: R=[180224->180224] S=[180224->180224]
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: TCP/UDP: Socket bind failed on local address [AF_INET][undef]:1194: Address in use (errno=98)
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: Exiting due to fatal error
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: Closing TUN/TAP interface
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: net_addr_v4_del: 10.111.111.1 dev tun_turris
Apr  3 17:54:08 turris netifd: Network device 'tun_turris' link is down
Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' has link connectivity loss
Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' is now down
Apr  3 17:54:08 turris openvpn(server_turris)[18467]: /usr/libexec/openvpn-hotplug down server_turris tun_turris 1500 1621 10.111.111.1 255.255.255.0 init
Apr  3 17:54:08 turris netifd: Interface 'vpn_turris' is disabled
Apr  3 17:54:08 turris samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Apr  3 17:54:09 turris samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: OpenVPN 2.5.3 arm-openwrt-linux-muslgnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: library versions: OpenSSL 1.1.1t  7 Feb 2023, LZO 2.10
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: net_route_v4_best_gw query: dst 0.0.0.0
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: net_route_v4_best_gw result: via 78.141.69.1 dev eth2
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: Diffie-Hellman initialized with 4096 bit key
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: CRL: loaded 1 CRLs from file /etc/ssl/ca/openvpn/ca.crl
Apr  3 17:54:13 turris openvpn(server_turris)[19088]: TUN/TAP device tun_turris opened
Apr  3 17:54:13 turris netifd: Interface 'vpn_turris' is enabled
Apr  3 17:54:13 turris netifd: Network device 'tun_turris' link is up
Apr  3 17:54:13 turris netifd: Interface 'vpn_turris' has link connectivity 
Apr  3 17:54:13 turris netifd: Interface 'vpn_turris' is setting up now

Solution (?):
It looks like some kind of problem with both Samba and OpenVPN.
So I tried uninstalling OpenVPN and suddenly the following appeared in syslog ((unfortunately, I can’t copy the exact wording because I refreshed the LuCI page :-/ ):

Samba is now the default browser for WORKGROUP....

Since then, playback seems to work as before = no problems.

The OpenVPN configuration was, one might say, default, as well as Wireguard is set exactly according to the instructions with almost default values.

Final question:
Is it possible that Wireguard caused all this?

Are we talking about Wireguard server or client? Server shouldnt affect your network but client could make your TV traffic to go by your tunnel

Wireguard server on the Omnia. No client connected to that server at that time. No wireguard on TV.