-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Use!! #10
Comments
Tell me more information. What network interface are you use? Do you run script with admin priv? |
And show me screenshots please if you have it. |
Used Wifi network interface which I have connected to, and yes I tried in Command Prompt as Admin too. |
Very strange. If you do not have any output in the terminal, then tshark does not capture packets. I'll see what can be done soon. |
Hello, this is due to the fact that the switch "Use peer-to-peer network for calls" is disabled in the call privacy settings, and in order for the IP address detection to work, this function must be enabled for both users. When this feature is disabled, calls pass through Telegram servers, which does not allow you to get an ip, when this feature is enabled, calls are redirected directly from one interlocutor to another interlocutor bypassing Telegram servers, so we can track the IP of the interlocutor. |
Yeah, I know. And yeah peer-to-peer for calls is enabled already for both of them |
you can test your network NAT type is what? while i got the same problem, my network NAT type is Symmetric NAT; i guess that is the problem when i check the packet flow by wireshark, while src client not direct connect to the dst client, instead, src and dst connected by use the telegram relay server |
anyone fix that, the same issues |
It just shows "Capturing traffic, please wait..." after selecting interface and calling to a mutual contact in Telegram Desktop. Using Windows, downloaded all modules, what's the problem? Please help.
The text was updated successfully, but these errors were encountered: