TCP/IP 5.3.4不连续的子网和无类别路由选择
生活随笔
收集整理的這篇文章主要介紹了
TCP/IP 5.3.4不连续的子网和无类别路由选择
小編覺得挺不錯的,現在分享給大家,幫大家做個參考.
5.3.4 不連續的子網和無類別路由選擇<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 溫習:有類別路由選擇:在邊界路由器上的路由匯總 處在兩個主網絡邊界上的路由器不會把其中一個主網絡的子網通告給另一個主網。 看圖
RIPV2在缺省情況下是會在主網絡邊界上進行路由匯總的 但是這里可以關閉這個功能no auto-summary
?
?
還有之前看到的不連續子網的問題,在RIPV1的時候 那個時候是用輔助地址的方法來解決的 現在路由協議能支持不連續子網,就可以解決這個問題了,不要用輔助地址的方式來解決 即是VLSM也是不連續子網 配置和net文件在附件里面呀?
用RIPV2的方式來看 第一、不能讓她在主網絡邊界上進行路由匯總,VLSM對他沒有影響,子網能夠過去了。 第二、RIPV2是無類別路由選擇協議,他會在目的地址和所有已知路由之間逐位執行最佳匹配。不連續對他沒有影響。?
(有類:就是按照IP地址的分類來分類了,無類就是沒有IP地址類別這個概念僅僅是逐位執行最佳匹配)?
查看RIP v2路由表 2個10段的子網是認出來了。知道該怎么走的?
在RIPV1的時候 是這個情況 有類路由就是這樣的 2個子網被他認成是一個網段?
?
?
?
?
?
?
現在來配置 VER2 Andy#debug ip rip RIP protocol debugging is on Andy# *Apr 19 23:33:26.147: RIP: sending v2 update to 224.0.0.9 via Loopback0 (192.168.12.65) *Apr 19 23:33:26.147: RIP: build update entries *Apr 19 23:33:26.151:?? 10.33.0.0/20 via 0.0.0.0, metric 2, tag 0 *Apr 19 23:33:26.151:?? 192.168.12.192/27 via 0.0.0.0, metric 1, tag 0 *Apr 19 23:33:26.155:?? 192.168.83.0/24 via 0.0.0.0, metric 1, tag 0 *Apr 19 23:33:26.155: RIP: ignored v2 packet from 192.168.12.65 (sourced from one of our addresses) *Apr 19 23:33:26.499: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (192.168.12.195) *Apr 19 23:33:26.499: RIP: build update entries *Apr 19 23:33:26.503:?? 10.33.0.0/20 via 0.0.0.0, metric 2, tag 0 *Apr 19 23:33:26.503:?? 192.168.12.64/27 via 0.0.0.0, metric 1, tag 0 *Apr 19 23:33:26.507:?? 192.168.83.0/24 via 0.0.0.0, metric 1, tag 0 Andy# *Apr 19 23:33:31.615: RIP: received v2 update from 192.168.12.196 on FastEthernet0/1 *Apr 19 23:33:31.619:????? 10.33.32.0/20 via 0.0.0.0 in 1 hops Andy# *Apr 19 23:33:33.619: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/1 (192.168.12.195) *Apr 19 23:33:33.619: RIP: build flash update entries - suppressing null update *Apr 19 23:33:33.623: RIP: sending v2 flash update to 224.0.0.9 via Loopback0 (192.168.12.65) *Apr 19 23:33:33.623: RIP: build flash update entries *Apr 19 23:33:33.627:?? 10.33.32.0/20 via 0.0.0.0, metric 2, tag 0 *Apr 19 23:33:33.627: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/0 (192.168.83.1) *Apr 19 23:33:33.631: RIP: build flash update entries *Apr 19 23:33:33.631:?? 10.33.32.0/20 via 0.0.0.0, metric 2, tag 0 Andy# *Apr 19 23:33:33.639: RIP: ignored v2 packet from 192.168.12.65 (sourced from one of our addresses) Andy# *Apr 19 23:33:40.199: RIP: received v2 update from 192.168.83.244 on FastEthernet0/0 *Apr 19 23:33:40.203:????? 10.33.0.0/20 via 0.0.0.0 in 1 hops Andy#un all All possible debugging has been turned off?
?
VER1 Andy#debug ip rip RIP protocol debugging is on Andy# *Apr 19 23:37:02.427: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.1) *Apr 19 23:37:02.427: RIP: build update entries *Apr 19 23:37:02.431:?? network 10.0.0.0 metric 2 *Apr 19 23:37:02.431:?? network 192.168.12.0 metric 1 Andy# *Apr 19 23:37:10.487: RIP: sending v1 update to 255.255.255.255 via Loopback0 (192.168.12.65) *Apr 19 23:37:10.487: RIP: build update entries *Apr 19 23:37:10.491:?? network 10.0.0.0 metric 2 *Apr 19 23:37:10.491:?? subnet 192.168.12.192 metric 1 *Apr 19 23:37:10.491:?? network 192.168.83.0 metric 1 Andy# *Apr 19 23:37:11.731: RIP: received v1 update from 192.168.12.196 on FastEthernet0/1 *Apr 19 23:37:11.735:????? 10.0.0.0 in 1 hops Andy# *Apr 19 23:37:12.995: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/1 (192.168.12.195) *Apr 19 23:37:12.995: RIP: build update entries *Apr 19 23:37:12.999:?? network 10.0.0.0 metric 2 *Apr 19 23:37:12.999:?? subnet 192.168.12.64 metric 1 *Apr 19 23:37:13.003:?? network 192.168.83.0 metric 1 *Apr 19 23:37:13.735: RIP: sending v1 flash update to 255.255.255.255 via FastEthernet0/1 (192.168.12.195) *Apr 19 23:37:13.735: RIP: build flash update entries - suppressing null update *Apr 19 23:37:13.739: RIP: sending v1 flash update to 255.255.255.255 via Loopback0 (192.168.12.65) *Apr 19 23:37:13.739: RIP: build flash update entries - suppressing null update Andy# *Apr 19 23:37:13.743: RIP: sending v1 flash update to 255.255.255.255 via FastEthernet0/0 (192.168.83.1) *Apr 19 23:37:13.747: RIP: build flash update entries - suppressing null update Andy# *Apr 19 23:37:18.591: RIP: received v1 update from 192.168.83.244 on FastEthernet0/0 *Apr 19 23:37:18.595:????? 10.0.0.0 in 1 hops Andy# *Apr 19 23:37:30.723: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.1) *Apr 19 23:37:30.723: RIP: build update entries *Apr 19 23:37:30.723:?? network 10.0.0.0 metric 2 *Apr 19 23:37:30.723:?? network 192.168.12.0 metric 1 Andy#un all All possible debugging has been turned off?
華麗麗的對比 這個是RIPV2的其中的一條信息 *Apr 19 23:33:33.627: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/0 (192.168.83.1) *Apr 19 23:33:33.631: RIP: build flash update entries *Apr 19 23:33:33.631:?? 10.33.32.0/20 via 0.0.0.0, metric 2, tag 0?
這個是RIPV1其中的一條信息 *Apr 19 23:37:02.427: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.83.1) *Apr 19 23:37:02.427: RIP: build update entries *Apr 19 23:37:02.431:?? network 10.0.0.0 metric 2轉載于:https://blog.51cto.com/2065130/841821
總結
以上是生活随笔為你收集整理的TCP/IP 5.3.4不连续的子网和无类别路由选择的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: MySQL之权限索引学习整理
- 下一篇: applyDimension的用法