I have a bit a stumper (for me at least). I have a 501 behind a broadband cable modem (motorola). The cable modem is acting as a bridge. The 501 gets a public IP from their ISP. To get to the configuration of the cable modem, in a web browser you type in the IP address http://192.168.100.1
Now, what I was doing on the 501 was using an IP address scheme of 192.168.0.X 255.255.255.0 netmask. Once I implemented the 501, I can no longer get to the cable modem to restart it or look at the configuration. What should I do? I thought about changing the IP address scheme of the 501 to 10.10.10.X netmask 255.255.255.0. That way, when I type in 192.168.100.1, its not on this network so it should pass the traffic onto the outside, correct?
If cable modem is set to 192.168.100.1 address and PIX is getting a different IP from your ISP, there is no way you can get to your cable modem. The only way to configure it is either assign the same subnet address as of cable modem. but in that case your pix will not be able to communicate outside. So the only option left for you is to use console cable to configure the cable modem. OR set the cable modem too, to get an IP from your ISP.
Tha is a strange thing. What is usually the range of IPs assigned from your ISP? Private? or Public? where they in the range 192.168.100.0? How could you access the modem in the first place if you directly connected a PC behind your modem? what IP where you given and what subnet mask? That could give you an idea on how to fix the problem. Only if you find how it worked before. Maybe you where given 2 IPs, one in the Range of 192.168.100.X and 1 in the ISPs normal DHCP Pool.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...