Unable to start 5 GHz Master network on RE450

Installing and Using OpenWrt Network and Wireless Configuration
1

Hello, today I was trying to make the TP-Link RE450 v2 to connect to my main router’s 5 GHz network to make a wireless repeater network.

I have successfully connected the TP-Link device to the main router’s network and have created a 2.4 GHz network with it, but I’m unable to create an AP on the 5 GHz band.

I have noticed that my system log is flooded with this message:

Fri Aug 21 16:20:54 2020 daemon.err hostapd: Failed to set beacon parameters

My wireless configuration (/etc/config/wireless) is as shown below (SSID and passwords changed):

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'pci0000:00/0000:00:00.0'
        option htmode 'VHT80'
        option legacy_rates '0'
        option country 'ES'
        option channel '36'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option wpa_disable_eapol_key_retries '1'
        option key 'Password123'
        option ssid 'Network5G'
        option encryption 'psk2+ccmp'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'platform/ahb/18100000.wmac'
        option htmode 'HT40'
        option channel 'auto'
        option legacy_rates '0'
        option country 'ES'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option wpa_disable_eapol_key_retries '1'
        option key 'Password123'
        option ssid 'Network2G'
        option encryption 'psk2+ccmp'

config wifi-iface 'wifinet2'
        option ssid 'MainWiFi'
        option device 'radio0'
        option mode 'sta'
        option key 'MainPassword'
        option network 'wwan'
        option encryption 'psk2+ccmp'

Does anyone know any reason why this happen? Any invalid settings?

Thanks in advance.

2

I seem to run into the same problem, hence I don't seem to get the deamon.err beacon logs