2nd Static IP addressing Issue - Please Help

sandman420 · ‎02-11-2009

I'm a little confused with something. I've got one of these routers (Cisco 1760 onboard fa0/0 and 1 ea. FXO, FXS) on-site now (I've completed voip config - just need to set with static ips and then play with the VPN). I've got the other at the office obtaining a DHCP WAN IP, and the second is on-site behind a Centurytel westell wireless router/modem. The modem has had firewall off and the public LAN enabled, which allows multiple static WAN IPs to be addressed to equipment behind the westell modem/router.

The problem is, is that the Cisco is not getting out to the internet, nor can internet access the router. When I configure my laptop nic with the same settings, everything works fine. There is nothing in the westell that is blocking anything, so I don't understand this. 1st router with 1st IP, along with the computers on the 1st LAN are able to ping the Cisco with 2nd IP, and the Cisco is able to ping its default-gateway, which is the 1st router/1st IP address, but cannot get past the 1st router, and nothing from the internet trying to access the 2nd IP can get past the 1st router.

Here's the IP configs:

Westell Modem/Router

IP: 66.112.75.5

Netmask: 255.255.255.252

Cisco Interface Fa 0/0:

IP: 66.112.75.6

Netmask: 255.255.255.252

IP default-gateway 66.112.75.5 & IP route 0.0.0.0 0.0.0.0 Fa 0/0 Have both been tried.

I've got the 2nd Cisco router, back at the office, right now accessible from the internet and has internet access on the fa 0/0 int using DHCP.

I'm pretty sure this has to be some count of IP route problem. I saw in the IP route table of the 2nd router at the shop, that it added a static route to another network via fa 0/0, which I can only assume is the multicast network that our cable modem is connected to. I'm wondering if the same would have to be added for the 1st Cisco with the 2nd static IP from the DSL connection?

Here's the table from the first router:

Gateway of last resort is 24.206.255.1 to network 0.0.0.0

172.24.0.0/32 is subnetted, 1 subnets

S 172.24.120.69 [254/0] via 24.206.255.1, FastEthernet0/0

24.0.0.0/24 is subnetted, 1 subnets

C 24.206.255.0 is directly connected, FastEthernet0/0

C 192.168.1.0/24 is directly connected, Loopback1

S* 0.0.0.0/0 [1/0] via 24.206.255.1

AND HERE'S THE TABLE FROM THE 2ND ROUTER:

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

C 192.168.10.0/24 is directly connected, Loopback1

66.0.0.0/30 is subnetted, 1 subnets

C 66.112.75.4 is directly connected, FastEthernet0/0

S* 0.0.0.0/0 is directly connected, FastEthernet0/0

I've also just tried to give the int fa 0/0 a private LAN address here, and assign default route to fa 0/0 and default-gateway to 192.168.1.1 (westell router) and still the same thing is happening. I don't understand this. It's not like the interface is bad or anything, and before I left the office with this, it was connected to that cable connection and obtaining a DHCP and everything works fine there. I know this has to be something really simple like a route or something. I thought it might have had something to do with the VPN config that I had started, and so I removed the crypto map from the fa 0/0 int, but still no go.

Anyway...I thought I'd include the config for this setup (being on the private LAN):

Giuseppe Larosa · ‎02-12-2009

Hello Mark,

try to use

ip route 0.0.0.0 0.0.0.0 66.112.75.5

with your current configuration you are relying on proxy-arp: on the willingness of westell router to answer to arbitrary ARP requests.

by the way:

sh ip route shows ip routing is enabled so the command

IP default-gateway 66.112.75.5

is useless

Hope to help

Giuseppe

Richard Burts · ‎02-12-2009

Giuseppe

I would suggest that useless is perhaps a bit strong. I agree that with IP routing enabled that it is not used. But it might be cheap and effective insurance if the router ever starts acting as an IP host - if there were a problem with the image and it booted into rommon for instance.

HTH

Rick

HTH

Rick

sandman420 · ‎02-12-2009

Giuseppe,

What would make the difference between my laptop and the router? If it works with my laptop, wouldn't that mean that the westell is answering the ARP requests? I'll try that route though, and let you know.

Thank you

Mark

sandman420 · ‎02-12-2009

I can't believe it. That was exactly it. I don't know why, but I guess I tried that address with the ip default-gateway, thinking that I had already put it in the ip route and never did. Thank you soo much.

On a side note, however, I did try to setup the router on the LAN and get dhcp, then configure port routing in the westell router to send tcp h.323 signaling and udp h.323 voice ports, and everything was working, except that the DTMF was not being passed. I am curious as to why that setup did not work. I was using "TCP port 1720 for signaling, and UDP 16384-32767 for audio" that was provided to me by another post. I did a debug dialpeer and got this:

Sigma#debug voip dialpeer

voip dialpeer default debugging is on

Sigma#

*Apr 22 13:07:28.360: //-1/D10699B58047/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=190, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Apr 22 13:07:28.360: //-1/D10699B58047/DPM/dpAssociateIncomingPeerCore:

Result=NO_MATCH(-1) After All Match Rules Attempt

*Apr 22 13:07:28.360: //-1/D10699B58047/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=190, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

Sigma#

*Apr 22 13:07:28.364: //-1/D10699B58047/DPM/dpAssociateIncomingPeerCore:

Result=NO_MATCH(-1) After All Match Rules Attempt

*Apr 22 13:07:28.380: //-1/D10699B58047/DPM/dpMatchPeersCore:

Calling Number=, Called Number=190, Peer Info Type=DIALPEER_INFO_SPEECH

*Apr 22 13:07:28.380: //-1/D10699B58047/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=190

*Apr 22 13:07:28.380: //-1/D10699B58047/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

*Apr 22 13:07:28.380: //-1/D10699B58047/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=190

Sigma#

*Apr 22 13:07:32.703: //-1/D39E8738804A/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=191, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

*Apr 22 13:07:32.703: //-1/D39E8738804A/DPM/dpAssociateIncomingPeerCore:

Result=NO_MATCH(-1) After All Match Rules Attempt

*Apr 22 13:07:32.707: //-1/D39E8738804A/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=191, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

Sigma#

*Apr 22 13:07:32.707: //-1/D39E8738804A/DPM/dpAssociateIncomingPeerCore:

Result=NO_MATCH(-1) After All Match Rules Attempt

*Apr 22 13:07:32.719: //-1/D39E8738804A/DPM/dpMatchPeersCore:

Calling Number=, Called Number=191, Peer Info Type=DIALPEER_INFO_SPEECH

*Apr 22 13:07:32.719: //-1/D39E8738804A/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=191

*Apr 22 13:07:32.719: //-1/D39E8738804A/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

*Apr 22 13:07:32.723: //-1/D39E8738804A/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=191

Thank you again,

Mark