cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1131
Views
0
Helpful
9
Replies

Cant see WAN gateway

zkartchner
Level 1
Level 1

Hello everyone, I have a cisco 3900 integrated services router. I am a little new to the cisco IOS. I am having an issue getting my LAN network to communicate with the WAN gateway. From hosts I can ping the interface IP address but not the gateway. I have used the default route command of IP route 0.0.0.0 0.0.0.0 [wan gateway from ISP] I have already set up NAT, DHCP, I just cant seem to get the internet working, the following is my config, any help would be appreciated.

version 15.1

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname tier3local

!

boot-start-marker

boot-end-marker

!

!

enable secret 5 $1$6/bs$GXiDaZSR8dA70Sn/fxcB7/

enable password cisco

!

no aaa new-model

!

!

crypto pki token default removal timeout 0

!

!

no ipv6 cef

ip source-route

no ip routing

no ip cef

!

!

!

!

ip dhcp pool DHCP_POOL

network 192.168.1.0 255.255.255.0

dns-server 68.105.28.11 68.105.29.11

default-router 192.168.1.1

lease infinite

!

!

!

multilink bundle-name authenticated

!

!

license udi pid C3900-SPE100/K9 sn FOC1634EV9M

!

!

!

redundancy

!

!

!

!

!

!

!

!

!

!

!

interface Embedded-Service-Engine0/0

no ip address

no ip route-cache

shutdown

!

interface GigabitEthernet0/0

ip address 24.249.174.157 255.255.255.240

ip nat outside

ip virtual-reassembly in

no ip route-cache

duplex auto

speed auto

no mop enabled

!

interface GigabitEthernet0/1

ip address 192.168.1.1 255.255.255.0

ip nat inside

ip virtual-reassembly in

no ip route-cache

shutdown

duplex auto

speed auto

!

interface GigabitEthernet0/2

no ip address

no ip route-cache

shutdown

duplex auto

speed auto

!

ip forward-protocol nd

!

no ip http server

no ip http secure-server

!

ip nat inside source list NAT_POOL interface GigabitEthernet0/0 overload

ip route 0.0.0.0 0.0.0.0 24.249.174.145

!

ip access-list standard NAT_POOL

permit 192.168.1.0 0.0.0.255

!

!

!

!

!

!

!

control-plane

!

!

!

line con 0

line aux 0

line 2

no activation-character

no exec

transport preferred none

transport input all

transport output pad telnet rlogin lapb-ta mop udptn v120 ssh

stopbits 1

line vty 0 4

password cisco

login

transport input all

!

scheduler allocate 20000 1000

end

9 Replies 9

John Blakley
VIP Alumni
VIP Alumni

Zach,

The only immediate thing that I see is that you inside interface is shut:

!

interface GigabitEthernet0/1

ip address 192.168.1.1 255.255.255.0

ip nat inside

ip virtual-reassembly in

no ip route-cache

shutdown

duplex auto

speed auto

Type in:

int g0/1

no shut

See if that helps..

HTH,
John

*** Please rate all useful posts ***

HTH, John *** Please rate all useful posts ***

Yes I turned that on. But from the cisco IOS i cant even ping the WAN gateway of 24.249.274.145 any thoughts?

You'll need to be able to do that first. Is the interface up/up? Do you have the correct addressing from the provider?

HTH,
John

*** Please rate all useful posts ***

HTH, John *** Please rate all useful posts ***

Hey

use this

no ip route 0.0.0.0 0.0.0.0 24.249.174.145

ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0

Well its owesome man

no ip routing

enable ip routing  using

ip routing

*** Do Rate All Helpful Posts***

Jawad

Hi,

yes turning ip routing on is indeed the solution but not changing the static route to point out a multipoint interface because it wouldn't be working if the gateway had proxy-arp disabled and it is not recommended to do so for performance.

Regards

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.

While I agree with everyone else on enabling routing, this would solve the natting issue. The OP stated that he couldn't ping the gateway from the router which doesn't require routing since it's a connected subnet. So, if the original problem of not being able to hit the gateway from the router is resolved then enabling routing will fix the natting issue but it will not fix the originally stated problem.

HTH,
John

*** Please rate all useful posts ***

HTH, John *** Please rate all useful posts ***

Thanks John. So knowing this after I have enabled IP routing what is the next step to getting the internet working for my LAN users? My ultimate goal is to just get the internet working...

Thanks!

Mar 14, 2013 12:26 AM (in response to John Blakley)

Cant see WAN gateway

Hey

use this

no ip route 0.0.0.0 0.0.0.0 24.249.174.145

ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0

Well its owesome man

no ip routing

enable ip routing  using

ip routing

*** Do Rate All Helpful Posts***

###############################################################################

Thanks I did that but now where do input the default gateway of 24.249.174.145 from my ISP so I can get the internet working on my LAN? I still can't ping it.

Hi,

leave the old static default route: ip route 0.0.0.0 0.0.0.0 24.249.174.145

and try pinging 8.8.8.8 from the router, maybe the ISP is filtering pings.

Regards

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.