Yes, I would agree with James that you first should look at the default
route and use a next hop as opposed to an interface (e0/0). Interface
in my experience should only be used on point-to-point links not
multiaccess links like what you have in this case (ethernet). In
addition to this, do you need to have an address pool for your NATing
if you are overloading? Could you not just use the "interface" keyword
so that all devices behind the 2600 at NATed to the IP of the external
2600 interface. Could test this by putting a computer on the network
between th 2600 and Linksys and set up a web server on it. See if you
can browse this serve then atleast. This will test your NATing, and
client default gateways etc are correct.
James wrote:
> Sorry ignore that you are NATing on the 2600.
>
> What happens if you change the default route on the 2600 to:-
>
> ip route 0.0.0.0 0.0.0.0 10.2.3.1
>
> wrote:
> > Hello I am trying to configure a Cisco 2611 router to connect to the
> > internet using a Linksys WRT54G as a border router. The reason I would
> > like to keep the linksys router on the outside of the Cisco router is
> > to prevent wireless clients from accessing my internal network but
> > allow them access to the internet. When I use the Config posted below
> > I am able to ping both interfaces on the 2611, and both interfaces on
> > the Linksys router out to the external interface but I am not able to
> > get out to the internet. I am some what new to Cisco routers so any
> > help with the Config would be much appreciated.
> >
> > The internal network IP is 192.168.x
> > The network in between the Cisco router and Linksys router is 10.2.3.x
> > with the internal interface on the Linksys router being 10.2.3.1 and
> > the external interface on the Cisco router being 10.2.3.5
> > The internet connection has a DHCP assigned address
> >
> > Using 896 out of 29688 bytes
> > !
> > version 12.3
> > service timestamps debug datetime msec
> > service timestamps log daletime msec
> > no service password-encryption
> > !
> > hostname Router
> > !
> > boot-start-marker
> > boot-end-marker
> > !
> > !
> > no aaa new-model
> > ip subnet-zero
> > ip cef
> > !
> > !
> > !
> > ip audit po max-events 100
> > !
> > !
> > interface Ethernet0/0
> > description WAN
> > ip address 10.2.3.5 255.255.255.0
> > ip nat outside
> > full-duplex
> > !
> > interface Ethernet0/1
> > description LAN
> > ip address 192.168.1.1 255.255.255.0
> > ip nat inside
> > full-duplex
> > !
> > ip nat pool crossbones 10.2.3.1 10.2.3.254 netmask 255.255.255.0
> > ip nat inside source list 7 pool crossbones overload
> > ip http server
> > no ip http secure-server
> > ip classless
> > ip route 0.0.0.0 0.0.0.0 Ethernet0/0
> > !
> > !
> > access-list 7 permit 192.168.1.0 0.0.0.255
> > access-list 7 permit 10.0.0.0 0.255.255.255
> > dialer-list 1 protocol ip permit
> > !
> > !
> >
> > line con 0
> > line aux 0
> > line vty 0 4
> > login
> > !
> > !
> > end