mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 09:05:54 +03:00
[GH-ISSUE #1355] Add IPv6 #1350
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1350
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NghiaTranUIT on GitHub (Sep 9, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1355
Originally assigned to: @NghiaTranUIT on GitHub.
Description
Some users request that Proxyman should listen on IPv6 too. We should support it.
@NghiaTranUIT commented on GitHub (Sep 9, 2022):
Beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.9.0_IPv6_on_Preference_General.dmg
Screenshot
@king112ola commented on GitHub (Jan 23, 2025):
Hi, I am testing on my ios remote device (connected to proxyman via wifi manual proxy setting) when I make a direct HTTPS request in Chrome browser using the ipv4 address e.g. https://1.1.1.1 , proxyman was able to capture that, but when I test an app that makes a similar request to (ipv4 - 142.250.198.170:443) or (ipv6 - [2404:6800:4005:815::200a]:443), I couldn't see it on proxyman.
Is that a problem with the iOS wifi manual proxy? or I have done anything wrong.
Or should I try Atlantis for iOS.
@NghiaTranUIT commented on GitHub (Jan 23, 2025):
@king112ola may I ask if your iOS is a native app or React Native?
and does your connection via IP success? Or failed?
@king112ola commented on GitHub (Jan 23, 2025):
@NghiaTranUIT, thanks for your reply!
The app isn't developed by me, it's a publicly available app on the Apple IOS App Store. What I wanted to achieve was to capture all the network traffic from this app and route it through a new app I developed, using the Network Extension Relay Manager's matchDomains to bypass the app's regional blocking. However, the issue is that the domains I captured using Proxyman (no IPv4/IPv6 addresses found, just domains) were insufficient to bypass the restriction.
Interestingly, when I used excludedDomains (similar to the way a typical VPN works) to route all network traffic to my relay without relying on matchDomains, it worked. This led me to wonder whether Proxyman, when used with an iOS remote device (via Wi-Fi manual proxy settings), might not capture certain hidden types of network traffic, such as IPv4, gRPC, or WebSocket.
@NghiaTranUIT commented on GitHub (Jan 23, 2025):
From what I know, If you manually set up the Proxy via WiFi, some apps might not respect the HTTP Proxy. For example, react native app has their own networking library, and it's usually bypass the HTTP Proxy.
However, if you're using Proxyman VPN (iOS app), all traffic will be navigate via the VPN and you might capture it.
Can you try using Proxyman for iOS and test again?
@king112ola commented on GitHub (Jan 23, 2025):
I have just tested it on the iOS version, but I only see HTTP domain requests. After some testing on wireshark (ios using rvictl), I suspect this is due to a DNS leak. Am I correct in assuming that Proxyman cannot capture DNS resolution requests?
@NghiaTranUIT commented on GitHub (Jan 23, 2025):
you're right. Proxyman can't capture DNS because it operates over TLS layer.
Proxyman only works with application layers, HTTP/HTTPS and Websocket
@king112ola commented on GitHub (Jan 23, 2025):
Got it, thx for your reply!