为什么移动的IPV6时好时坏啊

Limitpea

我在OpenWrt上拨号 刚开始WAN6可以获取到ipv6

后面突然又没有了 获取不到ipv6
有dalao知道什么情况吗

zyyhcufe

Limitpea 发表于 2023-4-18 13:53

日志可以看到和移动局端设备的链路地址协商没有问题，问题出在你的odhcp6c没有正常工作。

先试试把mwan3彻底禁用。

还不行的话，wan-高级设置-获取IPv6地址改成手动，然后wan6-物理设置，接口填@wan。

zyyhcufe

什么有用的信息都没有，你指望网友靠猜找故障吗。

Limitpea

不好意思老哥 忘记补图了

thzzy

和移动IPv6有什么关系？我也用移动好几年了都没这个问题，很稳定。你要找找其它原因了。光猫是改了桥接吧？OpenWrt没问题吧(毕竟是定制的固件，各种问题总还是有的)？用其它官方固件的品牌路由器测试试试，IPv6也不稳定吗？

Limitpea

thzzy 发表于 2023-4-18 13:35
和移动IPv6有什么关系？我也用移动好几年了都没这个问题，很稳定。你要找找其它原因了。光猫是改了桥接吧？ ...

光猫是桥接的 手头上也没其他路由器能测了
刚安装完的OpenWrt是可以正常获取到ipv6的 过几天重启了一下就没了
之前装的ikuai貌似也有这个问题
用于连接光猫拨号的口是PVE直通bcm5719    OpenWrt装在PVE下

zyyhcufe

Limitpea 发表于 2023-4-18 13:45
光猫是桥接的 手头上也没其他路由器能测了
刚安装完的OpenWrt是可以正常获取到ipv6的 过几天重启了 ...

拨号那一段的日志贴一下。

wgy2000

路由器刷的op,稳如老狗。v6用于访问黑群晖

Limitpea

zyyhcufe 发表于 2023-4-18 13:47
拨号那一段的日志贴一下。

1. Tue Apr 18 13:51:45 2023 daemon.info pppd[7496]: Plugin pppoe.so loaded.
   
2. Tue Apr 18 13:51:45 2023 daemon.info pppd[7496]: PPPoE plugin from pppd 2.4.9
   
3. Tue Apr 18 13:51:45 2023 daemon.notice pppd[7496]: pppd 2.4.9 started by root, uid 0
   
4. Tue Apr 18 13:51:45 2023 daemon.info pppd[7496]: PPP session is 45706
   
5. Tue Apr 18 13:51:46 2023 daemon.warn pppd[7496]: Connected to 24:4c:07:89:d2:f5 via interface eth1
   
6. Tue Apr 18 13:51:46 2023 kern.info kernel: [   22.494067] pppoe-wan: renamed from ppp0
   
7. Tue Apr 18 13:51:46 2023 daemon.err odhcp6c[7490]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
   
8. Tue Apr 18 13:51:46 2023 daemon.info pppd[7496]: Renamed interface ppp0 to pppoe-wan
   
9. Tue Apr 18 13:51:46 2023 daemon.info pppd[7496]: Using interface pppoe-wan
   
10. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: Connect: pppoe-wan <--> eth1
    
11. Tue Apr 18 13:51:46 2023 daemon.info pppd[7496]: syncppp not active
    
12. Tue Apr 18 13:51:46 2023 daemon.info pppd[7496]: CHAP authentication succeeded: Authentication success,Welcome!
    
13. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: CHAP authentication succeeded
    
14. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: peer from calling number 24:4C:07:89:D2:F5 authorized
    
15. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Joining mDNS multicast group on interface pppoe-wan.IPv6 with address fe80::c05e:9766:f268:b180.
    
16. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: local  LL address fe80::c05e:9766:f268:b180
    
17. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: remote LL address fe80::264c:07ff:fe89:d2f5
    
18. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: New relevant interface pppoe-wan.IPv6 for mDNS.
    
19. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Registering new address record for fe80::c05e:9766:f268:b180 on pppoe-wan.*.
    
20. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: local  IP address 10.6.104.170
    
21. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: remote IP address 10.6.0.1
    
22. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: primary   DNS address 211.136.192.6
    
23. Tue Apr 18 13:51:46 2023 daemon.notice pppd[7496]: secondary DNS address 120.196.165.24
    
24. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address 10.6.104.170.
    
25. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: New relevant interface pppoe-wan.IPv4 for mDNS.
    
26. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Registering new address record for 10.6.104.170 on pppoe-wan.IPv4.
    
27. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Withdrawing address record for 10.6.104.170 on pppoe-wan.
    
28. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Leaving mDNS multicast group on interface pppoe-wan.IPv4 with address 10.6.104.170.
    
29. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Interface pppoe-wan.IPv4 no longer relevant for mDNS.
    
30. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address 10.6.104.170.
    
31. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: New relevant interface pppoe-wan.IPv4 for mDNS.
    
32. Tue Apr 18 13:51:46 2023 daemon.info avahi-daemon[3816]: Registering new address record for 10.6.104.170 on pppoe-wan.IPv4.
    
33. Tue Apr 18 13:51:46 2023 daemon.notice netifd: Network device 'pppoe-wan' link is up
    
34. Tue Apr 18 13:51:46 2023 daemon.notice netifd: Interface 'wan' is now up
    
35. Tue Apr 18 13:51:46 2023 daemon.notice netifd: Network alias 'pppoe-wan' link is up
    
36. Tue Apr 18 13:51:46 2023 daemon.notice netifd: Interface 'wan_6' is enabled
    
37. Tue Apr 18 13:51:46 2023 daemon.notice netifd: Interface 'wan_6' has link connectivity
    
38. Tue Apr 18 13:51:46 2023 daemon.notice netifd: Interface 'wan_6' is setting up now
    
39. Tue Apr 18 13:51:46 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
    
40. Tue Apr 18 13:51:47 2023 daemon.err odhcp6c[7490]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
    
41. Tue Apr 18 13:51:47 2023 daemon.info avahi-daemon[3816]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::da9d:67ff:fe2b:92da.
    
42. Tue Apr 18 13:51:47 2023 daemon.info avahi-daemon[3816]: New relevant interface eth1.IPv6 for mDNS.
    
43. Tue Apr 18 13:51:47 2023 daemon.info avahi-daemon[3816]: Registering new address record for fe80::da9d:67ff:fe2b:92da on eth1.*.
    
44. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47Z" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header"
    
45. Tue Apr 18 13:51:47 2023 daemon.err modprobe: failed to find a module named aufs
    
46. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.241161107Z" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
    
47. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.241463444Z" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
    
48. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.242351080Z" level=error msg="failed to initialize a tracing processor "otlp"" error="no OpenTelemetry endpoint: skip plugin"
    
49. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.249928740Z" level=error msg="failed to mount overlay: invalid argument" storage-driver=overlay2
    
50. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.249977291Z" level=error msg="exec: "fuse-overlayfs": executable file not found in $PATH" storage-driver=fuse-overlayfs
    
51. Tue Apr 18 13:51:47 2023 kern.err kernel: [   23.700493] overlayfs: filesystem on '/opt/docker/check-overlayfs-support1446579393/upper' not supported as upperdir
    
52. Tue Apr 18 13:51:47 2023 daemon.err modprobe: failed to find a module named aufs
    
53. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.254028744Z" level=error msg="AUFS was not found in /proc/filesystems" storage-driver=aufs
    
54. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.254593314Z" level=error msg="failed to mount overlay: invalid argument" storage-driver=overlay
    
55. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.254604575Z" level=error msg="Failed to built-in GetDriver graph devicemapper /opt/docker"
    
56. Tue Apr 18 13:51:47 2023 kern.err kernel: [   23.705137] overlayfs: filesystem on '/opt/docker/check-overlayfs-support4106075691/upper' not supported as upperdir
    
57. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.263228368Z" level=warning msg="Unable to find memory controller"
    
58. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.263237315Z" level=warning msg="Unable to find cpu controller"
    
59. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.263241242Z" level=warning msg="Unable to find io controller"
    
60. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.263243897Z" level=warning msg="Unable to find cpuset controller"
    
61. Tue Apr 18 13:51:47 2023 daemon.err dockerd[7408]: time="2023-04-18T05:51:47.263247374Z" level=warning msg="Unable to find pids controller"
    
62. Tue Apr 18 13:51:47 2023 daemon.info modprobe: nf_conntrack is already loaded
    
63. Tue Apr 18 13:51:47 2023 daemon.info modprobe: nf_conntrack_netlink is already loaded
    
64. Tue Apr 18 13:51:47 2023 daemon.info avahi-daemon[3816]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
    
65. Tue Apr 18 13:51:47 2023 daemon.info avahi-daemon[3816]: New relevant interface docker0.IPv4 for mDNS.
    
66. Tue Apr 18 13:51:47 2023 daemon.info avahi-daemon[3816]: Registering new address record for 172.17.0.1 on docker0.IPv4.
    
67. Tue Apr 18 13:51:47 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
    
68. Tue Apr 18 13:51:47 2023 kern.info kernel: [   24.089694] traps: check[8860] general protection fault ip:8049007 sp:ffc78a80 error:402 in check[8049000+1000]
    
69. Tue Apr 18 13:51:52 2023 user.notice mwan3[2903]: Using firewall mask 0x3F00
    
70. Tue Apr 18 13:51:52 2023 user.notice mwan3[2903]: Max interface count is 60
    
71. Tue Apr 18 13:51:52 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
    
72. Tue Apr 18 13:51:52 2023 user.notice nlbwmon: Reloading nlbwmon due to ifup of lan (br-lan)
    
73. Tue Apr 18 13:51:53 2023 daemon.err miniupnpd[9740]: could not open lease file: /var/upnp.leases
    
74. Tue Apr 18 13:51:53 2023 daemon.notice miniupnpd[9740]: HTTP listening on port 5000
    
75. Tue Apr 18 13:51:53 2023 daemon.notice miniupnpd[9740]: Listening for NAT-PMP/PCP traffic on port 5351
    

复制代码

Limitpea

zyyhcufe 发表于 2023-4-18 14:25
日志可以看到和移动局端设备的链路地址协商没有问题，问题出在你的odhcp6c没有正常工作。

先试试把mwa ...

还是不行 WAN口获取的是fe80的IPV6地址

Limitpea

zyyhcufe 发表于 2023-4-18 14:25
日志可以看到和移动局端设备的链路地址协商没有问题，问题出在你的odhcp6c没有正常工作。

先试试把mwa ...

我把mwan3直接整个删掉了

zyyhcufe

Limitpea 发表于 2023-4-18 16:36
还是不行 WAN口获取的是fe80的IPV6地址

wan就是fe80，这个是正常的。
wan改成手动、wan6设备改成@wan之后，就可以手动重连wan6了，看下日志。

Limitpea

zyyhcufe 发表于 2023-4-18 17:03
wan就是fe80，这个是正常的。
wan改成手动、wan6设备改成@wan之后，就可以手动重连wan6了，看下日志。

获取到IPV6地址了
万分感谢

Limitpea

zyyhcufe 发表于 2023-4-18 17:03
wan就是fe80，这个是正常的。
wan改成手动、wan6设备改成@wan之后，就可以手动重连wan6了，看下日志。

但是现在LAN口分配不了ipv6-PD地址了。。都是fe80和fd50的内网地址

zyyhcufe

Limitpea 发表于 2023-4-18 18:35
但是现在LAN口分配不了ipv6-PD地址了。。都是fe80和fd50的内网地址

LAN - DHCP服务器 - IPv6设置，路由通告服务选服务器模式，DHCPv6服务选停用。
不行就手动重连下LAN吧，这个是你固件的问题，可能太老或者装的东西太多哪里冲突了。
还有就是短时间内多次重新拨号可能会导致一段时间获取不到IPv6。