Relayd Wireless Bridge Packet Loss/Dropped Packets Problem

Hi there, I am using Relayd to make a wireless bridge on my TP-Link Archer C7 V2 (Qualcomm Atheros QCA9958) to connect to my main router TP-Link TL-WR1043N/ND V2.

The bridge works fine most of the time, but sometimes it just starts losing packets and sometimes even fully loses connection for ~15 minutes.

Here is a ping from a client connected via Ethernet to the relayd router

C:\Windows\System32>ping 192.168.1.1 -n 64
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=143ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=16ms TTL=63
Reply from 192.168.1.1: bytes=32 time=168ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=72ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=83ms TTL=63
Reply from 192.168.1.1: bytes=32 time=116ms TTL=63
Reply from 192.168.1.1: bytes=32 time=100ms TTL=63
Request timed out.
Reply from 192.168.1.1: bytes=32 time=84ms TTL=63
Reply from 192.168.1.1: bytes=32 time=99ms TTL=63
Reply from 192.168.1.1: bytes=32 time=132ms TTL=63
Request timed out.
Reply from 192.168.1.1: bytes=32 time=68ms TTL=63
Reply from 192.168.1.1: bytes=32 time=93ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=38ms TTL=63
Reply from 192.168.1.1: bytes=32 time=148ms TTL=63
Ping statistics for 192.168.1.1:
	Packets: Sent = 37, Received = 14, Lost = 23 (62% loss),
Approximate round trip times in milli-seconds:
	Minimum = 16ms, Maximum = 168ms, Average = 97ms

However, here is a ping from a laptop connected directly to the main routers wireless network (at the same distance)

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=28ms TTL=64
Reply from 192.168.1.1: bytes=32 time=42ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=28ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

What am I doing wrong?
I followed this guide: https://openwrt.org/docs/guide-user/network/wifi/relay_configuration

Both of your devices are OpenWrt compatible (and also working well under OpenWrt), which means you could use WDS/ 4addr instead of relayd. 4addr tends to be significantly more reliable than relayd (I tried relayd in the past, with less than stellar experiences) - and contrary to relayd, 4addr also supports IPv6 transparently.

The only drawback of 4addr is that both APs need to support it, which is only given fore devices using mainline nl80211 based wireless drivers (so basically restricted to devices running OpenWrt).

any way i can configure it using luci?

I have tried the WDS part with my Archer C7 v2 with OpenWRT 19.07.2.
Main router is an AVM Fritz!Box 7430.
I used the WDS bridge from documentation.
I have tried the ralayd solution which works but sometimes gets stuck and forces me to reboot the OpenWRT box.
No way to make it work with WDS, as I need to use the Archer's ethernet to bridge some wired devices to the wifi LAN. But DHCP doesn't work.
Any hint?

4addr is only supported by mainline (kernel.org) wireless drivers, which are based on nl80211, it doesn't work in combination with proprietary drivers (such as those running on your Fritz!Box).

--
There is an open pull request for the Fritz!Box 7430 on github, which will support VDSL2 and wireless (including 4addr) just fine, but the whole phone functionality never will be usable on OpenWrt.