search

bepass-org / warp-plus

Warp+Psiphon, an anti censorship utility for iran
MIT License
1.49k stars 252 forks source link

WARP scanner not working as expected #120

Open KatanaO opened 4 months ago

KatanaO commented 4 months ago

Version number 1.2.1 and also older ones

I just find internal scanner doesnt work properly, then i add --endpoint [a working ip:port that i had before and its working on my ISP-mkh] in command and everything is OK. i try other flag and command [-4 , --rtt , ...] in auto scan line but they made no change in result. Auto-scan for endpoint needs to be improved.

And also in 1.2.1 version after run in gool or cfon mode "stuff' and "ca.psiphon.PsiphonTunnel.tunnel-core' sub-folders are not created, while they were made in 1.1.3 version

abbasudo commented 4 months ago

@KatanaO Stuff is no longer used in the new version. more details in #80

abbasudo commented 4 months ago

@KatanaO how can i find a working ip:port for my ISP?

KatanaO commented 4 months ago

@KatanaO how can i find a working ip:port for my ISP?

They are results of Warp-ip-scanners or The others (shared by people on tg channels, X , etc.). i used 2-3 of them in wg connection from 1-2 years ago till now. my new scan results (with warp-ip-scanner) dont work, and i'm confused a little about why and how one ip:port works or not on different ISPs. by the way i got the working ip:port by accident :(

markpash commented 4 months ago

The interesting thing about that is that the WARP scanner built inside of this project is working fine! It is able to successfully handshake with WARP IPs, but then the wireguard code fails to handshake! So either I need to improve the scanner to be the same as the wireguard code, or improve the wireguard code to be more like the scanner. :laughing:

Amir2367 commented 4 months ago

The interesting thing about that is that the WARP scanner built inside of this project is working fine! It is able to successfully handshake with WARP IPs, but then the wireguard code fails to handshake! So either I need to improve the scanner to be the same as the wireguard code, or improve the wireguard code to be more like the scanner. 😆

The reason for these errors is that the scanner has a very serious problem and cannot detect the correct IP and port, finally it can detect the correct IP once out of every 10 scans and the proxy mode is activated.

To solve this problem, I scan the IP and port with Peyman's scanner and manually add them like this.

./warp-plus -e ip:port This manual method makes the connection much more difficult.

  1. The IP and port do not work for more than one day in the first mobile and shatel and mci, and the new IP and port must be replaced.

  2. connection steps will be much longer

  3. It is better to replace another scanner to solve this problem from the root.

Screenshot_2024-05-30-22-16-45-827_com termux

Screenshot_2024-05-30-22-28-14-874_com termux