Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 23087 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Client Authentication Agent and macOS High Sierra

Bizcocho

Hi forum,

I've tried the XG Authentication Agent for the first time - and I've installed it on the newest macOS High Sierra release. To me, it looks like it doesn't work, as it doesn't connect. I've setup the rules in the XG ruleset, and also given the user access to the virtual SSL VPN.

How to troubleshoot this agent? Are there any log files somewhere to check? And has anyone else tried this agent on High Sierra?

Running XG Home Version beta 17.



This thread was automatically locked due to age.
  • 0 in reply to Sivu

    Maybe I should clarify my context: I am working from another office outside the company owning the VPN. I am a contractor working remotely for them. My DHCP server is running on the local wifi router in my office and it set my default gateway to 192.168.1.1

    I tried adding as default gateway 1.2.3.4:9922 but I get an error (I can only specify the IP, not the port) and I would expect it to not work anyway, because that address would not be reachable from my WLAN, maybe when I manage to connect to the VPN the VPN can magically resolve it but I am not sure how to do to connect to the VPN in my context.

    Sorry for the basic questions but since the upgrade to macOS High Sierra (weeks ago) I am unable to connect.

  • 0 in reply to Federico Tomassetti

    Client Authentication Agent is intended for clients on those networks who have the XG as default gateway. Obviously the XG is not your default gateway and this raises the question what would it help if Client Authentication Agent is able to connect. Your traffic would not be routed through the XG because its not the default gateway. If you are using it to access some specific subnets and access is granted by XG based on your Identity via Client Authentication Agent, then you could try to install a host route on your macOS, so that traffic destined to 1.2.3.4 will be sent to the XG.

    e.g. sudo route -n add -host 1.2.3.4 <XG's IP>