I recently installed Ivanti Secure Access Client on MacOS 13.0 in order to access some company-private locations.
Works like a charm in order to reach those locations, but of course it heavily messes up pretty much every other functionality (web navigation, any other client that needs to connect anywhere).
I'm looking for a way to only send certain traffic through Ivanti Secure Access Client and leave the rest unaffected. Could you suggest anything like that?
Solved! Go to Solution.
Adding on my initial explanation: I know I could achieve what I need by installing the Ivanti client on e.g. an Ubuntu VM, and then using the VM as a JumpProxy; but since I'm using a MacBook running on an Apple M1 chip (i.e. underlying arm64 architecture) I actually can't install the Ivanti client on Ubuntu, since the only Ubuntu/Debian installer available is meant for amd64 architectures.
So if I understand correctly the client "decides" what traffic should be routed through the tunnel based on server-side configurations, and this is the built-in feature that Pulse offers in order to meet this requirement.
Without this server-side configuration (I'm currently not in a position to request specific configurations to the admin) do you believe any other way would work? I was thinking of something along the lines of defining a secondary private network interface and somehow bind Pulse to that interface; then edit my local route tables so that only certain adresses are resolved through that secondary interface. No idea about how to "somehow bind Pulse to" a specific interface though.
Thank you for your time anyway.
As an alternative,
I'm trying to go down a different path
Nevermind, that didn't make sense but I couldn't find a way to actually remove it.