When working with VPNs, solve confusing "routing" problems with Full NATs. [:)]
Lars, Jan, the trick is create virtual VPN IP Pool for VPN Static IP.
Add virtual network different with VPN IP Pool (10.242.2.0/24) ie. 10.242.7.0/24 in Local Networks SSL.
Create virtual VPN Static IP using Full NAT (DNAT/SNAT)
Any --> Any --> Client IP Static (ie. 10.242.7.7) --> Source Trans: Internal Addr --> Dest. Trans: Name_A (User Network) --> Automatic Packet FR: Checked.
....
....
Any --> Any --> Client IP Static (ie. 10.242.7.9) --> Source Trans: Internal Addr --> Dest. Trans: Name_Z (User Network) --> Automatic Packet FR: Checked.
Client to Client Communication is ready to be connected through virtual IP static.
Kind Regards,
Gunawidjaja Joseph
PT. Ultrajaya Milk Industry & Trading Co., Tbk.
Indonesia.
Traffic Source: Any
Traffic Service: Any
Traffic Destination: Ruben-Static {a DNS Host object you define with a fixed address}
NAT mode: Full NAT
Destination: Ruben (User Network) {this is the object created by WebAdmin when the user "Ruben" was defined}
Destination Service: {leave blank}
Source: Internal (Address) {this is the object created by WebAdmin when the interface was defined}
Source Service: {leave blank}
Hi, Ruben, and welcome to the User BB!
For example:Traffic Source: Any
Traffic Service: Any
Traffic Destination: Ruben-Static {a DNS Host object you define with a fixed address}
NAT mode: Full NAT
Destination: Ruben (User Network) {this is the object created by WebAdmin when the user "Ruben" was defined}
Destination Service: {leave blank}
Source: Internal (Address) {this is the object created by WebAdmin when the interface was defined}
Source Service: {leave blank}
Did that help?
Cheers - Bob