Hi @CostinR1, WireGuard itself is quite tricky to configure properly, especially in site2site scenario, where you have to manually setup all the routing. Fortunately in client2site scenario the...

Hi @CostinR1, I see the problem: the Wireguard local IP and the peer's allowed IP must be in the same network range 192.168.0.235 is well outside of 192.168.0.244/30 the usable IP range for...

Hi @Vincent-TP, sorry.... I'm subscribed to beta software and firmware, so EAP FW was before the 1.5.3. The controller is updated at every new release. Unfortunately I can't say, when the settings...

Hi @Vincent-TP, maybe a small misunderstanding, let's summarize the issue again - now with picture 1st of all - Controller settings were in sync with EAP physical settings, so no "Force provision"...

hi all, I've just found out by accident, that after some FW or Controller upgrade the former static IP configuration of EAPs was reverted back to DHCP on all my EAPs. When I clicked to configure...

Hi @arrmo quite strange.... Normally no keys are requested for SSH login, unless you want to login without username/password - then the user key must be stored at SSH server - which generally doesn't...