Full VPN tunnel from FlexH 1.32 FW to Nebula Org firewall

Yes VTI are in the same subnet now, but the hidden mistake was to use the same IP (not the same subnet…) for both. I did not see this mistake because it was set once on Nebula and never checked again until some hours of testing.

Now I have this rule working properly:

but the local LAN of FlexH goes remotely on the first subnet it finds.

When I set the VPN as "Custom" on FlexH I told the VPN to go to a specific remote subnet but it seems it ignores that:

that blu "Destionation" subnet is where I wanted to have that traffic from VPN.

Remotely I have different subnets:

• 192.168.1.1
• 192.168.10.1
• 192.168.201.1 and so on….

So the traffic from VPN has to go on a specific one.

In reality the VPN goes to 192.168.1.1 network

Should I used this advance area to specificy which is the remote destination?