IPSEC Use static remote access IP not working

Question

Hello, 
 I have a UTM 9 SG210 model and since the latest updates seems that the static allocation of IP's became a real pain, because the UTM gives the same IP to other clients also. 
 I opened a support case but they did'n find any issue on my configuration, also i send to them the log on clients. 
 The first issue came with the IP 10.2.2.1 which wasn't allocated to none of the static clients and still was offered to ipsec clients which had another IP allocated. 
 Recently, after i made a static allocation of the ip 10.2.2.1 i find out that now the UTM gives the IP 10.2.2.6 which is also reserved, to other clients also. Also on that IP class i don't have any DHCP it's only a simple pool. 
 Does anyone had this issue? 
 Thank you in advance.

BAlfson · Accepted Answer

Salut Gabriel, 
 It sounds like you don't have that many Remote Access users, so I would try expanding "VPN Pool (IPsec)" to .0/24 and then assign fixed IPs in .128/25. Odds are that that would not cause any conflicts. If that "trick" doesn't work, you'll need to craft manual Firewall rules instead of using automatic. Let us know. 
 Cheers - Bob

Gabriel Georgescu · Answer

Hi Bob, 
 Entire 10.2.2 network is split in many subnets because i have also RED15 devices. So the actual split is: 
 - 10.2.2.0/25 
 - 10.2.2.128/27 
 - 10.2.2.208/28 
 - 10.2.2.224/28 
 - 10.2.2.240/28 
 If i understand well i should decrease 10.2.2.0/25 for pool allocation and the rest should remain the actual static VPN clients?