Księga danych 3com 3c16611 Superstack Ii Dual Speed Hub 500

Subskrybuj nasze sieci społecznościowe, aby być na bieżąco z najnowszymi aktualizacjami!

Komentarz

The VPN tunnels are from the outside interface on one router to the outside interface on the other router. In a typical site-to-site VPN configuration, you should configure the tunnel-groups and peers with the other router's outside interface IP address. The access-lists should be configured to permit traffic flows from one router's inside network to the other router's inside network. Hope that helps.

Just to clarify, you're right to be thinking about a static IP address for the ASA. That's clearly the best solution. If, for whatever reason, that's not possible, the dynamic DNS client may solve your problem. Good luck!

an amazing video.

The dynamic IP address is not an ASA issue. You need a dynamic DNS client running on your inside subnet. The dynamic DNS client will detect when the ASA's outside IP address changes and update your DNS server's A record accordingly. It's been a while since I used that type of service, but just search for "dynamic dns update client" and you'll find something to try. The key is to put it on a computer on your inside subnet. The ASA itself doesn't support it, but your internal client should work.

The demo doesn't use NAT. If you use NAT on the router along with a site-to-site VPN, you must use an access-list with a NAT statement to specify which traffic you want to NAT and which you don't want to NAT. As to your comment about a user, there is no user in a site-to-site VPN, it's router-to-router. As you can see in the video, it works fine. The video is recorded live and there are no editing tricks.

Thanks Mr. Crawley, you have a very user friendly speaking voice - I googled ASA5505 Firewall to DMZ - and I found you.  You gave me clarity on how I will design my senior project security setup.  Will search your site for more firewall ideas and network segmentation.  Thank you again, sir.

Thanks for your comment. Sorry for the delay in replying. I'm not sure how I missed it. It's a matter of configuring separate policies for the site-to-site and remote-access VPNs. Search on the term "site-to-site vpn and remote-access vpn on the same router". You'll find several forum and blog posts covering how to do it and issues others have encountered during the process.

Thanks for your comment. You should be able to set up a site-to-site VPN using an ADSL modem. Search on the term "site to site vpn over adsl" and there are several articles and discussions about how to do it. Good luck!

Would it be possible to use a dynamic DNS name for the outside interface rather than an IP address? This would be for offices that don't have a static external address form there ISP's.

Cracking video - thank you! Really helpful.

Thank you so much for this GREAT video ,

Hi Don, Need to know that during your configuration you applied route map to interface directly without ACL declaration if we will put like this in production will it lead to outage as ACL 100 will do implicit deny to every packet. Please help me in same thanks regards Suresh Joshi

Awesome video. One question I want to ask regarding VPN IPsec. Is it possible to create site to site vpn IPsec when one site is using adls modem so the cisco router will be behind the modem. If it is can possible can you make a video on that or advice on that issue. Thanks

shouldn't the static route be just be set for the remote LAN address and reachable via the other router's outside IP address?

Great and Brilliant Training

Just found this awesome video...do you have one for setting up BGP peers?

Thank you so much i could not had better introduction to VPNs than this video. all the best, Dusan

Very well explained !! Best :) :)

I'm glad it was helpful. :)

Hello Again,

.

Zostaw komentarz

#0