Network requirements – H3C Technologies H3C SR8800 User Manual
Page 406
390
# Telnet to Router B (1::2/64) from Router A. The operation succeeds.
<RouterA> telnet ipv6 1::2
Trying 1::2 ...
Press CTRL+K to abort
Connected to 1::2 ...
******************************************************************************
* Copyright (c) 2004-2011 Hangzhou H3C Tech. Co., Ltd. All rights reserved. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
# Telnet to Router C (2::2/64) from Router A. The operation fails.
<RouterA> telnet ipv6 2::2
Trying 2::2 ...
Press CTRL+K to abort
Can't connect to the remote host!
# Ping Router C (2::2/64) from Router A. The operation succeeds.
<RouterA> ping ipv6 2::2
PING 2::2 : 56 data bytes, press CTRL_C to break
Reply from 2::2
bytes=56 Sequence=1 hop limit=64 time = 4 ms
Reply from 2::2
bytes=56 Sequence=2 hop limit=64 time = 2 ms
Reply from 2::2
bytes=56 Sequence=3 hop limit=64 time = 2 ms
Reply from 2::2
bytes=56 Sequence=4 hop limit=64 time = 2 ms
Reply from 2::2
bytes=56 Sequence=5 hop limit=64 time = 2 ms
--- 2::2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/2/4 ms
Telnet uses TCP, and ping uses IMCP. The preceding results show that all TCP packets of Router A
are forwarded via next hop 1::2, and other packets are forwarded according to the routing table.
The PBR configuration is effective.
Configuring IPv6 interface PBR based on packet type
Network requirements
As shown in
, configure PBR on Router A, so that TCP packets arriving on the interface
GigabitEthernet 3/1/1 are forwarded via next hop 1::2 and other IPv6 packets are forwarded
according to the routing table.