Solved: how do you connect a cisco router to the internet through a cable modem/ router gateway - Page 6

breynold76 · ‎04-27-2013

I have searched on here but can't find the exact answer i am looking for. I have a cisco 1760 router and a 2950 switch. The router has an ethernet wic card added so i have two ethernet connections available. I would like to connect the cable modem gatway to the router through one of the ethernet connections on the router and then to the switch. I cannot seem to get this setup to work. There are several different ways i have seen posted to accomlish this. dhcp, no dhcp, creating a seperate network, and giving the e0/0 an ip address within the range of the cable gateways network addresses. None of this has worked. Can anybody post the commands that need to be entered on the router to make this possible?

Richard Burts · ‎04-29-2013

I went back and looked again at the debug output. And I noticed that we are debugging for server activity. But in our case the router is a dhcp client and not server. I suggest that we try a debug dhcp on the router and see what it tells us.

HTH

Rick

HTH

Rick

breynold76 · ‎04-29-2013

R1(config)#service ?

alignment Control alignment correction and logging

compress-config Compress the nvram configuration file

config TFTP load config files

dhcp Enable DHCP server and relay agent

disable-ip-fast-frag Disable IP particle-based fast fragmentation

exec-callback Enable exec callback

exec-wait Delay EXEC startup on noisy lines

finger Allow responses to finger requests

hide-telnet-addresses Hide destination addresses in telnet command

linenumber enable line number banner for each exec

nagle Enable Nagle's congestion control algorithm

old-slip-prompts Allow old scripts to operate with slip/ppp

pad Enable PAD commands

password-encryption Encrypt system passwords

prompt Enable mode specific prompt

pt-vty-logging Log significant VTY-Async events

sequence-numbers Stamp logger messages with a sequence number

slave-log Enable log capability of slave IPs

tcp-keepalives-in Generate keepalives on idle incoming network

connections

tcp-keepalives-out Generate keepalives on idle outgoing network

connections

tcp-small-servers Enable small TCP servers (e.g., ECHO)

telnet-zeroidle Set TCP window 0 when connection is idle

timestamps Timestamp debug/log messages

udp-small-servers Enable small UDP servers (e.g., ECHO)

R1(config)#service dhcp ?

R1#show version

Cisco Internetwork Operating System Software

IOS (tm) C1700 Software (C1700-IPBASE-M), Version 12.3(6a), RELEASE SOFTWARE (fc4)

Compiled Fri 02-Apr-04 20:22 by kellythw

Image text-base: 0x80008120, data-base: 0x80C73694

ROM: System Bootstrap, Version 12.2(7r)XM2, RELEASE SOFTWARE (fc1)

R1 uptime is 2 hours, 21 minutes

System returned to ROM by reload at 00:51:44 UTC Tue Jul 29 2008

System restarted at 00:43:19 UTC Tue Jul 29 2008

System image file is "flash:c1700-ipbase-mz.123-6a.bin"

cisco 1760 (MPC860P) processor (revision 0x500) with 55597K/9939K bytes of memory.

Processor board ID FOC08211BP4 (3060850850), with hardware revision 0000

MPC860P processor: part number 5, mask 2

Bridging software.

X.25 software, Version 3.0.0.

1 FastEthernet/IEEE 802.3 interface(s)

2 Low-speed serial(sync/async) network interface(s)

32K bytes of non-volatile configuration memory.

32768K bytes of processor board System flash (Read/Write)

Configuration register is 0x2142

breynold76 · ‎04-29-2013

R1#debug dhcp

DHCP client activity debugging is on

R1#

Jul 29 03:16:39.149: DHCP: Try 36 to acquire address for FastEthernet0/0

Jul 29 03:16:39.149: DHCP: allocate request

Jul 29 03:16:39.149: DHCP: new entry. add to queue

Jul 29 03:16:39.149: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:16:39.149: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:16:39.149: DHCP: SDiscover 294 bytes

Jul 29 03:16:39.149: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:16:42.150: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:16:42.150: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:16:42.150: DHCP: SDiscover 294 bytes

Jul 29 03:16:42.150: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:16:45.151: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:16:45.151: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:16:45.151: DHCP: SDiscover 294 bytes

Jul 29 03:16:45.151: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:16:59.539: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:17:29.540: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:17:59.541: DHCP: Try 37 to acquire address for FastEthernet0/0

Jul 29 03:17:59.541: DHCP: allocate request

Jul 29 03:17:59.541: DHCP: new entry. add to queue

Jul 29 03:17:59.541: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:17:59.541: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:17:59.541: DHCP: SDiscover 294 bytes

