Register VPN clients in DNS

Which Remote Access method are you using?  Why do you wan to know the IPs?

Cheers - Bob

Hi Bob,

As I said we need to know the IP to access these systems from our office. So every day we have to logon to the UTM, go to RemoteAccess, search for the client IP (e.g. 10.242.2.19) and then connect to it.

We are using SSL VPN. We cannot set a static IP because it only works with IPsec.

Any ideas?

Well, it's not pretty, but it does result in fixed IPs...

Whenever user johann logs into SSL VPN remote access, the object "johann (User Network)" is populated with the IP assigned by the SSL VPN server.  If I assign an Additional Address "johann" on the Internal interface, I can make a NAT rule for johann to reach internal devices like:

SNAT : johann (User Network) -> {services} -> {internal resources} : from Internal [johann] (Address)

Or, to reach the systems from inside, people use the IP of "Internal [johann] (Address)" along with a NAT rule like:

DNAT : Internal (Network) -> {services} -> Internal [johann] (Address) : to johann (User Network)

Will that work for you?

Cheers - Bob

Well, it's not pretty, but it does result in fixed IPs...

Whenever user johann logs into SSL VPN remote access, the object "johann (User Network)" is populated with the IP assigned by the SSL VPN server.  If I assign an Additional Address "johann" on the Internal interface, I can make a NAT rule for johann to reach internal devices like:

SNAT : johann (User Network) -> {services} -> {internal resources} : from Internal [johann] (Address)

Or, to reach the systems from inside, people use the IP of "Internal [johann] (Address)" along with a NAT rule like:

DNAT : Internal (Network) -> {services} -> Internal [johann] (Address) : to johann (User Network)

Will that work for you?

Cheers - Bob

Hi!

Yes, you're right. It's not pretty but should do what we need :-D

I will test it in one or two weeks and let you know. 

Thanks!