[GH-ISSUE #4368] How to get real IP address to RDP servers?

gitea-mirror commented

2026-05-05 14:13:13 -06:00

Owner

Copy link

Originally created by @ylluminate on GitHub (Aug 4, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4368

Bug Description

RDP servers get a lot of attacks. It doesn't seem there's a way to pass the true IP address of the attackers through FRP so as to be able to block them with EvlWatcher or IPBan. Is there any known workaround or such to facilitate getting the IP to Windows servers?

frpc Version

0.59

frps Version

0.59

System Architecture

linux/amd64

Configurations

Not relevant.

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @ylluminate on GitHub (Aug 4, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4368 ### Bug Description RDP servers get a lot of attacks. It doesn't seem there's a way to pass the true IP address of the attackers through FRP so as to be able to block them with EvlWatcher or IPBan. Is there any known workaround or such to facilitate getting the IP to Windows servers? ### frpc Version 0.59 ### frps Version 0.59 ### System Architecture linux/amd64 ### Configurations Not relevant. ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [X] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:13:13 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:13:17 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (Aug 4, 2024):

这需要 RDP 支持 “proxy protocol”。显然，这不太可能

@xqzr commented on GitHub (Aug 4, 2024): 这需要 RDP 支持 “proxy protocol”。显然，这不太可能

gitea-mirror commented

2026-05-05 14:13:17 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 26, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Aug 26, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:47:58 -06:00

[PR #3449] [MERGED] refactor the code related to xtcp #4747

No Branch/Tag specified