I am in pretty much the same situation you are. I had a LOT of trouble with the cisco vpn because it takes over your routing and hostname lookups. I solved this by replacing my router with a linux router (old enough to run the cisco client). I configured dns to do lookups on the correct dns server for the different domains (the whole world, vs my local or work networks). I configured dhcp to install my home machines in dns. I script wrappered the cisco client to restore my hand edited resolv.conf after starting. Now I can connect to my work network from any machine behind my router, and print properly etc. (from vm's too). You'r requirements are a little less demanding than mine and you might be able to overcome the printing problem by adding a static route to your print server after bringing up the cisco client... There is also an opensource "vpnclient" which will connect to the cisco vpn server (if you're using the old Concentrator 3000 series or compatable). It works ok, but tends to go down during key replacement (about 8 hrs). wcn Kai Ponte wrote:
I have an odd question. I don't really *need* this but I wonder if it can be done.
I often telecommute to work. Particularly in the evenings, I work at home. I can either load a VM - such as - Vista or work directly.
When I load the VM, I run the VPN client (Cisco with a RSA key FOB) from the VM. My "main" network is not touched and openSUSE is still on my "home" network.
When I load the VPN client (Cisco VPN Client 4.8.00) from openSUSE I connect the computer entirely to my corporate network.
Now the question - every once in a while, I decide I need to print something locally.
I currently share a printer with my wife's computer (Windows 2000 Pro) over SMB.
Is there any way I can run on the vpn with my corporate network yet attach locally to my home connection?
Do I need to create a proxy or something?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org