The situation is this:
We have 2 datacenters, one in HQ and one remote.
Pulse metal is located on the remote datacenter, split tunneling is enabled.
Our clients are located in HQ and can access the servers on HQ without pulse but must use pulse in order to connect to the remote datacenter.
When working from home, while connecting to Pulse, I added the HQ routes, which makes clients that are connecting to pulse, to also be able to connect to HQ servers. everything is working.
The issue is, when clients are working from HQ, connecting to pulse, they still get the routing table I added. When they try to connect to HQ servers, they are routed through the remote datacenter to HQ datacenter, which makes big latency.
So what im looking for is routing by rules (Detailed Rules).
I tried to set it up with no success.
I'm trying to place a rule by source ip, using the lan subnet on HQ/or wan ip of HQ. im not sure.
The issue is, im not sure what is this "source ip", i tried every ip possible without success.
Going to System->Log/Monitoring->User Access, I can see from different logs, that users has src ip of 127.0.0.1 .
any help on how to approach this would be appriciated!
Solved! Go to Solution.
while keep investigating, I understood that theres NAT involved.
the ip everyone is getting is not 127.0.0.1 but the gateway ip.
trying to understand why it was set up that way