Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Feature Request] About HaProxy and the way this plugin works #25

Open
8MiYile opened this issue Feb 11, 2023 · 5 comments
Open

[Feature Request] About HaProxy and the way this plugin works #25

8MiYile opened this issue Feb 11, 2023 · 5 comments
Labels
bug Something isn't working enhancement New feature or request question Further information is requested

Comments

@8MiYile
Copy link

8MiYile commented Feb 11, 2023 •
edited
Loading

1.这个插件支持与Velocity的ProxyProtocol配置联动并正确使用吗？（然而测试不通过）
2.客户端方面能否支持UDP类型以及允许设置TCP+UDP混合工作（以通过UDP正确读到客户端IP地址）
3.绑定IP为全0导致刷日志的问题 (已经解决)
Frp fatedier/frp#3304

  1. Does this plugin support HAProxy from velocity's config？My Velocity server is configured with a hybrid port, configured via the plugin HaProxy-Detector plugin, allowing both HaProxy connections and direct connections
  2. Does it support loading RakNet when selecting a connection in the form of a button on the Edit Server Information Page .Mode:[Low,High,AutoDetect]
  3. TCP+UDP Mixed Mode?
  4. Can I disable certain IP segments? I don't want to see them working in the background, or only use IPs with 0.0.0.0
  5. If it doesn't work, just turn it on once according to Velocity.toml' bind configuration
  6. this log is loading
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:b825:62ff:fec0:2096%22]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:5cec:38ff:fea1:e96%14]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:448:38ff:feee:c056%18]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:ac64:c6ff:feab:79c3%12]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:80f7:f9ff:fe83:739c%16]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.28.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:9fff:fe0d:46c1%9]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.17.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.27.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.18.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:eff:fed0:1873%6]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.19.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:f1ff:fe66:fdc3%5]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.20.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:45ff:feeb:fbce%4]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /172.21.0.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[240e:379:ad22:8800:fe4b:d325:ed81:744d%0]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[240e:379:ad12:6800:0:0:0:fea%0]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:84f4:f069:31fe:6439%2]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[240e:379:ad12:6800:c6fd:ccda:e476:eb0f%0]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /10.0.0.5:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /[0:0:0:0:0:0:0:1%0]:25565
[04:35:38] [Velocity Async Event Executor - #2/INFO] [raknetify]: Raknetify server started on /127.0.0.1:25565

wtf... including docker's IP?

[04:38:38] [Velocity Task Scheduler - #7/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:38:38] [Velocity Task Scheduler - #9/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:ced:3ff:fe2a:3f9d%25692]:25565
[04:38:38] [Velocity Task Scheduler - #10/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:38:48] [Velocity Task Scheduler - #11/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:38:48] [Velocity Task Scheduler - #7/INFO] [raknetify]: Closing Raknetify server /192.168.250.1:25565
[04:38:48] [Velocity Task Scheduler - #12/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:ced:3ff:fe2a:3f9d%25692]:25565
[04:40:48] [Velocity Task Scheduler - #7/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:40:48] [Velocity Task Scheduler - #12/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:40:58] [Velocity Task Scheduler - #7/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:40:58] [Velocity Task Scheduler - #12/INFO] [raknetify]: Closing Raknetify server /192.168.250.1:25565
[04:44:58] [Velocity Task Scheduler - #7/ERROR] [raknetify]: Raknetify server failed to start on /[fe80:0:0:0:b4ec:89ff:fe6b:c2ae%vethfb8136a]:25565: bind(..) failed: 无法指定被请求的地址
[04:44:58] [Velocity Task Scheduler - #13/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:44:58] [Velocity Task Scheduler - #12/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565

IP: 192.168.250.X is a Deepin UEngine's local IP
@8MiYile
Copy link
Author

8MiYile commented Feb 11, 2023

and ... w... wtf?

[04:38:38] [Velocity Task Scheduler - #7/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:38:38] [Velocity Task Scheduler - #9/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:ced:3ff:fe2a:3f9d%25692]:25565
[04:38:38] [Velocity Task Scheduler - #10/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:38:48] [Velocity Task Scheduler - #11/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:38:48] [Velocity Task Scheduler - #7/INFO] [raknetify]: Closing Raknetify server /192.168.250.1:25565
[04:38:48] [Velocity Task Scheduler - #12/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:ced:3ff:fe2a:3f9d%25692]:25565
[04:40:48] [Velocity Task Scheduler - #7/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:40:48] [Velocity Task Scheduler - #12/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:40:58] [Velocity Task Scheduler - #7/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:40:58] [Velocity Task Scheduler - #12/INFO] [raknetify]: Closing Raknetify server /192.168.250.1:25565
[04:44:58] [Velocity Task Scheduler - #7/ERROR] [raknetify]: Raknetify server failed to start on /[fe80:0:0:0:b4ec:89ff:fe6b:c2ae%vethfb8136a]:25565: bind(..) failed: 无法指定被请求的地址
[04:44:58] [Velocity Task Scheduler - #13/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:44:58] [Velocity Task Scheduler - #12/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:45:08] [Velocity Task Scheduler - #12/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:45:08] [Velocity Task Scheduler - #7/INFO] [raknetify]: Closing Raknetify server /192.168.250.1:25565
[04:48:08] [Velocity Task Scheduler - #7/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:48:08] [Velocity Task Scheduler - #14/INFO] [raknetify]: Raknetify server started on /192.168.250.1:25565
[04:48:08] [Velocity Task Scheduler - #12/INFO] [raknetify]: Raknetify server started on /[fe80:0:0:0:a864:f3ff:fead:7bc1%25710]:25565
[04:48:18] [Velocity Task Scheduler - #14/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:a864:f3ff:fead:7bc1%25710]:25565
[04:48:18] [Velocity Task Scheduler - #12/INFO] [raknetify]: Closing Raknetify server /[fe80:0:0:0:42:d6ff:fe23:520f%3]:25565
[04:48:18] [Velocity Task Scheduler - #7/INFO] [raknetify]: Closing Raknetify server /192.168.250.1:25565

无法指定被请求的地址?
Is this an internal network test pass-through port?

@toinouH toinouH added bug Something isn't working enhancement New feature or request question Further information is requested labels Feb 12, 2023
@8MiYile
Copy link
Author

8MiYile commented Feb 12, 2023 •
edited
Loading

And when I connected to the server through OpenFrp, I found that the UDP port was not loaded with the HaProxy Protocol (Proxy Protocol), which caused the backend to show that the IP connected through OpenFrp's UDP tunnel was my server's internal IP.
Can you support reading Velocity's configuration items haproxy-protocol and HaProxy-Detector plugins?

@8MiYile
Copy link
Author

8MiYile commented Feb 12, 2023

image
this server using mix protocol
Bedrock+LanBoardcast+Haproxy+UDP（Raknet）

@8MiYile 8MiYile mentioned this issue Feb 12, 2023
Closed
11 tasks
@ishland
Copy link
Contributor

ishland commented Apr 5, 2023

  1. As far as I know, proxy-protocol doesn't exist on UDP applications.
  2. No.
  3. Pretty sure that is out of scope of this mod.
  4. There are currently no way to know where the UDP packets come from when using 0.0.0.0 as bind address. That is a workaround for compatibility with multiple network interfaces.
  5. If that's the case, people will be confused with not being able to connect after the server (re)connecting a network.

@8MiYile
Copy link
Author

8MiYile commented Apr 5, 2023

In other words, is a TCP handshake followed by a UDP-assisted transmission out of scope?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working enhancement New feature or request question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@8MiYile @ishland @toinouH