Remote-Access pulls all subnets from Gateways in remote-access community

[skandshus]

Hello everyone

We manage gateway for different customer.

Since many of them use remote-access we have disabled the automatic mep topology to block endpoint client from pulling information about all gateway in the manager.

If we do a route print in CMD in windows we can see routes are being pushed to endpoint client from all the gateways. Perhapt because all gateway are in the remote-access community. How do we Block that from happening so connection to Gateway A only gets routes to Gateway A and not routes to Gateway B/C/D even though they dont work

[JozkoMrkvicka]

Since it is not possible to have more than 1 Remote Access Community in the same Domain, the solution can be to migrate Gateway B to Domain2, Gateway C to Domain3 and so on.

If Gateways B/C/D dont work, why you have them part of Remote Access Community ?

[skandshus]

Correct.

But that would result in having to buy multiple management license because we have to go multidomain server or multiple management servers.
and we have paid for 1 management server to manage multiple gateways 🙂

[PhoneBoy]

Remote Access clients get their routes based on the RemoteAccess encryption domain.
At the moment, there is only one RemoteAccess encryption domain per management domain.
As far as I know, there is no way around this.

I believe I heard we are planning to add support for multiple RemoteAccess encryption domains in R82.10.
Given that we just released R82, I don't see R82.10 coming out in the near future.
This leaves you with using either multiple management servers (may wish to consider Smart-1 Cloud for this) or multi-domain as the only way to meet this requirement currently.

[skandshus]

does that mean you are forced to recieved routes from all gateways in the remote access part?

isnt there any way to actually modify anything in the trac client so it doesnt pull from all other gateway but only the current connected gateway?

[PhoneBoy]

There is a single RemoteAccess community per management domain.
Each gateway has it's own (Remote Access) Encryption Domain.
When the gateway is added to the RemoteAccess community, the necessary routes for ALL gateways in the RemoteAccess encryption domain will be sent to the client when the client connects to one of the gateways. 

It does appear there might be a way to resolve this (get topology from connected gateway only).
See: https://support.checkpoint.com/results/sk/sk92676