1720 Bellsouth xDSL

Mar 31, 2005 4 Replies

I'm try to connect my Cisco 1720 to a Wintell xDSL modem through Bellsouth. I have a very simple setup with one dsl modem, my 1720 router and 1 pc.



Here is my setup:


************************* Wintell xDSL modem Internet IP = DHCP Local IP =192.168.1.254/24
*************************** Cisco 1720 WIC 1 Eth 0/0 =192.168.1.253/24 FastEthernet 0/0= 198.168.0.1/24
********************************* PC Static IP= 192.168.0.2/24 Gateway= 192.168.0.1 DNS= 192.168.0.1
*******************************


From the PC I can ping everything except the Wintell modem.


>From the 1720 I can ping everything including the PC and internet

addresses. I don't have passwords setup and security isn't a concern at this point.


Router#sh run Building configuration...


Current configuration : 780 bytes ! version 12.2 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Router ! ! memory-size iomem 15 mmi polling-interval 60 no mmi auto-configure no mmi pvc mmi snmp-timeout 180 ip subnet-zero ! ! ip name-server 192.168.1.254 ! ip ssh time-out 120 ip ssh authentication-retries 3 ! crypto mib ipsec flowmib history tunnel size 200 crypto mib ipsec flowmib history failure size 200 ! ! ! interface Ethernet0 ip address 192.168.1.253 255.255.255.0 half-duplex ! interface FastEthernet0 ip address 192.168.0.1 255.255.255.0 speed auto ! ip classless ip route 0.0.0.0 0.0.0.0 Ethernet0 ip route 192.168.1.254 255.255.255.255 Ethernet0 no ip http server ! ! ! line con 0 line aux 0 line vty 0 4 login line vty 5 15 login ! end

Do you have a static route in your Wintell for 192.168.0.0/24?

My guess is that the Wintell doesn't know about that subnet. If your wintell was a cisco the config would look similar to this...

ip route 192.168.0.0 255.255.255.0 192.168.1.253

-Dan

Could it have something to do with nat? I'm very new to cisoc and i've noticed almost all the online configs i've looked at have nat statements in them.

I don't think so....

What I think I'm seeing is that the Westell isn't aware of network

198.168.0.0/24. By default the westell routing table should only consist of two networks: the default or WAN(0.0.0.0) and the LAN(192.168.1.0/24). So what I think is happening is your pings are hitting the westell and the westell is responding to your WAN network instead of back towards your LAN network. You probably need a route statement pointing 198.168.0.0/24 towards your LAN.

-Dan

PS: sorry I'm so slow with responses. I only get to read NNTP every couple of days.

I figured it out. It was the nat statement. Thanks!

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required