3560 Can't ping my gateway.

[Deepseadata]

I can ping the gateway 192.168.15.254 from inside the router.
I can ping clients on both of my test Vlans from inside the router.
I can ping from client to client 172.16.50.2 to 172.16.70.2
I can ping from client to the 3560's routed interface 192.168.15.250
I can not ping from client to 192.168.15.254 (ADSL modem)

I must me missing something... Can someone be so kind and have a quick look for me as I research what's going wrong?

Thanks!

AmeviCoreSwitch#sh run
Building configuration...

Current configuration : 4495 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname AmeviCoreSwitch
!
!
no aaa new-model
ip subnet-zero
ip routing
ip name-server 192.168.15.254
ip dhcp excluded-address 172.16.50.1
ip dhcp excluded-address 172.16.10.1
ip dhcp excluded-address 172.16.20.1
ip dhcp excluded-address 172.16.30.1
ip dhcp excluded-address 172.16.40.1
ip dhcp excluded-address 172.16.60.1
ip dhcp excluded-address 172.16.70.1
ip dhcp excluded-address 172.16.80.1
ip dhcp excluded-address 172.16.90.1
!
ip dhcp pool vlan5
import all
network 172.16.50.0 255.255.255.0
netbios-name-server 172.16.50.250
domain-name MotorYachtAmevi.local
default-router 172.16.50.1
dns-server 192.168.15.254
lease 8
!
ip dhcp pool vlan7
import all
network 172.16.70.0 255.255.255.0
default-router 172.16.70.1
dns-server 192.168.15.254
lease 8
!
!
!
!
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
!
interface FastEthernet0/1
description Management port
no switchport
no ip address
!
interface FastEthernet0/2
switchport access vlan 2
!
interface FastEthernet0/3
switchport access vlan 2
!
interface FastEthernet0/4
switchport access vlan 2
!
interface FastEthernet0/5
switchport access vlan 2
!
interface FastEthernet0/6
switchport access vlan 5
!
interface FastEthernet0/7
switchport access vlan 5
!
interface FastEthernet0/8
switchport access vlan 5
!
interface FastEthernet0/9
switchport access vlan 5
!
interface FastEthernet0/10
switchport access vlan 4
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0/11
switchport access vlan 4
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0/12
switchport access vlan 4
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0/13
switchport access vlan 4
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0/14
switchport access vlan 4
!
interface FastEthernet0/15
!
interface FastEthernet0/16
switchport access vlan 6
!
interface FastEthernet0/17
description AMS Port
switchport access vlan 8
!
interface FastEthernet0/18
description Vid Conferencing Port
switchport access vlan 9
!
interface FastEthernet0/19
switchport access vlan 9
!
interface FastEthernet0/20
switchport access vlan 10
!
interface FastEthernet0/21
switchport access vlan 5
!
interface FastEthernet0/22
switchport access vlan 8
!
interface FastEthernet0/23
!
interface FastEthernet0/24
switchport access vlan 10
!
interface FastEthernet0/25
switchport access vlan 7
!
interface FastEthernet0/26
!
interface FastEthernet0/43
!
interface FastEthernet0/44
!
interface FastEthernet0/45
!
interface FastEthernet0/46
!
interface FastEthernet0/47
!
interface FastEthernet0/48
description Gateway to Selector
no switchport
ip address 192.168.15.250 255.255.255.0
!
interface GigabitEthernet0/1
!
interface GigabitEthernet0/2
!
interface GigabitEthernet0/3
!
interface GigabitEthernet0/4
!
interface Vlan1
description Switches
ip address 172.16.10.1 255.255.255.0
!
interface Vlan2
description Cameras
ip address 172.16.20.1 255.255.255.0
!
interface Vlan3
description CCTV Clients
ip address 172.16.30.1 255.255.255.0
!
interface Vlan4
description WAPs
ip address 172.16.40.1 255.255.255.0
!
interface Vlan5
description Office
ip address 172.16.50.1 255.255.255.0
!
interface Vlan6
description Crestron
ip address 172.16.60.1 255.255.255.0
!
interface Vlan7
description Guests
ip address 172.16.70.1 255.255.255.0
!
interface Vlan8
description Service
no ip address
!
interface Vlan9
description AMS
no ip address
!
interface Vlan10
description Vid Conf
no ip address
!
router eigrp 1
network 192.168.15.0
network 172.16.50.0
network 172.16.70.0
auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.15.250
ip http server
!
!
control-plane
!
line con 0
line vty 0 4
no login
line vty 5 15
no login
!
end

