Cisco 871w WAN connection problem

Unanswered Question
Aug 21st, 2007

Perhaps one of you experts can assist me with this problem: I've configured my 871W to get the LAN and wireless working without any problems. However, I'm now having trouble getting my WAN connection working. I've configured the WAN interface with the IP address from the ISP. I have the NAT translation from 192.168.69.0-192.168.69.255 to the first usable address in our IP block, which is 209.168.233.112(IP changed here for security reasons). They have given us a "block" of IPs, which ranges from x.x.x.110 to x.x.x.114. The first, is our actual address, x.x.x.110. The second is their gateway, x.x.x.111, or (according to them), the address of their ADTRAN router device, which is in front of ours on the the way to the Internet. I called them, and they stated that they do not have a NAT firewall in place on their router, and they are "just handing off the address to us". The Cisco device will replace a Linksys WRT54GL, which has a staic WAN IP of 209.168.233.112, and is using a gateway of 209.168.233.111. I'm not sure where to configure a gateway on the Cisco device, or if that's even possible. I asked the ISP if they have encountered a similar scenario, and they stated that most customers don't use sophisticted devices like Cisco, only devices like the Linksys router we currently have in place. They were little help except to clarify that they do not have a conflicting NAT in place on their router. I'm attaching my config. This was all done using the SDM. Any help is appreciated, thanks.

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jon Marshall Tue, 08/21/2007 - 12:48

Hi

I apprecaite you have changed the public IP address but .112 with a 255.255.255.248 subnet mask makes 209.168.233.112 the actual network address ie. it is not a useable IP address.

In addition if the ISP gateway was .111 this would be in a separate subnet.

I know you don't want to reveal your public IP addresses but could you confirm whether the last octet and subnet masks are representative of what you have on the router.

You do have a default route in your config ie.

ip route 0.0.0.0 0.0.0.0 FastEthernet4

although a more effecient default route would be

ip route 0.0.0.0 0.0.0.0 "ISP next hop address"

HTH

Jon

Pra3tor1an Tue, 08/21/2007 - 13:14

Yes, thanks for replying. The public IP given is not the actual, you are correct. Two other people have suggested the change:

ip route 0.0.0.0 0.0.0.0 209.168.233.XXX (next hop default gateway)

Do I need to get rid of the the "default-router 192.168.69.1" line in the config? Someone else suggested I do so.

Pra3tor1an Wed, 08/22/2007 - 13:32

Hey, Jon:

Your fix worked, thanks. I also had to delete the other route:

default-router 192.168.69.1

Actions

This Discussion