Gateway of last resort is not set...

MAC_Addy

I've been labbing for a little while now. I set my default route to ip route 0.0.0.0 0.0.0.0 e0

Now, when I go back and check sh ip route. I get the gateway of last resort is not set.

What do I need to change?

Also, just to let you know I'm just playing with my home cable modem, trying to get my 1710 router to be able to talk across the internet.

Excellent1

What routing protocol are you using?

MAC_Addy

I'm using RIP.

Excellent1

If you're using ripv2, maybe try disabling auto summary. I know sometimes default routes won't propogate using auto summary (ran into that recently), but you might post your config for more experienced folks to take a look at.

MAC_Addy

I did that. It works when I connect everything up to my home router (much appreciated by the way). But whenever I connect to my cable modem it loses everything and won't grab the DHCP from it.

Bl8ckr0uter

Is E0 up? Did you try ip default gateway? Sorry I meant default network.

Also check this out:

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094374.shtml

MAC_Addy

Yep. E0 is up. Status = UP protocol =UP. IP Address is unassigned.

The default network needs to be the link to FA0/0, correct?

Bl8ckr0uter

I dont know your topology but I think you probaby missing the ip default network command. Review the link I posted

cisco_trooper

MAC_Addy wrote: »

I did that. It works when I connect everything up to my home router (much appreciated by the way). But whenever I connect to my cable modem it loses everything and won't grab the DHCP from it.

Did you reboot the cable modem after you put the router in behind it? I don't know the technical term on the cable modems but I've seen plenty of them get ticked off and not hand out DHCP leases if the device behind it changes. Put the router behind it, reboot the modem, then reboot the router and take it from there.

MAC_Addy

cisco_trooper wrote: »

Did you reboot the cable modem after you put the router in behind it? I don't know the technical term on the cable modems but I've seen plenty of them get ticked off and not hand out DHCP leases if the device behind it changes. Put the router behind it, reboot the modem, then reboot the router and take it from there.

That worked. I appreciate it. I wouldn't have thought about rebooting my cable modem. This is definitely helping me learn though.

Here's a copy and paste from the router.

Router#sh run
Building configuration...

Current configuration : 944 bytes
!
! Last configuration change at 14:03:18 UTC Wed Nov 30 2011
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
memory-size iomem 15
no aaa new-model
ip subnet-zero
!
!
ip dhcp excluded-address 10.10.23.1 10.10.23.100
!
ip dhcp pool DHCP_POOL
network 10.10.23.0 255.255.255.0
default-router 10.10.23.1
dns-server 4.2.2.2 8.8.8.8
!
ip cef
!
!
!
!
interface Ethernet0
ip address dhcp
ip nat inside
no ip route-cache cef
no ip route-cache
half-duplex
!
interface FastEthernet0
ip address 10.10.23.1 255.255.255.0
ip nat inside
no ip route-cache cef
no ip route-cache
speed auto
!
ip nat inside source list 1 interface Ethernet0 overload
ip classless
ip http server
!
access-list 1 permit 10.10.23.0 0.0.0.255
!
line con 0
line aux 0
line vty 0 4
login
!
end