I have a 2154 handling many to one translations. As fas as I know IPSEC only works with a one to one translation. Are they going to implement a way for IPSEC to flow in the many to one environment or should I look for other solutions. If I had roughly ten addresses, could I reserve a pool of 9 for IPSEC only and i address if they aren't using ipsec. So to say, if my internal users wanted to surf, it would overload the one address. If they wanted to use the vpn they could grab one from the pool to be static. I am fairly new to the scene so any help would be greatly appreciated.
As I am so fond of saying, anything can be done if you are willing to live with the complexity. The first question that comes to mind is what are you doing with IPSec that you would need NAT? If you are going between remote offices, then you do not need NAT. I would need more information on what is on the other side of the iPSec tunnel to provide assistance.
Small business using a cable modem for internet access needs to connect to a larger business via a vpn concentrator cisco 3005. the cable modem provider limits what we can do with the router. I just want the ability for users internal to the cable modem to initiate a vpn connection using cisco vpn software.
ok, what I would do is build an IPSec tunnel from the 2514 to the 3005, I would then have a GRE tunnel from the 2514 to another router at the corporate site. In effect, the GRE tunnel could be treated as a normal wan connection between your remote site and the larger site. You should not need to do nat to get to or from the remote site to the larger site, but would only need NAT for remote site users to access the internet
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...