I would maintain a general document of the setup (as it involves Windows, it won't obviously become a downloadable Virtual Appliance) so anyone facing the same problem can just follow the cookbook and be in business.įor Check Point specifically, you could try IPSecuritas on the Mac OS side. Do I need a Windows Server version, will Routing and Remote Access be my best bet, or do you have any other simpler solution?Ģ- OS X routing help, in order to get the correct routing entries added. I need ideas and help in some areas:ġ- How to route (or NAT?) at the Windows VM level so traffic can go from the VPN tunnel back to the Host-Only adapter. And at the Windows level, I must be able to route properly what comes from the Host Only adapter to the VPN tunnel and back.īuilding a 2 NICs VM is not my problem.
I would need to add proper routes from within OS X to route through the vmnet1 adapter (which I don't know how to do - I know I must pretty much route let's say 10.33.0.0/16 back to the VM to be forwarded to the Checkpoint VPN connection). Kind of a Virtual Appliance, to handle Microsoft-only VPNs. So, I want to use a Windows VM, load the CheckPoint client (and this solution would be an option for Firewall clients where no OS X version exists), have two NICs in the VM, one for Internet Access and one Host Only networking.
I also have to deal with some no-Mac-version-VPN clients and I hate simply reverting back to Outlook under a VM. And don't respond the Mac OSX Checkpoint VPN Client, as it will not work in Leopard, due for the end of this month (and based on Checkpoint track record, we might wait 6 to 9 month before getting a suitable 10.5 compatible client).
0 kommentar(er)
