Options

Question about connectivity

nice343nice343 Member Posts: 391
problem1.jpg

the network between the two routers is 192.168.2.0/24
R1 interface f0/0 is 192.168.2.2 and R2 interface f0/1 192.168.2.3

the network connecting to the LAN is 192.168.1.0/24. R2 f0/0 is 192.168.1.1

I have configured the switch with the "ip default-gateway 192.168.1.1" command and configured
Ip route 0.0.0.0 0.0.0.0 f0/1 on R2 but for some reason I still cannot ping 192.168.2.2 (R1) from the switch??? Am 1 doing something wrong?
My daily blog about IT and tech stuff
http://techintuition.com/

Comments

  • Options
    mikearamamikearama Member Posts: 749
    It's the default route... change it from

    Ip route 0.0.0.0 0.0.0.0 f0/1

    to

    Ip route 0.0.0.0 0.0.0.0 f0/0

    You have everything defaulting to away from the router... f0/0 will default everything to the router. That's the only way to cross subnets.
    There are only 10 kinds of people... those who understand binary, and those that don't.

    CCIE Studies: Written passed: Jan 21/12 Lab Prep: Hours reading: 385. Hours labbing: 110

    Taking a time-out to add the CCVP. Capitalizing on a current IPT pilot project.
  • Options
    NetstudentNetstudent Member Posts: 1,693 ■■■□□□□□□□
    You needa route back to the LAN. Sure the data can get there, but how will it get back? I think any one of those routes Mike suggested would work, they would just have a different AD. You still needa route on R2 pointing to your LAN subnet.
    There is no place like 127.0.0.1 BUT 209.62.5.3 is my 127.0.0.1 away from 127.0.0.1!
  • Options
    mikearamamikearama Member Posts: 749
    Hmmm, I like NS's idea better.
    There are only 10 kinds of people... those who understand binary, and those that don't.

    CCIE Studies: Written passed: Jan 21/12 Lab Prep: Hours reading: 385. Hours labbing: 110

    Taking a time-out to add the CCVP. Capitalizing on a current IPT pilot project.
  • Options
    nice343nice343 Member Posts: 391
    mikearama wrote:
    It's the default route... change it from

    Ip route 0.0.0.0 0.0.0.0 f0/1

    to

    Ip route 0.0.0.0 0.0.0.0 f0/0

    You have everything defaulting to away from the router... f0/0 will default everything to the router. That's the only way to cross subnets.

    I changed the deafult route on R2 to 1p route 0.0.0.0 0.0.0.0 192.168.2.2(next hop routerR1)
    My daily blog about IT and tech stuff
    http://techintuition.com/
  • Options
    nice343nice343 Member Posts: 391
    I tried using the f0/0 on the Ip route and it would not work
    My daily blog about IT and tech stuff
    http://techintuition.com/
  • Options
    bighornsheepbighornsheep Member Posts: 1,506
    nice343 wrote:
    I changed the deafult route to 1p route 0.0.0.0 0.0.0.0 192.168.2.2(next hop routerR1)

    it is till not working

    Make sure your switch has
    ip default-network 192.168.1.1
    

    and your R1 should have
    ip route 0.0.0.0 0.0.0.0 192.168.2.3
    

    Your R2 shouldn't have ANY default route.
    Jack of all trades, master of none
  • Options
    nice343nice343 Member Posts: 391
    nice343 wrote:
    I changed the deafult route to 1p route 0.0.0.0 0.0.0.0 192.168.2.2(next hop routerR1)

    it is till not working

    Make sure your switch has
    ip default-network 192.168.1.1
    

    and your R1 should have
    ip route 0.0.0.0 0.0.0.0 192.168.2.3
    

    Your R2 shouldn't have ANY default route.


    I already have this command on the switch
    ip default-network 192.168.1.1
    
    plus I don't want to create a default route on R1. I want the deafault route to be on R2
    My daily blog about IT and tech stuff
    http://techintuition.com/
  • Options
    NetstudentNetstudent Member Posts: 1,693 ■■■□□□□□□□
    R2 already knows about all the networks because they are directly connected. Thats why you don't need a route on R2. I don;t think it would hurt to put it in there anyways, especially if R1 was your edge router. Can you post the running-config?
    There is no place like 127.0.0.1 BUT 209.62.5.3 is my 127.0.0.1 away from 127.0.0.1!
  • Options
    bighornsheepbighornsheep Member Posts: 1,506
    nice343 wrote:
    and your R1 should have
    ip route 0.0.0.0 0.0.0.0 192.168.2.3
    

    Your R2 shouldn't have ANY default route.

    I don't want to create a default route on R1. I want the deafault route to be on R2

    You can configure whatever you want, but it won't work like you are expecting it to. Your switch (plus workstations connected to it) won't be able to ping R1, and other connections on R1 also will not be able to ping the switch and its devices unless you configure your routes properly. If you do not have a default route on R1, it the ping (and any packet in general) will fail on the return path because R1 doesn't know what to do with packets destined for 192.168.1.0/24

    The only reason you would configure a default route on R2 is if it connects to another network such as the internet.
    Jack of all trades, master of none
  • Options
    NetstudentNetstudent Member Posts: 1,693 ■■■□□□□□□□
    If you can ping R2's fa0/1 and not R1's fa0/0, then you know it is the route on R1. IF you cannot ping R2's fa0/1, then you have something else wrong that is not routing.
    There is no place like 127.0.0.1 BUT 209.62.5.3 is my 127.0.0.1 away from 127.0.0.1!
  • Options
    nice343nice343 Member Posts: 391
    Netstudent wrote:
    If you can ping R2's fa0/1 and not R1's fa0/0, then you know it is the route on R1. IF you cannot ping R2's fa0/1, then you have something else wrong that is not routing.

    I can ping R2 f0/1 and f0/0 from the switch

    I cannot ping R1 f0/0 from the switch
    My daily blog about IT and tech stuff
    http://techintuition.com/
  • Options
    NetstudentNetstudent Member Posts: 1,693 ■■■□□□□□□□
    One thing I will add, is that what you are trying to do should be done with static routes. You have a default route on R1 pointing toward the inside of the network. Usually default routes should point outside the network. R2 should have a default route pouinting to R1 and R1 should have a static route pointing to R2. Deconfigure the default route on R1 and use a static route like this

    ip route 192.168.1.0 255.255.255.0 192.168.2.3
    There is no place like 127.0.0.1 BUT 209.62.5.3 is my 127.0.0.1 away from 127.0.0.1!
  • Options
    nice343nice343 Member Posts: 391
    I already know I can accomplish connectivity using default routes on both routers but I was actually experimenting something.


    Thanks for your help anyway.
    My daily blog about IT and tech stuff
    http://techintuition.com/
Sign In or Register to comment.