Compare cert salaries and plan your next career move
MentholMoose wrote: » Why not use the PIX for the site to site VPN? Even if the other side isn't a PIX, it should still be possible to get working... I've done various combinations with no problems, such as PIX to Netscreen, ASA, and Sonicwall. The 501 is pretty weak though, so with stronger encryption you may get as low as 1MB/sec VPN throughput. Anyway to set up a forwarded port, you have to modify your ACL assigned to the outside interface to allow the port, then setup a static translation to map that port from the outside interface to the server. So a barebones config to forward 9999/tcp (assuming external IP is 172.16.0.50) to server 10.0.0.5 would be like this: Create ACL: access-list site_vpn_acl permit tcp any host 172.16.0.50 eq 9999 Assign ACL to outside interface: access-group site_vpn_acl in interface outside Create static translation: static (inside,outside) tcp 172.16.0.50 9999 10.0.0.5 9999 netmask 255.255.255.255
mathelize wrote: » Thanks for your reply, so you mean I can use a pix 501 at one end and then maybe a windows server 2008 at the other end.
john-cisco wrote: » You could, but have to allow it. What access-list are on the pix? Do a "sh access-group" to see Then check those access-lists "sh access-list" based on the interface it is applied. ACL on a pix is applied INBOUND only. What VPN traffic do you want to allow? Is the server being accessed from a live internet IP? Is that IP natted as a static on the pix, check with sh static. hth
Compare salaries for top cybersecurity certifications. Free download for TechExams community.