XX-net/XX-Net

如何重置IPv6设置？win7，组策略里改了6to4服务器地址后一直异常。

Open

#10,306 opened on Apr 2, 2018

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Python (33,036 stars) (7,691 forks)batch import
help wanted需要帮助

Description

即使最新的3.11.7也无法获取资源 提示： Apr 02 21:48:10.769 - [DEBUG] GAEProxy Web_control 127.0.0.1:54335 GET /check_ip?cmd=get_process

Apr 02 21:48:10.951 - [DEBUG] report_connect_fail IPv6 continue_fail_count:359

Apr 02 21:48:10.951 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:10.951 - [DEBUG] connect 2***3 network fail

Apr 02 21:48:10.953 - [DEBUG] report_connect_fail IPv6 continue_fail_count:360

Apr 02 21:48:10.953 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:10.953 - [DEBUG] connect *** network fail

Apr 02 21:48:11.429 - [DEBUG] report_connect_fail IPv6 continue_fail_count:361

Apr 02 21:48:11.429 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:11.429 - [DEBUG] connect 26**:e network fail

Apr 02 21:48:12.002 - [DEBUG] report_connect_fail IPv6 continue_fail_count:362

Apr 02 21:48:12.002 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:12.003 - [DEBUG] report_connect_fail IPv6 continue_fail_count:363

Apr 02 21:48:12.003 - [DEBUG] connect 2***a network fail

Apr 02 21:48:12.003 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:12.003 - [DEBUG] connect 2***19 network fail

Apr 02 21:48:12.917 - [DEBUG] report_connect_fail IPv6 continue_fail_count:364

Apr 02 21:48:12.917 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:12.917 - [DEBUG] connect 26***:d network fail

Apr 02 21:48:13.015 - [DEBUG] report_connect_fail IPv6 continue_fail_count:365

Apr 02 21:48:13.015 - [DEBUG] report_connect_fail network fail

Apr 02 21:48:13.015 - [DEBUG] connect 24***:a network fail

暂不清楚究竟是不是我更改过设置的缘故，本机的IP6是由路由器分配的6t4地址。网络状态中显示IPV6已经连接internet。地址都是正确地址。虽然设置全都恢复默认了，但依旧上不去网。我在考虑系统还原一下，只不过需要重新安装好多软件。

Contributor guide

Tech stack
python
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
IPv6 knowledgeproxy configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate how the user's modification of the 6to4 server address in Windows group policy affects IPv6 connectivity via XX Net. Examine the XX Net codebase, particularly the network connection handling in Python, to understand the 'network fail' log messages and identify if there is a way to reset or ignore custom IPv6 settings. Check the issue comments for any maintainer responses that might provide clues. The goal is to determine if the issue is a configuration problem or a bug in XX Net's IPv6 handling, and then propose a fix or workaround.