@Joseph-TP thanks for the feedback.

"TP-Link range extenders use a web-based management interface" agreed, this what I used to do for configuring the device from any computer with an Ethernet connection and a patch cord

"meaning you can access their settings simply by entering the extender's IP address in your browser" agreed, and I can also use the url tplinkrepeater.net to access it, or use an app called Tether TP_Link

"This allows you to configure, update firmware, and adjust other settings directly from your Linux device—no special software or compatibility required" agreed, as I updated the extender each revision of the firmware, hoping this would fix the issue. I am currently running latest RE200(EU)_V4_210916 revision without more success

"Alternatively, you can connect your Linux device to another network for comparison.", agreed, and it is working flawlessly. But I need an extender to reach my working place, the reason I put the RE200 in place, and it is working great with Windows, iOs and Android but not Linux. 

Here's a extract from a log. Everything went well up to the 4way handshake, I am connected to MY_WIFI_2G (the RE200 extender, 2,45GHz).
Then I request an IP to the DHCP server through the RE200 but... no reply. So the connection is ended.

MyPC NetworkManager[911]: <info>  [1759063665.8349] device (wlo1): supplicant interface state: 4way_handshake -> completed
MyPC NetworkManager[911]: <info>  [1759063665.8349] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "MY_WIFI_2G"
MyPC NetworkManager[911]: <info>  [1759063665.8349] device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> completed
MyPC NetworkManager[911]: <info>  [1759063665.8351] device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
MyPC NetworkManager[911]: <info>  [1759063665.8356] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
MyPC wpa_supplicant[916]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-49 noise=9999 txrate=0
MyPC systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
MyPC NetworkManager[911]: <info>  [1759063711.0858] device (wlo1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
MyPC NetworkManager[911]: <info>  [1759063711.0870] manager: NetworkManager state is now DISCONNECTED
MyPC NetworkManager[911]: <warn>  [1759063711.0882] device (wlo1): Activation: failed for connection 'MY_WIFI_2G'
MyPC NetworkManager[911]: <info>  [1759063711.0889] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
MyPC NetworkManager[911]: <info>  [1759063711.0937] dhcp4 (wlo1): canceled DHCP transaction
MyPC NetworkManager[911]: <info>  [1759063711.0937] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
MyPC NetworkManager[911]: <info>  [1759063711.0937] dhcp4 (wlo1): state changed no lease

I've tried one other thing: having the DHCP server at RE200 side: and it works. I connect immediately to MY_WIFI_2G.

So as far as I understand:

- I tried with 3 different version of Linux

- I tried with 2 different DHCP clients
- I can connect to my base wifi network from my Linux laptop, so the router is out of issue

- Router and RE200 communicate well as long as the request comes from a Windows, iOS or Android peripheral

- the RE200 is unable to bring an IP to my laptop when it is requested by a Linux device

I also tried asking "please", but RE200 didn't get it neither.

Maybe you have other inputs that could help me?

Regards


 

Just adding a bit of information: when connecting my laptop with an Ethernet cable TO the RE200, I can't have an IP address. I MUST ask myself to the DHCP server an IP address: 

sudo dhclient -v (my network interface)

Tested on a desktop with Linux too, and it works the same Strange the RE200 doesn't do it.
Linux doesn't wrap the request the "right" way ?