How to properly configure RIP when WAN interface is DHCP

I have a Cisco 1841 connected to my ISP with the WAN port configured for DHCP.  I have a /30 subnet with public addresses (no NAT) configured on my LAN port.  I'm having trouble configuring RIP to advertise this local subnet to my ISP's upstream router.  I'm getting an IP from my ISP and from the router console I'm able to ping a host on the internet, however I'm unable to communicate with any host beyond my local 1841 router if attempted from a host on the LAN. The same solution works fine on a smaller residential  Linksys router with minimal effort.  Below is my current config.  Any help would be greatly appreciated.

interface FastEthernet0/0
 description LAN
 ip address 69.x.x.x 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet0/1
 description WAN
 ip address dhcp
 duplex auto
 speed auto
!
router rip
 redistribute connected

Open in new window

etcitAsked:
Who is Participating?
 
etcitConnect With a Mentor Author Commented:
I was finally able to get this working.  Below is the working RIP config that I've deployed for anyone that may encounter this problem in the future.

router rip
 version 2
 redistribute connected
 network 0.0.0.0
 default-metric 1
 no auto-summary

Open in new window



The key was the network 0.0.0.0 line.  This enables RIP advertisements on all interfaces.  If you want to suppress RIP messages on other interfaces just add passive-interface ifnumber to the RIP configuration.  Thanks everyone for your assistance.
0
 
Istvan KalmarHead of IT Security Division Commented:
Hi,

Only that you need to add route fast 0/1 interface:

ip route 0.0.0.0 0.0.0.0 fast 0/1
0
 
FWestonCommented:
ikalmar is correct.  RIP should provide a route, but I haven't seen any ISP use RIP in ages.  Usually they'll have a static route pointed to your WAN address for your /30 and you would just need to add a static default route as ikalmar has suggested.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
etcitAuthor Commented:
The default route is provided by my ISP via DHCP.  I know this is working because I'm able to communicate with hosts on the Internet from my router's console.  The reason for using RIP is due to the fact that the IP address on my router's WAN port is dynamic.  My ISP would have to update their static route any time the WAN IP on my router changes.  This scenario has worked flawlessly for months now over my Linksys router by simply enabling RIP.  I'm just looking to perform the same function with my $1000 Cisco 1841 that my $40 Linksys is doing :) I'm just missing something in my RIP configuration.
0
 
Istvan KalmarHead of IT Security Division Commented:
Please show:

sh ip route
sh ip proto
0
 
etcitAuthor Commented:
#sho ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 24.239.16.1 to network 0.0.0.0

     69.0.0.0/30 is subnetted, 1 subnets
C       69.85.108.128 is directly connected, FastEthernet0/0
     172.16.0.0/32 is subnetted, 1 subnets
S       172.16.254.6 [254/0] via 24.239.16.1, FastEthernet0/1
     24.0.0.0/20 is subnetted, 1 subnets
C       24.239.16.0 is directly connected, FastEthernet0/1
S*   0.0.0.0/0 [254/0] via 24.239.16.1


#sho ip proto
Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 30 seconds, next due in 0 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Redistributing: connected, rip
  Default version control: send version 1, receive any version
  Automatic network summarization is in effect
  Maximum path: 4
  Routing for Networks:
  Routing Information Sources:
    Gateway         Distance      Last Update
  Distance: (default is 120)

Open in new window

0
 
Marius GunnerudSenior Systems EngineerCommented:
you could issue the command default-information originate on your 1841 router under the rip process. This will tell all other neighboring rip processes to send traffic for unknown networks to that router.
0
 
etcitAuthor Commented:
Tried other suggestions but finally arrived at solution through my own testing efforts
0
All Courses

From novice to tech pro — start learning today.