Mandatory information
- NetIP Version: v0.3.0
- Operating System Version: Win 10
Summary
When using a local proxy that listens on IPv4 127.0.0.1, IPv6 connectivity is broken.
Steps to reproduce
- Enable a local proxy like v2ray
- Attempt to fetch the public IPv6
Expected result
NetIP should be to fetch the IPv6.
Current result
NetIP gets HTTP errors while fetching the IPv6
Relevant logs and/or screenshots
[ERR] [Public IPv6] An error occurred while making the HTTP request. System.Net.Http.HttpRequestException: An attempt was made to access a socket in a way forbidden by its access permissions. (127.0.0.1:10809)
---> System.Net.Sockets.SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__Core|281_0(IPAddress[] addresses, Int32 port, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.<ConnectAsync>g__Core|281_0(IPAddress[] addresses, Int32 port, CancellationToken cancellationToken)
at NetIP.Services.NetworkInfoService.<>c__DisplayClass1_0.<<GetConnectCallBack>b__0>d.MoveNext()
--- End of stack trace from previous location ---
Additional context
N/A
Possible fixes
- add a information about IP providers that support forcing v4/v6 protocols via their urls
- add a config option in NetIP to use the system’s proxy or ignore it, and if enabled, warn the user that he must use these aforementioned providers.