rustdesk / rustdesk/rustdesk-server
The client encountered an issue while using ipv6
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Server OS : openwrt x86 docker
Server version:1.1.10-3
client os : MacOS
client:1.2.3
When the client has an IPv6 address, it is obtained by using the SIM card on the phone, opening the hotspot, and obtaining the IPv6 address. After connecting, the client: does not show as ready. Please check the network connection, but you can still enter the ID to control others, as well as the logs displayed by the server. I have uploaded them, please check
server logs
stdout: [2024-04-20 12:05:10.784476 +00:00] INFO [src/rendezvous_server.rs:597] IP change of 332279342 from [::ffff:220.196.193.50]:14331 to [2408:840d:dd30:ac8b:ce5:82b5:b13b:fbbd]:61953
It seems that the client's IPv4 address has been changed to the client's IPv6 address, and the server is frantically repeating the above log content. I only intercepted the last line of the log, and the content is the same.
After turning off the client's ipv6, the network will show ready and everything is normal. It is known that the hotspot ipv6 issued by the SIM card of the mobile phone in China is likely to be prohibited from entering. Maybe this is the reason why ipv6 cannot work properly. I Just a guess.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IPv6 address-change handling reported at src/rendezvous_server.rs:597 and review the attached server logs. Reproduce the issue with an IPv6 client using a phone hotspot, then verify that the client reaches ready state without repeatedly logging IP changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100