Results 1 to 6 of 6

Thread: Routing between RIPv1 & RIPv2

  1. #1
    themask Guest

    Default Routing between RIPv1 & RIPv2

    sh run
    Building configuration...

    Current configuration:
    !
    version 12.0
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    !
    hostname singapore
    !
    !
    ip subnet-zero
    !
    !
    !
    !
    !
    interface Loopback0
    ip address 192.168.3.1 255.255.255.0
    no ip directed-broadcast
    !
    interface Ethernet0
    no ip address
    no ip directed-broadcast
    shutdown
    !
    interface Serial0
    ip address 192.168.240.1 255.255.255.252
    no ip directed-broadcast
    no ip mroute-cache
    no fair-queue
    clockrate 64000
    !
    interface Serial1
    ip address 192.168.224.1 255.255.255.252
    no ip directed-broadcast
    clockrate 64000
    !
    interface BRI0
    no ip address
    no ip directed-broadcast
    shutdown
    !
    router rip
    version 2
    network 192.168.3.0
    network 192.168.224.0
    network 192.168.240.0
    !
    ip classless
    !
    !
    line con 0
    transport input none
    line aux 0
    line vty 0 4
    !
    end

    singapore#
    singapore#
    singapore#
    singapore#sh ipro   route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
    U - per-user static route, o - ODR

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial1
    192.168.240.0/30 is subnetted, 1 subnets
    C 192.168.240.0 is directly connected, Serial0
    R 192.168.252.0/24 [120/1] via 192.168.240.2, 00:00:17, Serial0
    C 192.168.3.0/24 is directly connected, Loopback0
    singapore#
    singapore#
    singapore#
    singapore#
    singapore#
    singapore#
    singapore#
    sanjose3#
    sanjose3#
    sanjose3#sh run
    Building configuration...

    Current configuration:
    !
    version 12.1
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    !
    hostname sanjose3
    !
    !
    !
    !
    !
    !
    ip subnet-zero
    no ip domain-lookup
    !
    !
    !
    !
    interface Loopback0
    ip address 192.168.1.3 255.255.255.0
    !
    interface Ethernet0
    ip address 200.200.50.2 255.255.255.0
    !
    interface Serial0
    ip address 192.168.224.2 255.255.255.252
    !
    interface Serial1
    no ip address
    shutdown
    !
    router rip
    version 1
    network 192.168.1.0
    network 192.168.224.0
    !
    ip classless
    ip http server
    !
    !
    line con 0
    logging synchronous
    transport input none
    line aux 0
    line vty 0 4
    login
    !
    end

    sanjose3#
    sanjose3#
    sanjose3#
    sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    C 200.200.50.0/24 is directly connected, Ethernet0
    C 192.168.1.0/24 is directly connected, Loopback0
    sanjose3#
    sanjose3#
    sanjose3#
    auckland#
    auckland#
    auckland#
    auckland#sh run
    Building configuration...

    Current configuration:
    !
    version 12.0
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    !
    hostname auckland
    !
    !
    ip subnet-zero
    !
    !
    !
    !
    !
    interface Loopback0
    ip address 192.168.252.1 255.255.255.0
    no ip directed-broadcast
    !
    interface Ethernet0
    no ip address
    no ip directed-broadcast
    shutdown
    !
    interface Serial0
    ip address 192.168.240.2 255.255.255.252
    no ip directed-broadcast
    no ip mroute-cache
    no fair-queue
    !
    interface Serial1
    no ip address
    no ip directed-broadcast
    shutdown
    !
    interface BRI0
    no ip address
    no ip directed-broadcast
    shutdown
    !
    router rip
    version 2
    network 192.168.240.0
    network 192.168.252.0
    !
    ip classless
    !
    !
    line con 0
    transport input none
    line aux 0
    line vty 0 4
    !
    end

    auckland#
    auckland#
    auckland#
    auckland#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
    U - per-user static route, o - ODR

    Gateway of last resort is not set

    R 192.168.224.0/24 [120/1] via 192.168.240.1, 00:00:17, Serial0
    192.168.240.0/30 is subnetted, 1 subnets
    C 192.168.240.0 is directly connected, Serial0
    C 192.168.252.0/24 is directly connected, Loopback0
    R 192.168.3.0/24 [120/1] via 192.168.240.1, 00:00:17, Serial0
    auckland#
    auckland#
    auckland#
    auckland#








    sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
    U - per-user static route, o - ODR

    Gateway of last resort is not set

    R 192.168.224.0/24 [120/1] via 192.168.240.1, 00:00:21, Serial0
    192.168.240.0/30 is subnetted, 1 subnets
    C 192.168.240.0 is directly connected, Serial0
    R 192.168.1.0/24 [120/2] via 192.168.240.1, 00:00:22, Serial0
    C 192.168.252.0/24 is directly connected, Loopback0
    R 192.168.3.0/24 [120/1] via 192.168.240.1, 00:00:22, Serial0
    auckland#
    auckland#
    auckland#
    auckland#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    C 200.200.50.0/24 is directly connected, Ethernet0
    C 192.168.1.0/24 is directly connected, Loopback0
    sanjose3#
    sanjose3#
    sanjose3#
    sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
    U - per-user static route, o - ODR

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial1
    192.168.240.0/30 is subnetted, 1 subnets
    C 192.168.240.0 is directly connected, Serial0
    R 192.168.1.0/24 [120/1] via 192.168.224.2, 00:00:09, Serial1
    R 192.168.252.0/24 [120/1] via 192.168.240.2, 00:00:00, Serial0
    C 192.168.3.0/24 is directly connected, Loopback0
    singapore#
    singapore#
    singapore#
    singapore#
    sanjose3#debug ip rip
    RIP protocol debugging is on
    sanjose3#clear ip route *
    sanjose3#
    00:35:18: RIP: sending request on Loopback0 to 255.255.255.255
    00:35:18: RIP: sending request on Serial0 to 255.255.255.255
    sanjose3#
    00:35:20: RIP: sending v1 flash update to 255.255.255.255 via Loopback0 (192.168.1.3)
    00:35:20: RIP: build flash update entries
    00:35:20: network 192.168.224.0 metric 1
    00:35:20: RIP: sending v1 flash update to 255.255.255.255 via Serial0 (192.168.224.2)
    00:35:20: RIP: build flash update entries
    00:35:20: network 192.168.1.0 metric 1
    sanjose3#
    00:35:28: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.1.3)
    00:35:28: RIP: build update entries
    00:35:28: network 192.168.224.0 metric 1
    00:35:28: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.224.2)
    00:35:28: RIP: build update entries
    00:35:28: network 192.168.1.0 metric 1
    00:35:29: RIP: ignored v2 packet from 192.168.224.1 (illegal version)
    sanjose3#
    sanjose3#
    sanjose3#
    sanjose3#un all
    All possible debugging has been turned off
    sanjose3#
    sanjose3#



    RIP illegal version




    sanjose3#
    sanjose3#
    sanjose3#conf t
    Enter configuration commands, one per line. End with CNTL/Z.
    sanjose3(config)#int s0
    sanjose3(config-if)#ip rip re
    sanjose3(config-if)#ip rip receive ver
    sanjose3(config-if)#ip rip receive version 2
    sanjose3(config-if)#^Z
    sanjose3#
    sanjose3#
    sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    C 200.200.50.0/24 is directly connected, Ethernet0
    C 192.168.1.0/24 is directly connected, Loopback0
    sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    C 200.200.50.0/24 is directly connected, Ethernet0
    C 192.168.1.0/24 is directly connected, Loopback0
    sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    R 192.168.240.0/24 [120/1] via 192.168.224.1, 00:00:00, Serial0
    C 200.200.50.0/24 is directly connected, Ethernet0
    C 192.168.1.0/24 is directly connected, Loopback0
    R 192.168.252.0/24 [120/2] via 192.168.224.1, 00:00:00, Serial0
    R 192.168.3.0/24 [120/1] via 192.168.224.1, 00:00:00, Serial0
    sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    R 192.168.240.0/24 [120/1] via 192.168.224.1, 00:00:04, Serial0
    C 200.200.50.0/24 is directly connected, Ethernet0
    C 192.168.1.0/24 is directly connected, Loopback0
    R 192.168.252.0/24 [120/2] via 192.168.224.1, 00:00:04, Serial0
    R 192.168.3.0/24 [120/1] via 192.168.224.1, 00:00:04, Serial0
    sanjose3#


    RIP1 & RIP2 can't understand eachother.

  2. #2

    Default Re: Routing between RIPv1 & RIPv2

    Sanjose3: RIP ver 1
    Singapore: RIP ver 2
    Auckland: RIP ver 2

    Sanjose3#clea ip route *
    Sanjose3#
    00:36:59: RIP: sending general request on Loopback0 to 255.255.255.255
    00:36:59: RIP: sending general request on Loopback0 to 224.0.0.9
    00:36:59: RIP: sending general request on Serial0 to 255.255.255.255
    00:36:59: RIP: sending general request on Serial0 to 224.0.0.9
    00:36:59: RIP: ignored v2 packet from 192.168.1.3 (sourced from one of our addresses)
    00:36:59: RIP: received v2 update from 192.168.224.1 on Serial0
    00:36:59: 192.168.3.0/24 -> 0.0.0.0 in 1 hops
    00:36:59: 192.168.240.0/24 -> 0.0.0.0 in 1 hops
    00:36:59: 192.168.252.0/24 -> 0.0.0.0 in 2 hops
    00:36:59: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.1.3)
    00:36:59: network 192.168.224.0, metric 1
    00:36:59: network 192.168.240.0, metric 2
    00:36:59: network 192.168.252.0, metric 3
    00:36:59: network 192.168.3.0, metric 2
    00:36:59: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.224.2)
    00:36:59: network 192.168.1.0, metric 1
    00:37:04: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.1.3)
    00:37:04: network 192.168.224.0, metric 1
    00:37:04: network 192.168.240.0, metric 2
    00:37:04: network 192.168.252.0, metric 3
    00:37:04: network 192.168.3.0, metric 2
    00:37:04: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.224.2)
    00:37:04: network 192.168.1.0, metric 1
    00:37:15: RIP: received v2 update from 192.168.224.1 on Serial0
    00:37:15: 192.168.3.0/24 -> 0.0.0.0 in 1 hops
    00:37:15: 192.168.240.0/24 -> 0.0.0.0 in 1 hops
    00:37:15: 192.168.252.0/24 -> 0.0.0.0 in 2 hops
    00:37:33: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.1.3)
    00:37:33: network 192.168.224.0, metric 1
    00:37:33: network 192.168.240.0, metric 2
    00:37:33: network 192.168.252.0, metric 3
    00:37:33: network 192.168.3.0, metric 2
    00:37:33: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.224.2)
    00:37:33: network 192.168.1.0, metric 1
    Sanjose3#
    Sanjose3#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
    U - per-user static route, o - ODR

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    R 192.168.240.0/24 [120/1] via 192.168.224.1, 00:00:04, Serial0
    C 192.168.1.0/24 is directly connected, Loopback0
    R 192.168.252.0/24 [120/2] via 192.168.224.1, 00:00:04, Serial0
    R 192.168.3.0/24 [120/1] via 192.168.224.1, 00:00:04, Serial0
    Sanjose3#
    Singapore#
    00:33:37: RIP: ignored v1 packet from 192.168.224.2 (illegal version)
    00:33:43: RIP: received v2 update from 192.168.240.2 on Serial1
    00:33:43: 192.168.252.0/24 via 0.0.0.0 in 1 hops
    00:33 RIP: sending v2 update to 224.0.0.9 via Loopback0 (192.168.3.1)
    00:33 RIP: build update entries
    00:33 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0
    00:33 192.168.224.0/24 via 0.0.0.0, metric 1, tag 0
    00:33 192.168.240.0/24 via 0.0.0.0, metric 1, tag 0
    00:33 192.168.252.0/24 via 0.0.0.0, metric 2, tag 0
    00:33 RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.224.1)
    00:33 RIP: build update entries
    00:33 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
    00:33 192.168.240.0/24 via 0.0.0.0, metric 1, tag 0
    00:33 192.168.252.0/24 via 0.0.0.0, metric 2, tag 0
    00:33 RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.240.1)
    00:33 RIP: build update entries
    00:33 192.168.1.0/24 via 0.0.0.0, metric 2, tag 0
    00:33 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
    00:33 192.168.224.0/24 via 0.0.0.0, metric 1, tag 0
    00:33 RIP: ignored v2 packet from 192.168.3.1 (sourced from one of our addresses)
    Singapore#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    192.168.240.0/30 is subnetted, 1 subnets
    C 192.168.240.0 is directly connected, Serial1
    R 192.168.252.0/24 [120/1] via 192.168.240.2, 00:00:03, Serial1
    C 192.168.3.0/24 is directly connected, Loopback0
    Singapore#
    Kết luận:
    Sanjose3, chạy RIP ver 1, chấp nhận quảng bá & cập nhật RIP ver 2
    Singapore, chạy RIP ver 2, không chấp nhận cập nhật RIP ver 1


    Routing between RIP v1 and RIP v2:
    Singapore: RIP ver 2, receive RIP ver 1

    Singapore(config)#int s0
    Singapore(config-if)#ip rip receive ver 1
    Singapore(config-if)#^Z
    Singapore#clear ip route *
    Singapore#
    01:04:59: RIP: sending request on Loopback0 to 224.0.0.9
    01:04:59: RIP: sending request on Serial0 to 224.0.0.9
    01:04:59: RIP: sending request on Serial1 to 224.0.0.9
    01:04:59: RIP: ignored v2 packet from 192.168.3.1 (sourced from one of our addresses)
    01:04:59: RIP: received v2 update from 192.168.240.2 on Serial1
    01:04:59: 192.168.252.0/24 via 0.0.0.0 in 1 hops
    Singapore#
    01:05:01: RIP: sending v2 flash update to 224.0.0.9 via Loopback0 (192.168.3.1)
    01:05:01: RIP: build flash update entries
    01:05:01: 192.168.224.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:01: 192.168.240.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:01: 192.168.252.0/24 via 0.0.0.0, metric 2, tag 0
    01:05:01: RIP: sending v2 flash update to 224.0.0.9 via Serial0 (192.168.224.1)
    01:05:01: RIP: build flash update entries
    01:05:01: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:01: 192.168.240.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:01: 192.168.252.0/24 via 0.0.0.0, metric 2, tag 0
    01:05:01: RIP: sending v2 flash update to 224.0.0.9 via Serial1 (192.168.240.1)
    Singapore#
    01:05:01: RIP: build flash update entries
    01:05:01: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:01: 192.168.224.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:01: RIP: ignored v2 packet from 192.168.3.1 (sourced from one of our addresses)
    Singapore#
    01:05:03: RIP: sending v2 update to 224.0.0.9 via Loopback0 (192.168.3.1)
    01:05:03: RIP: build update entries
    01:05:03: 192.168.224.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:03: 192.168.240.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:03: 192.168.252.0/24 via 0.0.0.0, metric 2, tag 0
    01:05:03: RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.224.1)
    01:05:03: RIP: build update entries
    01:05:03: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:03: 192.168.240.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:03: 192.168.252.0/24 via 0.0.0.0, metric 2, tag 0
    01:05:03: RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.240.1)
    01:05:03: RIP: build update entries
    01:05:03: 192.168.3.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:03: 192.168.224.0/24 via 0.0.0.0, metric 1, tag 0
    01:05:03: RIP: ignored v2 packet from 192.168.3.1 (sourced from one of our addresses)
    Singapore#
    01:05:09: RIP: received v2 update from 192.168.240.2 on Serial1
    01:05:09: 192.168.252.0/24 via 0.0.0.0 in 1 hops
    Singapore#sh ip route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
    E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
    i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route

    Gateway of last resort is not set

    192.168.224.0/30 is subnetted, 1 subnets
    C 192.168.224.0 is directly connected, Serial0
    192.168.240.0/30 is subnetted, 1 subnets
    C 192.168.240.0 is directly connected, Serial1
    R 192.168.1.0/24 [120/1] via 192.168.224.2, 00:00:02, Serial0
    R 192.168.252.0/24 [120/1] via 192.168.240.2, 00:00:08, Serial1
    C 192.168.3.0/24 is directly connected, Loopback0
    Singapore#
    Singapore chấp nhận RIP ver 1

  3. #3

    Default Re: Routing between RIPv1 & RIPv2

    Thân mời số đông thành viên tham gia thảo luận về kết luận dưới đây của chipchip và themask:

    Kết luận:
    Sanjose3, chạy RIP ver 1, chấp nhận quảng bá & cập nhật RIP ver 2
    Singapore, chạy RIP ver 2, không chấp nhận cập nhật RIP ver 1


    Có ý kiến ngược lại như sau:

    RIP version 1 không hiểu và không chấp nhận RIP version 2.
    RIP version 2 hiểu và chấp nhận cập nhật RIP version 1.

    Ý kiến của các bạn thế nào?

    Xin cám ơn,
    Viet Professionals Co. Ltd. VnPro ®
    ---------------------------------------
    149/1D Ung Văn Khiêm P25 Q.Bình thạnh TPHCM
    Tel: (08) 35124257 (7 lines)
    Fax: (08) 5124314
    Support forum: http://vnpro.org
    LiveChat : http://www.vnpro.vn/support
    Blog VnPro : http://vnpro.org/blog
    Forum Wifi : http://wifipro.org

  4. #4
    tuaninbox Guest

    Default Re: Routing between RIPv1 & RIPv2

    Xin chào,

    Ý kiến của em là:

    Rip v 2 nhận update v1 và v2, gửi v2
    Rip v 1 nhận update v1, gửi v1

    Từ đó có thể lý giải cấu hình của themask như sau:

    SanJose3 không hiểu v2 update từ Sing do Sing gởi v2 mà SanJ chỉ hiểu được v1

    sanjose3#
    00:35:28: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.1.3)
    00:35:28: RIP: build update entries
    00:35:28: network 192.168.224.0 metric 1
    00:35:28: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.224.2)
    00:35:28: RIP: build update entries
    00:35:28: network 192.168.1.0 metric 1
    00:35:29: RIP: ignored v2 packet from 192.168.224.1 (illegal version)
    sanjose3#
    themask đã cấu hình cho SanJ hiểu v2 bằng lệnh: ip rip receive version 2. Lệnh này nói rằng rip sẽ chỉ hiểu v2 update trên int s0. Bài toán đã được giải quyết.

    Tuy nhiên, theo debug của anh chip thì Sing (chạy v2) lại không hiểu v1 update từ SanJose (chạy v1). Không biết cấu hình của anh chip có giống 100% cấu hình của themask?

  5. #5
    danguyennhi Guest

    Default

    Hi,

    Sỡ dĩ RIP v.1 không thể hiểu và chấp nhận RIP v.2 update là do trong RIP update của version 2 có dùng thêm một số field. Các field này không thể xử lý bởi các routers chạy RIP v.1

    mến,

  6. #6
    leminhkhoi Guest

    Default

    chào,

    Rip v 2 nhận update v1 và v2, gửi v2 ,V1
    Rip v 1 nhận update v1, gửi v1
    Theo mình nghĩ là vậy.

