-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
-
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 4 comments · 14 replies
-
目前的配置: |
Beta Was this translation helpful? Give feedback.
All reactions
-
大概知道怎么回事了。。软件逻辑获得延迟似乎不是靠这个ip,而是看url响应时间。。。 |
Beta Was this translation helpful? Give feedback.
All reactions
-
我自己的外链也是ipv6,加入订阅,就被过滤掉了,好像测速失败一样,但是如果加入白名单,强制保留,结果一样播放。这个问题docker和工作流部署都是这个情况 |
Beta Was this translation helpful? Give feedback.
All reactions
-
stdout: Starting periodic command scheduler: cron. |
Beta Was this translation helpful? Give feedback.
All reactions
-
运行日志显示是有结果的,而你的问题是生成的结果中的ipv6有无,我需要你的ouput/sort.log文件才能进一步排查 |
Beta Was this translation helpful? Give feedback.
All reactions
-
如果不方便暴露接口,你可以截取ipv6测速信息部分,检查这些ipv6接口的延迟和速率信息 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Name: CCTV-2, URL: http://106.46.147.208:10443/tsfile/live/0002_1.m3u8?key=txiptv&playlive=1&authid=0$订阅源, Date: None, Delay: 38 ms, Speed: 13.77 M/s, Resolution: 1920x1080 发现了,最后这个好像是none有问题? |
Beta Was this translation helpful? Give feedback.
All reactions
-
这些都是ipv4,结果正常。没有获取到分辨率的,如果你开启了分辨率过滤,自然会被过滤,除非同时开始补偿,才会保留这些结果。对于部分由于dns获取不到分辨率的(#864),可以拉取最新镜像再试试。 |
Beta Was this translation helpful? Give feedback.
All reactions
-
上传完整的sort.log我看看? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
刚刚关了组播源 酒店源 和分辨率过滤 |
Beta Was this translation helpful? Give feedback.
All reactions
-
抱歉,现在才看到你的消息,我刚看了日志,ipv6延迟是有正常输出的结果的,并非所有都为-1,-1表示连接请求失败,可能是接口本身的原因。如果有疑问,请提供具体可访问,但测速结果失效的ipv6地址。 |
Beta Was this translation helpful? Give feedback.
All reactions
-
谢谢 |
Beta Was this translation helpful? Give feedback.
抱歉,现在才看到你的消息,我刚看了日志,ipv6延迟是有正常输出的结果的,并非所有都为-1,-1表示连接请求失败,可能是接口本身的原因。如果有疑问,请提供具体可访问,但测速结果失效的ipv6地址。