I just need to set-up my 1811 router to connect our LAN to the internet through our ISPs T1 router. It has a static IP address and we have a range of IP address that we may use without NAT. I have established a static IP on the FE0 interface and setup NAT and DHCP for the local network, but it doesn't route to the internet. I need help.
My first question would be whether there was an appropriate default route on your router. My second question would be whether there is some problem in your address translation. We might find answers to these questions if you would post the config of the router.
Perhaps the question I should have asked, is "What are the basic steps to setup an 1811 router to use it behind an ISP router with a static IP?" I haven't been able to find any document that could tell me that, so I have just been taking shots in the dark and I appear to be missing the barn.
Perhaps we can start with some clarification. In your original post you say this:"It has a static IP address and we have a range of IP address that we may use without NAT". Can you clarify whether the addresses are an address for your interface and additional addresses in the same subnet that you can use. Or is it an address for your interface and a separate subnet of addresses that you can use (on your LAN perhaps)?
To answer your follow up question I would suggest that these are generally the steps in setting up a router to provide Internet access:
- configure appropriate addresses on the outside and inside interfaces of the router.
- verify that the router can ping the next hop gateway address (the ISP router).
- configure a default route with the ISP router as the next hop.
- determine whether you need to translate addresses on the inside. if you do need to translate addresses then configure address translation.
- verify whether the inside interface can access the ISP router (extended ping with inside interface as source address) or whether some PC connected to the inside interface can ping the ISP router. (verify that the ISP is routing back for the addresses on the inside interface.
- determine if you need restrictions on traffic from your network going to the Internet. If so then configure appropriate access lists and assign them to the interfaces.
- determine if you need restrictions on traffic from the Internet coming to you. If so then configure an appropriate access list and assign it to the outside inteface.
- verify whether the router is able to ping to addresses in the Internet (verify that the router traffic gets out and that responses are routed back.
- verify whether the router inside interface or PCs connected on the inside interface are able to access addresses in the Internet.
If you can not ping the ISP router or even the outside port then something is wrong. Is this router connected directly (physically) to the ISP router? Is it using straight through cable or cross over cable?
Perhaps it would help if you would post the output of show ip interface brief.
If you are doing DHCP using 192.168.x.x then I would expect the inside interface to be configured with a 192.168.x.y address. Perhaps you could post the DHCP config, the interface config for inside, and the NAT config?
Is your router directly connected to the ISP router, or is there a hub or switch in between? You say you cannot ping .29 which is the ISP router address. If you do a "Sh ip int brief", does your interface show the connection as up up?
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...