cant PING across serial link

[adfsadfafasf]

Newb Alert.

messing around with PT

connected a router, switch and pc (lets call this Westside)

connected a separate group consisting of also, one router, switch and one pc (Eastside)

connected routers with serial cable and can ping from end-to-end and all points in between

I added 3pcs on each end and created 3 VLANS on each end (10,20,30 on Westside and 40,50,60 on eastside)

configured router on a stick on each end and can ping from vlan to vlan but cannot ping from vlan any farther than the se2/0 on its local router. (i.e. cant ping remote router)

However, the first standalone pc that could ping end-to-end before I created vlans, still can.  

I have tried many things, including adding a default route (its not in current config) but to no avail.

Im pretty stubborn, but am going to have to breakdown and ask for help so I can sleep tonight. :)

wouldnt let me attach my packet tracer file.

Thanks 

[Georg Pauwen]

Hello,

rename the .pkt file to .jpg, you can then post it.

Or use pastebin.com...

[Georg Pauwen · Accepted solution]

Hello,

I added two default routes:

ip route 0.0.0.0 0.0.0.0 192.168.2.1

ip route 0.0.0.0 0.0.0.0 192.168.2.2

and end to end ping works. I have attached the working config...

[adfsadfafasf]

so i tried adding a route of 0.0.0.0 0.0.0.0 se2/0

when do i use the local serial inteface in the route and when do i use the ip?  i have researched but not found the answer. this is why i wanted to do it all statically to being to have a bettern understanding.  thank you VM.. do you know of a good place to read about different ways of doing static routes?

[Georg Pauwen]

Hello,

you use the local interface when you don't know the IP address of the next hop. This is typically the case when you connect to an ISP and get your IP address through DHCP (or ip address negotiated). In your case, on point to point serial links, you always know the IP address on the other side.

It doesn't really matter if you use the outgoing interface or the next hop IP address, the only difference is that when you use the local interface, the interface always needs to ARP for the IP address on the other side, which consumes resources and is considered less reliable...