Jul 29 03:17:59.541: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:18:02.542: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:18:02.542: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:18:02.542: DHCP: SDiscover 294 bytes

Jul 29 03:18:02.542: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:18:05.543: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:18:05.543: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:18:05.543: DHCP: SDiscover 294 bytes

Jul 29 03:18:05.543: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:18:19.930: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:18:49.931: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:19:19.933: DHCP: Try 38 to acquire address for FastEthernet0/0

Jul 29 03:19:19.933: DHCP: allocate request

Jul 29 03:19:19.933: DHCP: new entry. add to queue

Jul 29 03:19:19.933: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:19:19.933: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:19:19.933: DHCP: SDiscover 294 bytes

Jul 29 03:19:19.933: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:19:22.934: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:19:22.934: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:19:22.934: DHCP: SDiscover 294 bytes

Jul 29 03:19:22.934: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:19:25.935: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:19:25.935: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:19:25.935: DHCP: SDiscover 294 bytes

Jul 29 03:19:25.935: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:19:40.326: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:20:10.327: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:20:40.328: DHCP: Try 39 to acquire address for FastEthernet0/0

Jul 29 03:20:40.328: DHCP: allocate request

Jul 29 03:20:40.328: DHCP: new entry. add to queue

Jul 29 03:20:40.328: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:20:40.328: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:20:40.328: DHCP: SDiscover 294 bytes

Jul 29 03:20:40.328: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:20:43.329: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:20:43.329: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:20:43.329: DHCP: SDiscover 294 bytes

Jul 29 03:20:43.329: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:20:46.330: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:20:46.330: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:20:46.330: DHCP: SDiscover 294 bytes

Jul 29 03:20:46.330: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:21:00.718: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:21:30.719: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:22:00.720: DHCP: Try 40 to acquire address for FastEthernet0/0

Jul 29 03:22:00.720: DHCP: allocate request

Jul 29 03:22:00.720: DHCP: new entry. add to queue

Jul 29 03:22:00.720: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:22:00.720: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:22:00.720: DHCP: SDiscover 294 bytes

Jul 29 03:22:00.720: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:22:03.721: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:22:03.721: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:22:03.721: DHCP: SDiscover 294 bytes

Jul 29 03:22:03.721: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:22:06.722: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:22:06.722: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:22:06.722: DHCP: SDiscover 294 bytes

Jul 29 03:22:06.722: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:22:21.110: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:22:51.111: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:23:21.112: DHCP: Try 41 to acquire address for FastEthernet0/0

Jul 29 03:23:21.112: DHCP: allocate request

Jul 29 03:23:21.112: DHCP: new entry. add to queue

Jul 29 03:23:21.112: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:23:21.112: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:23:21.112: DHCP: SDiscover 294 bytes

Jul 29 03:23:21.112: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:23:24.113: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:23:24.113: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:23:24.113: DHCP: SDiscover 294 bytes

Jul 29 03:23:24.113: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:23:27.114: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:23:27.114: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:23:27.114: DHCP: SDiscover 294 bytes

Jul 29 03:23:27.114: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:23:41.501: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:24:11.503: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:24:41.504: DHCP: Try 42 to acquire address for FastEthernet0/0

Jul 29 03:24:41.504: DHCP: allocate request

Jul 29 03:24:41.504: DHCP: new entry. add to queue

Jul 29 03:24:41.504: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:24:41.504: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:24:41.504: DHCP: SDiscover 294 bytes

Jul 29 03:24:41.504: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:24:44.505: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:24:44.505: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:24:44.505: DHCP: SDiscover 294 bytes

Jul 29 03:24:44.505: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:24:47.506: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:24:47.506: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:24:47.506: DHCP: SDiscover 294 bytes

Jul 29 03:24:47.506: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:25:01.893: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:25:31.894: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:26:01.896: DHCP: Try 43 to acquire address for FastEthernet0/0

Jul 29 03:26:01.896: DHCP: allocate request

Jul 29 03:26:01.896: DHCP: new entry. add to queue

Jul 29 03:26:01.896: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:26:01.896: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:26:01.896: DHCP: SDiscover 294 bytes

Jul 29 03:26:01.896: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:26:04.897: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:26:04.897: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:26:04.897: DHCP: SDiscover 294 bytes

Jul 29 03:26:04.897: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:26:07.897: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:26:07.897: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:26:07.897: DHCP: SDiscover 294 bytes

Jul 29 03:26:07.897: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:26:22.289: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Richard Burts · ‎04-29-2013

