Sometimes everything will work. Devices connected via the ethernet jack or the configured 5g wifi network connection will get dhcp from the network on the other side of the wlan bridge, everything is fine. Devices on the other side of the network will work, connecting to the remote endpoint of the bridge will also make a working device - hence connectivity on the place of the repeater is allways available

errnous behaviour:

- the signal LED is blue, as 2.4 ghz LED and power LED. 5ghz led is off.

- the repeater is connected via 2.4 ghz to an upstream network.

- it may obtain its own address via dhcp or hard configured

- the status screen in the webinterface shows a yellow checkmark on the "Internet" icon

However, occasionally devices connected to the repeater will not get the DHCP of the remote side, but from the repeater itself. (dhclient anounces the IP of the DHCP-Server, which is the one of the repeater)

Though it knows all the upstream dhcp connection parameters, it will anounce itself as default route and DNS, which for sure won't work.

One can ping IPs on the other side of the bridge then, nmap will find devices on both sides of the bridge. Manually configuring the default Gateway and DNS will make the network on clients connected to the repeater work.

Though the router has the proper internet and DNS configuration, trying to bind it with a tplink cloud network will not work - "Request timed out"

Obviously this seems to be the mode, where the repeater allows the connectivity for its own initial configuration, though its fully configured.

How does it decide to go into this mode? How can it be fixed? This is really anoying.

Cheers,

Willi