IPv6 LAN 在启动期间停止路由/响应

IPv6 LAN 在启动期间停止路由/响应

我最近设置了一个 HE 隧道,以便为我的网络添加 IPv6 支持。路由器启动时,“启动防火墙”会在控制台上滚动两次。第一次之后,我能够从网络上的计算机 ping 路由器的 LAN IPv6 地址,以及外部 IPv6 地址 (facebook)。我还可以毫无问题地 ping LAN 网络上的节点。第二次之后,我无法从网络上的任何节点通过其 IPv6 地址访问路由器,而路由器无法访问 LAN 上的任何 ipv6 地址。对 LAN 网络上任何节点的跟踪路由都会从路由器的地址给我 !A。从路由器,我可以通过隧道访问任何外部 IPv6。

我已经验证了高级设置中启用了 IPv6。我尝试向防火墙添加任何规则。我尝试暂时完全禁用防火墙。我尝试过拆除隧道并设置 IPv6 局域网,但问题依然存在。我验证了我的路由表是正确的。

此时,我非常感激任何帮助,因为我完全不知所措。

当它停止工作时,system.log 如下所示:

Mar 28 12:11:57 firewall kernel: ..
Mar 28 12:11:59 firewall check_reload_status: updating dyndns WAN_DHCP
Mar 28 12:11:59 firewall check_reload_status: Restarting ipsec tunnels
Mar 28 12:11:59 firewall check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 28 12:11:59 firewall check_reload_status: Reloading filter
Mar 28 12:12:00 firewall check_reload_status: updating dyndns WANGW
Mar 28 12:12:00 firewall check_reload_status: Restarting ipsec tunnels
Mar 28 12:12:00 firewall check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 28 12:12:00 firewall check_reload_status: Reloading filter
Mar 28 12:12:23 firewall kernel: .done.
Mar 28 12:12:23 firewall kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to accept, logging disabled
Mar 28 12:12:23 firewall kernel: DUMMYNET 0 with IPv6 initialized (100409)
Mar 28 12:12:23 firewall kernel: load_dn_sched dn_sched FIFO loaded
Mar 28 12:12:23 firewall kernel: load_dn_sched dn_sched QFQ loaded
Mar 28 12:12:23 firewall kernel: load_dn_sched dn_sched RR loaded
Mar 28 12:12:23 firewall kernel: load_dn_sched dn_sched WF2Q+ loaded
Mar 28 12:12:23 firewall kernel: load_dn_sched dn_sched PRIO loaded

我的路由表看起来正确:

Routing tables

Internet6:
Destination                       Gateway                       Flags      Netif Expire
::1                               link#8                        UH          lo0
MYIPV6PREFIX::/64                 link#2                        U           em1
MYIPV6PREFIX:3::5                 link#2                        UHS         lo0
fe80::%em0/64                     link#1                        U           em0
fe80::290:27ff:feee:a042%em0      link#1                        UHS         lo0
fe80::%em1/64                     link#2                        U           em1
fe80::290:27ff:feee:a043%em1      link#2                        UHS         lo0
fe80::%lo0/64                     link#8                        U           lo0
fe80::1%lo0                       link#8                        UHS         lo0
fe80::%ovpns1/64                  link#9                        U        ovpns1
fe80::290:27ff:feee:a042%ovpns1   link#9                        UHS         lo0
ff01::%em0/32                     fe80::290:27ff:feee:a042%em0  U           em0
ff01::%em1/32                     fe80::290:27ff:feee:a043%em1  U           em1
ff01::%lo0/32                     ::1                           U           lo0
ff01::%ovpns1/32                  fe80::290:27ff:feee:a042%ovpns1 U        ovpns1
ff02::%em0/32                     fe80::290:27ff:feee:a042%em0  U           em0
ff02::%em1/32                     fe80::290:27ff:feee:a043%em1  U           em1
ff02::%lo0/32                     ::1                           U           lo0
ff02::%ovpns1/32                  fe80::290:27ff:feee:a042%ovpns1 U        ovpns1

答案1

如果其他人遇到同样的问题,可以通过删除我的 Captive Portal 配置来解决。

相关内容