Protocol-type based local Policy Routing configuration Experiment

"Topology and software used"

The switch used in this paper is H3C Simulator, the download address is as follows: Http://forum.h3c.com/forum.php? Mod=viewthread&tid=109740&highlight=h3c%e6%a8%a1%e6%8b%9f%e5%99%a8 interested friends can download on the forum

Demand

R1 respectively and R2,R3, such as the above figure directly connected, R2 and R3 routing is not up to, through the policy route control from the R1 sent messages, all TCP messages are sent through the serial port s0/6/0, other messages still follow the way to find the routing table forwarding

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Network/lyjs/

Configuration

R1:

#

ACL number 3101

Rule 0 Permit TCP

#

Interface serial0/6/0

Link-protocol PPP

IP address 10.1.1.1 255.255.255.0

#

Interface SERIAL0/6/1

Link-protocol PPP

IP address 10.1.2.1 255.255.255.0

#

Policy-based-route 123 Permit Node 5

If-match ACL 3101

Apply Output-interface serial0/6/0

R2:

Telnet Server Enable

Interface serial0/6/0

Link-protocol PPP

IP address 10.1.1.2 255.255.255.0

#

User-interface Con 0

User-interface vty 0 4

Authentication-mode None

R3:

#

Telnet Server Enable

#

Interface SERIAL0/6/1

Link-protocol PPP

IP address 10.1.2.2 255.255.255.0

#

User-interface Con 0

User-interface vty 0 4

Authentication-mode None

"Result Validation"

1, first from R1 local ICMP message:

<r1>ping 10.1.1.2

PING 10.1.1.2:56 Data bytes, press Ctrl_c to break

Reply from 10.1.1.2:bytes=56 sequence=1 ttl=255 time=10 ms

Reply from 10.1.1.2:bytes=56 sequence=2 ttl=255 time=14 ms

Reply from 10.1.1.2:bytes=56 sequence=3 ttl=255 time=25 ms

Reply from 10.1.1.2:bytes=56 sequence=4 ttl=255 time=26 ms

Reply from 10.1.1.2:bytes=56 sequence=5 ttl=255 time=10 ms

---10.1.1.2 ping statistics---

5 packet (s) transmitted

5 packet (s) received

0.00% Packet Loss

Round-trip Min/avg/max = 10/17/26 ms

<r1>ping 10.1.2.2

PING 10.1.2.2:56 Data bytes, press Ctrl_c to break

Request Time Out

Reply from 10.1.2.2:bytes=56 sequence=2 ttl=255 time=30 ms

Reply from 10.1.2.2:bytes=56 sequence=3 ttl=255 time=1 ms

Reply from 10.1.2.2:bytes=56 sequence=4 ttl=255 time=10 ms

Reply from 10.1.2.2:bytes=56 sequence=5 ttl=255 time=10 ms

---10.1.2.2 ping statistics---

5 packet (s) transmitted

4 packet (s) received

20.00% Packet Loss

Round-trip Min/avg/max = 1/12/30 ms

The above information shows ICMP message normal forwarding, routing up to

2. Send TCP message locally from R1

<r1>tel

<r1>telnet 10.1.1.2

Trying 10.1.1.2 ...

Press Ctrl+k to abort

Connected to 10.1.1.2 ...

******************************************************************************

* Copyright (c) 2004-2007 Hangzhou h3c Tech. Co., Ltd.  All rights reserved. *

* Without the owner ' s prior written consent, *

* No decompiling or reverse-engineering shall be allowed. *

******************************************************************************

<R2>

<R2>

<R2>

<R2>

<R2>

<R2>

<r2>qu

The connection was closed by the remote host!

<r1>telnet 10.1.2.2

Trying 10.1.2.2 ...

Press Ctrl+k to abort

Can ' t connect to the remote host! Not Up!!

<R1>

<R1>

<R1>

As on the information, from the R1 TCP message (telnet) can be to R2, but not up to R3 because all TCP packets from the s0/6/0 issued, so only to reach the s0/6/0 directly with the R2, access to R3.

This article is from the "It Positive Energy" blog, please be sure to keep this source http://kuangweidong.blog.51cto.com/3272922/1142658