设备型号:H3C MSR3600,我按照官网配置配置了aft,但是内网192.168.1.3去ping 10.89.244.247为什么在路由器外网口抓不到源地址为46:ffdb::/96的包,而且也ping不通10.89.244.247。IPv6 Internet中240C:8051:500::11:0:37这台主机上是有默认路由的,网关地址为240C:8051:500::11:0:33。是否是因为路由的原因?但是我看路由表里面是有到达10.89.244.247的主机路由的。一本通上的配置如下,我根据我的实际情况改了一些地址。

<H3C>dis current-configuration
#
version 7.1.064, Release 0707P21
#
sysname H3C
#
telnet server enable
#
dhcp enable
dhcp server always-broadcast
#
dns proxy enable
#
password-recovery enable
#
vlan 1
#
dhcp server ip-pool lan1
gateway-list 192.168.0.1
network 192.168.0.0 mask 255.255.254.0
address range 192.168.1.2 192.168.1.254
dns-list 192.168.0.1
#
controller Cellular0/0
#
interface NULL0
#
interface Vlan-interface1
ip address 192.168.0.1 255.255.254.0
tcp mss 1280
aft enable
#
interface GigabitEthernet0/0
port link-mode route
#
interface GigabitEthernet0/1
port link-mode route
#
interface GigabitEthernet0/2
port link-mode route
aft enable
ipv6 address 240C:8051:500::11:0:33/96
#
interface GigabitEthernet0/27
port link-mode route
#
interface GigabitEthernet0/28
port link-mode route
#
interface GigabitEthernet0/3
port link-mode bridge
#
interface GigabitEthernet0/4
port link-mode bridge
#
interface GigabitEthernet0/5
port link-mode bridge
#
interface GigabitEthernet0/6
port link-mode bridge
#
interface GigabitEthernet0/7
port link-mode bridge
#
interface GigabitEthernet0/8
port link-mode bridge
#
interface GigabitEthernet0/9
port link-mode bridge
#
interface GigabitEthernet0/10
port link-mode bridge
#
interface GigabitEthernet0/11
port link-mode bridge
#
interface GigabitEthernet0/12
port link-mode bridge
#
interface GigabitEthernet0/13
port link-mode bridge
#
interface GigabitEthernet0/14
port link-mode bridge
#
interface GigabitEthernet0/15
port link-mode bridge
#
interface GigabitEthernet0/16
port link-mode bridge
#
interface GigabitEthernet0/17
port link-mode bridge
#
interface GigabitEthernet0/18
port link-mode bridge
#
interface GigabitEthernet0/19
port link-mode bridge
#
interface GigabitEthernet0/20
port link-mode bridge
#
interface GigabitEthernet0/21
port link-mode bridge
#
interface GigabitEthernet0/22
port link-mode bridge
#
interface GigabitEthernet0/23
port link-mode bridge
#
interface GigabitEthernet0/24
port link-mode bridge
#
interface GigabitEthernet0/25
port link-mode bridge
#
interface GigabitEthernet0/26
port link-mode bridge
#
scheduler logfile size 16
#
line class console
user-role network-admin
#
line class tty
user-role network-operator
#
line class vty
user-role network-operator
#
line con 0
user-role network-admin
#
line vty 0 63
authentication-mode scheme
user-role network-operator
#
ipv6 route-static :: 0 240C:8051:500::11:0:1
#
ssh server enable
#
acl basic 2000
rule 0 permit source 192.168.0.0 0.0.1.255
rule 5 deny
#
password-control enable
undo password-control aging enable
undo password-control history enable
password-control length 6
password-control login-attempt 3 exceed lock-time 10
password-control update-interval 0
password-control login idle-time 0
password-control complexity user-name check
#
domain system
#
domain default enable system
#
role name level-0
description Predefined level-0 role
#
role name level-1
description Predefined level-1 role
#
role name level-2
description Predefined level-2 role
#
role name level-3
description Predefined level-3 role
#
role name level-4
description Predefined level-4 role
#
role name level-5
description Predefined level-5 role
#
role name level-6
description Predefined level-6 role
#
role name level-7
description Predefined level-7 role
#
role name level-8
description Predefined level-8 role
#
role name level-9
description Predefined level-9 role
#
role name level-10
description Predefined level-10 role
#
role name level-11
description Predefined level-11 role
#
role name level-12
description Predefined level-12 role
#
role name level-13
description Predefined level-13 role
#
role name level-14
description Predefined level-14 role
#
user-group system
#
local-user admin class manage
service-type ssh telnet http
authorization-attribute user-role network-admin
#
aft prefix-nat64 46:FFDB:: 96
aft v6tov4 source 240C:8051:500::11:0:37 10.89.244.247
aft v4tov6 source acl number 2000 prefix-nat64 46:FFDB:: 96
#
ip http enable
#
wlan global-configuration
#
wlan ap-group default-group
vlan 1
#
return
<H3C>sys
[H3C]dis ip routing-table
Destinations : 13 Routes : 13
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.89.244.247/32 Direct 2 0 0.0.0.0 NULL0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
192.168.0.0/23 Direct 0 0 192.168.0.1 Vlan1
192.168.0.0/32 Direct 0 0 192.168.0.1 Vlan1
192.168.0.1/32 Direct 0 0 127.0.0.1 InLoop0
192.168.1.255/32 Direct 0 0 192.168.0.1 Vlan1
224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0
224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
[H3C]
(0)
最佳答案
根据您的配置和描述,问题很可能出在路由配置和AFT转换规则上。您在路由器外网口抓不到NAT64转换后的数据包,说明数据包没有到达外网口,或者AFT转换没有生效。
问题分析与解决步骤
1. 核心问题分析
从您的配置和路由表看:
IPv4内网:192.168.0.0/23(包含192.168.1.3)
NAT64前缀:46:FFDB::/96
IPv6服务器地址:240C:8051:500::11:0:37
映射的IPv4地址:10.89.244.247
您遇到的问题是:
路由表显示10.89.244.247/32指向NULL0接口 - 这是AFT自动生成的黑洞路由,用于捕获去往该地址的流量进行转换
抓包看不到46:FFDB::/96前缀的包 - 说明转换没有发生或路由有问题
2. 配置修正建议
步骤1:检查并修正路由配置
您的路由表缺少重要路由:
# 添加到达10.89.244.247的主机路由,指向正确的下一跳
[H3C] ip route-static 10.89.244.247 32 192.168.0.1
# 或者指向出接口(根据实际情况)
[H3C] ip route-static 10.89.244.247 32 GigabitEthernet0/2
# 检查IPv6路由是否正确
[H3C] display ipv6 routing-table
# 确保有到达240C:8051:500::11:0:37/128的路由
步骤2:修正AFT配置
您的AFT配置有几个关键问题:
# 1. 检查NAT64前缀配置是否正确
[H3C] display aft prefix-nat64
# 2. 重新配置AFT规则(建议按顺序)
[H3C] undo aft v4tov6 source acl number 2000 prefix-nat64 46:FFDB:: 96
[H3C] undo aft v6tov4 source 240C:8051:500::11:0:37 10.89.244.247
[H3C] undo aft prefix-nat64 46:FFDB:: 96
# 3. 重新配置(按正确顺序)
[H3C] aft prefix-nat64 46:FFDB:: 96
[H3C] aft v4tov6 source acl number 2000 prefix-nat64 46:FFDB:: 96
[H3C] aft v6tov4 source 240C:8051:500::11:0:37 10.89.244.247
# 4. 确认接口AFT启用状态
[H3C] display aft interface
步骤3:关键配置检查点
# 1. 确认ACL 2000正确匹配
[H3C] display acl 2000
# 2. 确认接口配置
# 内网接口应配置AFT(已配置)
[H3C-GigabitEthernet0/2] display this
# 确保接口有正确的IPv6地址和AFT启用
# 3. 添加必要的IPv6路由
[H3C] ipv6 route-static 240C:8051:500::11:0:37 128 240C:8051:500::11:0:1
# 或确保默认路由正确
[H3C] ipv6 route-static :: 0 240C:8051:500::11:0:1
3. 完整修正配置示例
基于您的需求和环境,建议配置:
# 系统视图
sysname H3C
# 基本网络配置
interface Vlan-interface1
ip address 192.168.0.1 255.255.254.0
aft enable
interface GigabitEthernet0/2
port link-mode route
ipv6 address 240C:8051:500::11:0:33/96
aft enable
# ACL配置
acl basic 2000
rule 0 permit source 192.168.0.0 0.0.1.255
# AFT配置
aft prefix-nat64 46:FFDB:: 96
aft v4tov6 source acl number 2000 prefix-nat64 46:FFDB:: 96
aft v6tov4 source 240C:8051:500::11:0:37 10.89.244.247
# 路由配置(关键!)
# IPv4路由:告诉路由器如何到达10.89.244.247(经过AFT转换)
ip route-static 10.89.244.247 32 NULL0 # 已有,用于触发AFT
# IPv6路由:确保转换后的包能发出
ipv6 route-static :: 0 240C:8051:500::11:0:1
4. 诊断命令
# 1. 检查AFT会话
<H3C> display aft session table ipv4
<H3C> display aft session table ipv6
# 2. 开启AFT调试
<H3C> terminal monitor
<H3C> terminal logging
<H3C> debugging aft ipv4
<H3C> debugging aft ipv6
# 3. 执行ping测试
# 从内网主机ping 10.89.244.247
# 4. 查看调试信息
<H3C> display debugging aft
# 5. 抓包分析
# 在内网口和外网口同时抓包
[H3C-GigabitEthernet0/2] tcpdump ipv6
5. 可能的问题原因
路由环路:10.89.244.247/32指向NULL0,但实际需要触发AFT转换
IPv6路由缺失:转换后的IPv6包没有正确的下一跳
AFT顺序问题:配置顺序可能影响转换
接口AFT未生效:确认两个接口都正确启用了AFT
6. 快速验证步骤
从路由器本身ping IPv6服务器:
<H3C> ping ipv6 240C:8051:500::11:0:37
如果失败,说明IPv6路由有问题。
从路由器ping映射的IPv4地址:
<H3C> ping 10.89.244.247
如果失败,说明AFT配置有问题。
检查AFT转换:
<H3C> display aft ipv4
<H3C> display aft ipv6
请按照上述步骤检查和修正配置,特别是路由配置部分。如果仍有问题,请提供以下信息以便进一步分析:
display aft session table的输出
display ipv6 routing-table的输出
路由器ping IPv6服务器和IPv4映射地址的结果
抓包结果(如果可能)
(0)
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论