configuring cisco 1720 to work with broadband cable

Config is below... I can ping www.cisco.com, DHCP interally works fine, but can't get pc's to route out ethernet 0... I need some help


Building configuration...

Current configuration : 984 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname winebev-1720
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$SpK9$wUBMxRRsBzItXHg/Taxek1
!
memory-size iomem 25
no aaa new-model
ip subnet-zero
!
!
ip dhcp excluded-address 192.168.1.253
ip dhcp excluded-address 192.168.1.250
ip dhcp excluded-address 192.168.1.249
 --More--         !
ip dhcp pool 1
   network 192.168.1.0 255.255.255.0
   default-router 192.168.1.253
   lease 3
!
ip cef
!
!
!
!
interface Ethernet0
 ip address dhcp
 ip nat outside
 half-duplex
!
interface FastEthernet0
 ip address 192.168.1.253 255.255.255.0
 ip nat inside
 speed auto
!
ip nat inside source list 1 interface Ethernet0 overload
ip nat inside source list internal interface Ethernet0 overload
 --More--         ip classless
ip route 0.0.0.0 0.0.0.0 Ethernet0
ip route 192.168.0.0 255.255.0.0 Ethernet0
no ip http server
!
!
line con 0
line aux 0
line vty 0 4
 password
 login
!
end

youngm40Asked:
Who is Participating?
 
JFrederick29Connect With a Mentor Commented:
You are missing access-list 1 to define the traffic to be NAT'ed.

access-list 1 permit 192.168.1.0 0.0.0.255

As grblades suggests, the "ip route 192.168.0.0 255.255.0.0 Ethernet0" command is not necessary.  Should be removed.
0
 
grbladesConnect With a Mentor Commented:
Hi youngm40,
> ip route 192.168.0.0 255.255.0.0 Ethernet0
This is incorrect. The subnet mask should be 255.255.255.0. You are also routing it out the internet interface.
Should this line be there at all?
0
 
youngm40Author Commented:
I figured it out late on friday 8/27, and got it to work... I had to add... the following below...


ip nat inside source list 1 interface Ethernet0 overload
ip nat inside source route-map cable interface Ethernet0 overload
===== not exactly sure which one of the above lines made it work, but I can figure that out easily=== I just wanted to let you guys know what I did...


access-list 1 permit 192.168.1.0 0.0.0.255
route-map cable permit 10
 match ip address 1
 match interface Ethernet0

as well as to the ip dhcp pool 1
I added DNS-Server XXX.XXX.XXX.XXX



I removed

ip route 192.168.0.0 255.255.0.0 Ethernet0

because I knew that the ip route statement before that would encompass all traffic that comes in on the internal interface...

Thanks for all the help


0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.