Thanks for posting these outputs. I do not see any other global configuration option that looks like it would be helpful.

There are some differences between the output of show interface and of show ip interface. Would you post the output of show ip interface fa0/0?

Can you do another test with the router connected to the cable modem, configured for DHCP and run the debug dhcp command?

HTH

Rick

HTH

Rick

breynold76 · ‎04-29-2013

R1#show ip int fa0/0

FastEthernet0/0 is up, line protocol is up

Internet address will be negotiated using DHCP

Broadcast address is 255.255.255.255

MTU is 1500 bytes

Helper address is not set

Directed broadcast forwarding is disabled

Outgoing access list is not set

Inbound access list is not set

Proxy ARP is enabled

Local Proxy ARP is disabled

Security level is default

Split horizon is enabled

ICMP redirects are always sent

ICMP unreachables are always sent

ICMP mask replies are never sent

IP fast switching is enabled

IP fast switching on the same interface is disabled

IP Flow switching is disabled

IP CEF switching is enabled

IP CEF Fast switching turbo vector

IP multicast fast switching is enabled

IP multicast distributed fast switching is disabled

IP route-cache flags are Fast, CEF

Router Discovery is disabled

IP output packet accounting is disabled

IP access violation accounting is disabled

TCP/IP header compression is disabled

RTP/IP header compression is disabled

Policy routing is disabled

Network address translation is disabled

WCCP Redirect outbound is disabled

WCCP Redirect inbound is disabled

WCCP Redirect exclude is disabled

BGP Policy Mapping is disabled

R1#debug dhcp

DHCP client activity debugging is on

R1#

Jul 29 03:37:35.396: DHCP: deleting entry 8177944C 0.0.0.0 from list

Jul 29 03:38:05.398: DHCP: Try 52 to acquire address for FastEthernet0/0

Jul 29 03:38:05.398: DHCP: allocate request

Jul 29 03:38:05.398: DHCP: new entry. add to queue

Jul 29 03:38:05.398: DHCP: SDiscover attempt # 1 for entry:

Jul 29 03:38:05.398: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:38:05.398: DHCP: SDiscover 294 bytes

Jul 29 03:38:05.398: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:38:08.399: DHCP: SDiscover attempt # 2 for entry:

Jul 29 03:38:08.399: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:38:08.399: DHCP: SDiscover 294 bytes

Jul 29 03:38:08.399: B'cast on FastEthernet0/0 interface from 0.0.0.0

Jul 29 03:38:11.399: DHCP: SDiscover attempt # 3 for entry:

Jul 29 03:38:11.399: DHCP: SDiscover: sending 294 byte length DHCP packet

Jul 29 03:38:11.399: DHCP: SDiscover 294 bytes

Jul 29 03:38:11.399: B'cast on FastEthernet0/0 interface from 0.0.0.0%Unknown DHCP problem.. No allocation possible

Jul 29 03:38:25.779: DHCP: Waiting for 60 seconds on interface FastEthernet0/0

Jul 29 03:38:55.780: DHCP: deleting entry 8177944C 0.0.0.0 from list

R1#no debug all

All possible debugging has been turned off

Richard Burts · ‎04-29-2013

Thank you for the additional outputs. I do not see anything significantly different in the show ip interface output (it all looks quite normal and like the DHCP should work).

The debug dhcp output is quite interesting and I believe useful. The most significant part seems to be this

from 0.0.0.0%Unknown DHCP problem.. No allocation possible

So it looks like the router is sending DHCP requests and for some reason the cable modem is not allocating an address. So it looks like we need to look into the cable modem for the explanation of why it is not working.

Is it possible that its address pool is exhausted? Is there some other limitation set up in its configuration?

HTH

Rick

HTH

Rick

Bilal Nawaz · ‎04-29-2013

I think it's quite clear and comprehensive that the router is trying to obtain an IP. But it can't. Hence I posted some options we could take a look at on the modem and web links on how we could possibly tweak the modem settings... Where to start with the options though...

Sent from Cisco Technical Support iPhone App

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

breynold76 · ‎04-29-2013

the address pool should not be exhausted. i have about 6-7 devices on the network. i am not sure what changes i would need to make in the router gui interface to allow this.

Richard Burts · ‎04-29-2013

I agree that figuring where to start is a challenge.

I am not familiar with this model of cable modem and I wonder if there is any kind of log or any status screen where it might indicate why it is rejecting the request from the router?

HTH

Rick

HTH

Rick

Richard Burts · ‎04-29-2013

