@MR.S 

but actually both are server and client in the wireguard world. like if you want to reach another wireguard network from the router you have to add this to the peer config on the router, the same way you do in your client file. her is an example of a wireguard client on an omada router

Here I have entered which remote network the router should have,

  @MR.S 

Good morning

Thanks again for your help, I have it working like this now :

I give the clients an ip from 192.168.124.100 until xxx

this gives me a nicer overview of the clients, the peers on the server side I give an ip starting from 192.168.124.1 until .99

But now I give the clients access to the complete ip subnet 192.168.123 and 192.168.124

I'm going to test how I have to configure the client to give only acces to one IP address 192.168.123.x

What address of the range 192.168.124 do I have to add too in the allowed IP's ? The ip of the Wireguard server 192.168.124.1 or also that from the peer 192.168.124.x ?

  @Rytec 

If you want the client to only reach one IP, add 192.168.123.10/32, for example, to only have access to 192.168.123.10.

Is it recommended to add a VLAN in the Omada network config for this new IP range which I use for Wireguard?

And which address do I use as DNS server?

I also have an own domain name, should I somewhere put this in the Omada configuration?