They wont be able to access the internet through the pix vpn, practically, when the client connection is up unless you do split tunneling. What you will need to do in order for them to do this is set up a access-list to say what networks they will have access to through the vpn tunnel. That way everything else will be allowed to go through there isp. Something like this.
Access-list 100 permit ip 192.168.1.0 255.255.255.0 10.1.1.0 255.255.255.0
vpngroup cisco split-tunnel 100
Where 192.x.x.x is your inside network and the 10.x.x.x is your pool for your vpn clients.
Now this isnt really recommend as its a security issue. What this will do will allow someone on the internet to say, pc anywhere to your vpn client and then access your internal network through the vpn tunnel. Several acceptable ways to prevent this is to verify that the client has some type of firewall on the pc. There is a built in firewall, umm would have to check to see if available with 3.1, think so, but definitely available with 3.5 +. But no way to verify that they actually have it turned on when going to the pix. With a 3000 you can force them to have it on or they can't connect. So, check to see whats right for you.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...