The manual in the link that was posted says that there is a status screen and that from the status screen that you can view event logs. I would ask that you see if you can get to the status screen and check the event logs. I would hope that they would have some indication of what it has been doing and the reason why it did not assign an address in response to the router request.

HTH

Rick

HTH

Rick

breynold76 · ‎04-29-2013

Status

SNMP Event Log help

This page displays the contents of the SNMP event log.

Time	Priority	Description
Time Not Established	Warning (5)	ToD request sent - No Response received;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Error (4)	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Error (4)	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Error (4)	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Warning (5)	ToD request sent - No Response received;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Bilal Nawaz · ‎04-30-2013

Hello Bernard, This is really interesting here.... The logs are displaying:

MAC=7c:bf:b1:b7:31:6b - Motorola

MAC=00:1b:54:c9:0a:8b - Cisco router

I cant quite make out what the logs say, but its definitely about DHCP WARNING

DHCP WARNING - Non-critical field invalid in response ;CM-MAC=7c:bf:b1:b7:31:6b;CMTS-MAC=00:1b:54:c9:0a:8b;CM-QOS=1.0;CM-VER=3.0;

I have no idea what this means though! any thoughts?

If we cant get anything working here, we could try bridged mode? Just seems like the motorola is not happy with the router being plugged in. Interesting post is here:

http://www.broadbandreports.com/forum/r27015950-TWC-How-to-run-a-Motorola-SBG6580-in-Bridge-mode.

Which suggests the modem/router does something funny with mac addresses. The author of the post explains really well what we can achieve with bridged mode and how to get to that stage. I think if we want this cisco router set up to work, perhaps this is the only option?

Please rate useful posts and remember to mark any solved questions as answered. Thank you.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

breynold76 · ‎04-30-2013

I went to the link and followed the instructions.

There is no rg passthrough option so I could not change that setting.

When i change all the other settings exept for NAPT the modem still functions and i can still ping it from the cisco router.

When i disable NAPT mode the ping from the cisco router to the modem fails. It locks up the modem and i cannot access the modem interface any longer and must do a factory reset on the modem to get it functional again.

I have spent many hours searching this and cannot even find someone else with the same problem. This setup is for a home lab to prepare for the ccna exam. is internet connectivity vital to lab work or can i get by without it?

breynold76 · ‎04-30-2013

Got internet up and running through the cisco router. Somebody posted that they could not get their server to work with the motorola gateway so they changed the dns server to the modems ip address 192.168.0.1. That worked for me. Here is the router on a stick with modifications that i entered.

R1#show run

Building configuration...

Current configuration : 1575 bytes

!

! Last configuration change at 04:34:10 UTC Wed Jul 30 2008

!

version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname R1

!

boot-start-marker

boot-end-marker

!

no logging console

!

mmi polling-interval 60

no mmi auto-configure

no mmi pvc

mmi snmp-timeout 180

no aaa new-model

ip subnet-zero

ip cef

!

ip dhcp excluded-address 192.168.1.0 192.168.1.99

ip dhcp excluded-address 192.168.0.0 255.255.255.0

ip dhcp excluded-address 192.168.0.0 192.168.0.99

!

ip dhcp pool MY_LAN

network 192.168.0.0 255.255.255.0

default-router 192.168.0.1

dns-server 192.168.0.1

!

ip name-server 24.217.0.5

ip name-server 8.8.8.8

ip name-server 192.168.0.1

no ftp-server write-enable

!

interface FastEthernet0/0

no ip address

speed auto

!

interface FastEthernet0/0.1

description ##my lan##

encapsulation dot1Q 1 native

ip address 192.168.1.1 255.255.255.0

ip nat inside

!

interface FastEthernet0/0.100

description ##internet##

encapsulation dot1Q 100

ip address 192.168.0.101 255.255.255.0

ip access-group MY_WAN in

ip nat outside

!

interface Serial0/0

no ip address

shutdown

!

interface Serial0/1

no ip address

shutdown

!

ip nat inside source list MY_LAN interface FastEthernet0/0.100 overload

ip classless

no ip http server

!

ip access-list standard MY_LAN

permit 192.168.1.0 0.0.0.255

!

ip access-list extended MY_WAN

permit tcp any any established

deny tcp any any

permit ip any any

!

line con 0

password cisco

login

line aux 0

line vty 0 4

password cisco

login

!

end

Richard Burts · ‎04-30-2013

I am glad that you have the Internet access working now. I would like to have figured out how to have the router learn its IP address as other devices do. But we worked so hard on that without success and using a static address on the router is an adequate work around. So congratulations on getting it to work.

HTH

Rick

HTH

Rick