Similar Threads

  1. [Dùng GNS3}ISCW LAB: MPLS VPN ROUTING VRF
    By tranmyphuc in forum ISCW
    Replies: 21
    Last Post: 04-06-2012, 02:58 PM
  2. Tips for CCIE Candidate
    By binhhd in forum CCIE Routing & Switching
    Replies: 10
    Last Post: 22-04-2009, 02:01 PM
  3. Routing TCP/IP Vol 1 Notes
    By tranmyphuc in forum CCIE Routing & Switching
    Replies: 11
    Last Post: 04-08-2008, 04:04 PM
  4. Policy Routing - Dung thuc te cua Nachi Worm
    By ccie2467 in forum CCIE Security
    Replies: 0
    Last Post: 24-08-2003, 09:51 PM
  5. Replies: 3
    Last Post: 13-08-2003, 10:41 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
 
   TRUNG TÂM TIN HỌC VNPRO
149/1D Ung Văn Khiêm, P. 25, Q.Bình Thạnh
Phone:(08) 35124257
Fax: (08) 35124314
Email: vnpro@vnpro.org
Powered by vBulletin Version 4.2.1
Copyright 2000 - 2011, Jelsoft Enterprises Ltd.
License owned by : VietProfessional Co.,Ltd
 

Ve may bay |Ve may bay gia re |Ve may bay di Ha Noi |Ve may bay di Nha Trang |Ve may bay di Da Nang |Ve may bay di Da Lat |Ve may bay di Vinh |Ve may bay di Hue |Ve may bay di Con Dao |Ve may bay di TP HCM |Air Asia |Tiger Airways |Vietnam Airlines |Lion Air |Aeroflot |Jetstar |Vietjet Air |Asiana |Delta Airlines |Singapore Airlines |Thai Airways |quantas |Turkish Airlines |China Southern Airlines |Air China |Ve may bay gia re |Ve may bay di Anh |Ve may bay di Canada |Ve may bay di Ha Lan |Ve may bay di Han Quoc |Ve may bay di Hong Kong |Ve may bay di Y |Ve may bay di Italia |Ve may bay di Malaysia |Ve may bay di Nga |Ve may bay di Phap |Ve may bay di Philippines |Ve may bay di Singapore |Ve may bay di Thai Lan |Ve may bay di Trung Quoc |Ve may bay di Uc |Ve may bay di Ukraina |Ve may bay di Duc |Ve may bay di My |Ve may bay di My