@vagelismin, you don't need a mesh network to offer your clients basic roaming functionality w/o having to specify an encryption key every time passing to another EAP. The solution is to use the same SSID and the same encryption key for all of your EAPs.

In fact, basic roaming has been there since the very first 802.11 standard. It's the reason why each AP has two SSIDs: the ESSID for the Extended Service Set (this is what people mean if they talk about the »SSID«, it's the name for a WLAN as seen in a wireless survey) and the BSSID for the Basic Service Set (a single AP as seen in a wireless survey). You can even roam between APs of different vendors:

If you can wire EAPs, wire them. Mesh networks do have disadavantages compared to wired EAPs.

The only advantage of a mesh network is to save a cable from the EAP to the wired network.

The disadvantages of a mesh network are:

• decreasing bandwidth (½ bandwidth in the 5 GHz band for every mesh hop),
• the Hidden Node Problem for clients in the 5 GHz band,
• and, most important, the reduction of total user capacity from ~60-80 clients per EAP to ~60-80 clients for all meshed EAPs together in both, the 2.4 GHz and the 5 GHz bands.

@vagelismin, you're welcome.

What exactly do you mean with »password«? The encryption key / WPA key? Or a portal password?

EAPs offer many different authentication schemes.

Next question: are you using the EAPs in stand-alone mode (web UI for management) or in managed mode (Omada Controller for management)?

vagelismin wrote

i think all the access points use different ip address. do they need to use all of them the same IP ?

The EAP must not use the same IP; each EAP needs its own, unique IP address.

An EAP's IP address does not play any role for a client connecting to a wireless network. The equivalent of an IP address in a wireless network is the BSSID (AP »address«/ID), which is determined by the client device by looking up the ESSID (WLAN name/ID).

vagelismin wrote

i had to give again password

You need to save the passwort in the wireless client (setting »remember this WLAN« or similar in your client device). Once saved, the client will roam between different EAPs using the same SSID and credentials w/o requesting the encryption key again. Make sure you really did set the same encryption key for the different EAPs.