Home > other >  The working principle of the routing table
The working principle of the routing table

Time:10-05

I have a questions about the routing table, the following is a routing table (routing table) example:


This is an example of network course exercises in actually, case said, network address 172.51.1.253 match option in the table line 5, and address 196.168.1.132 does not match any one line, my question is, why 172.51.1.253 match line 5? I tried the following operation, but can't come to the same network as the fifth row address (172.32.0.0) :

172.51.1.253=10101100, 00110011, 00000001, 11111101
Netmask=11111111, 11111000, 00000000, 00000000

AND=10101100, 00110000, 00000000, 00000000
The final results converted to decimal=172. 48. 0.0.
But this with the fifth line of the network address (172. 32. 0.0) is not the same! Then how 172.51.1.253 match the fifth line

CodePudding user response:

what's the use of this specific?

CodePudding user response:

Is to give a destination IP, choose the path from the routing table of the next branch address

CodePudding user response:

Obviously, the book write wrong,

CodePudding user response:

For the top!

CodePudding user response:

172.48.0.0. Is 172.32.0.0 subnet, so...

CodePudding user response:

CodePudding user response:



IP address, there are three blocks to be private:

1 -- 10.0.0.0, those
2 - along, 172.31.255.255
3 -- 192.168.0.0, 192.168.255.255

I saw there should be a book

CodePudding user response:

A good post for the top

CodePudding user response:

172.48.0.0 network is subnetwork of 172.32.0.0 network... So it is right!

CodePudding user response:

CodePudding user response:

Network segment 172.32.0.0 255.248.0.0
That is his address range
172.32.0.1-172.39.255.255

172.51.1.253 segment that does not belong to 172.32.0.0
Any rule does not match the routing table
Routing table didn't also the default routing
172.51.1.253 won't be routing

  • Related