AmeviCoreSwitch#

 

[dgrizzard]

Does your ADSL modem have routes to get back to your clients?

 

[Deepseadata]

Nope.

All I did was put an IP address on its LAN interface so I'd have something to ping. I then put a couple PC's on two switchport acccess ports.

I just recently reviewed cisco's inter-vlan routing config guide and I've copied it to the T... still nothing.

Do I need to put something in there for the inbound routing?

 

[Deepseadata]

Whoops. I notice I said I could ping from inside the "router"... please replace that word with "switch."

Sorry about the confusion.

Kelley

 

[dgrizzard]

Your ADSL modem would need a route to know how to get to your client networks. From the modem's perspective it only knows about the internet (from the service provider) and your 192.168.15.0/24 network. It does not know how to get to 172.16.50.0 or 172.16.70.0 to reply to the pings.

When you are pinging from the switch it is using your 192.168.15.250 address the switch has, which the modem can reply to.

 

[Deepseadata]

I guess the next question is, how to get things to work? Hehehe.

Usually when I setup a network I setup the WAN int with a static or dhcp for the ISP side. Then I give it a LAN IP and give my clients that LAN IP as their gateway... job done.

I've never had to create anything for stuff coming back in... but I clearly do not know enough.

It sounds like I'm supposed to put a gateway address in the modem (that I'm just using as something on that routed switch port) for incoming traffic from the modem.

 

[dgrizzard]

If the modem has the ability to add static routes then just add one saying anything bound for 172.16.50.0/24 or .70.0/24 go to 192.168.15.250. You can't do NAT on this switch so that would be your only option. The other option is not use multiple subnets and have everything on the 192.168.15.0/24 subnet.

 

[Deepseadata]

Whoa!

Are you telling me that \i'm screwed unless I have a device where I can add a static route back to my switch?

I don't know why I figured I could just use a routing protocol and add the all the subnets hoping that they'd now all be able to find each other. Then read the cisco inter-vlan routing article and decided to use a static route instead. But it sounds like that's only a oneway street.

The last option you mentioned.. did you mean I could leave it all on the 192.168.15.0 but use didn't subnet masks to split it?

Now I'm worried that I don't have enough hardware!

 

[dgrizzard]

If you're ADSL modem doesn't have the ability to input static routes then it doesn't know how to get back to your client networks. The easiest solution is to put everything on on the same VLAN/subnet, change your port to the modem back to a regular switch port and place it on the same VLAN.

Otherwise you would need a router and then place the DSL modem in passthrough/brige mode and connect it to that router.

 

[Deepseadata]

This might sound desperate but.. what if I put a Pix 501 between the switch and the modem?

 

[dgrizzard]

It would work, but then you will be doing double NAT, you will be NAT'ing on the DSL modem and then NAT'ing on the Pix 501, the way you currently have it setup.

If you want to place a Pix 501 in the mix, then still place the dsl modem in passthrough/bridge mode, then the Pix501 will receive the outside internet address. You can contact your provider if you're not sure how to do this and they should be able to step you through it (the DSL modem configuration that is).

 

[Deepseadata]

Thanks for all the input!

It turns out that I can do static routes on the modem.

I'm going to use your advice and plug some routes in there.

Thanks!

 

[Deepseadata]

I added these static routes to the modem:

destination 172.16.50.0/24 can be found at 192.168.15.254
and
destination 172.16.70.0/24 can be found at 192.168.15.254

Worked like a charm. Thanks people!

I hope this helps someone else down the road.