GFW-knocker/Xray-core

WebRTC Leak Test> Wrong Public IP address

Closed this issue · 0 comments

Integrity requirements

  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I provided the complete config and logs, rather than just providing the truncated parts based on my own judgment.
  • I searched issues and did not find any similar issues.
  • The problem can be successfully reproduced in the latest Release

Description

Hi Gfw-knocker

I came here to tell you about a bug in xray core for webrtc leak from client side:

when we connect our config
and test for webrtc in sites like:browserleak or ...
it always show:
26.26.26.1

it really bad
if you can fix it like sing-box(they replace it with private ip)
We really thanksfull for you.🤝🏻
Screenshot_20240829_012732_Chrome

Reproduction Method

nothing i have:)

Client config


Server config


Client log


Server log