github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 16:15:49 -06:00

[GH-ISSUE #2519] do we have Sub domain to TCP feature? #2001

New issue

Closed

opened 2026-05-05 13:17:38 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

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

Owner

Originally created by @infinitysky on GitHub (Aug 8, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2519

The solution you want

by using a sub domain to proxy TCP connection
使用 2级域名的方式代理TCP 连接

Alternatives considered

How to implement this function

frpc.ini

[mysql]
type = tcp
local_ip = 127.0.0.1
local_port = 9899
custom_domains = mysql1

[mysql]
type = tcp
local_ip = 127.0.0.1
local_port = 9899
custom_domains = mysql2

After that. I could access to the mysql server by using the following link
在此之后，使用如下连接即可访问 mysql 服务器

mysql1.domainname.com:3306

mysql2.domainname.com:3306

Application scenarios of this function

when using layer 4 proxy in a mass production environment, the remote port from the server is not enough to handling the hosts.

I have over 200 clients now... and each client could have 2-3 terminal machine , also each terminal needs 3 ports to expose.... there for a sub-domain connection will be an ideal solution

correct me, if we got similar solution already....

I have tried tcpmuxhttpconnect and secret_tcp, they are not works in this scenario..

thanks for your time and help, have a nice day

简述：
由于目前我有将近200+ （还在增长中）的客户，每个客户基本上拥有 2-3台终端，于此同时每个终端至少有2-3个服务端口需要开放，因此只在服务器上维护端口号远远不够。。。我已经尝试了很多方式比如 tcpmuxhttpconnect 和 secret_tcp，但是这些都不满足需求。。
因此请问有没有合适的方式来满足这类需求？
非常感谢诸位的时间和帮助，谢谢

Originally created by @infinitysky on GitHub (Aug 8, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2519  **The solution you want**  by using a sub domain to proxy TCP connection 使用 2级域名的方式代理TCP 连接 **Alternatives considered**  **How to implement this function**  `frpc.ini` ``` [mysql] type = tcp local_ip = 127.0.0.1 local_port = 9899 custom_domains = mysql1 ``` ``` [mysql] type = tcp local_ip = 127.0.0.1 local_port = 9899 custom_domains = mysql2 ``` After that. I could access to the mysql server by using the following link 在此之后，使用如下连接即可访问 mysql 服务器 `mysql1.domainname.com:3306` `mysql2.domainname.com:3306` **Application scenarios of this function**  when using layer 4 proxy in a mass production environment, the remote port from the server is not enough to handling the hosts. I have over 200 clients now... and each client could have 2-3 terminal machine , also each terminal needs 3 ports to expose.... there for a sub-domain connection will be an ideal solution correct me, if we got similar solution already.... I have tried tcpmuxhttpconnect and secret_tcp, they are not works in this scenario.. thanks for your time and help, have a nice day 简述：由于目前我有将近200+ （还在增长中）的客户，每个客户基本上拥有 2-3台终端，于此同时每个终端至少有2-3个服务端口需要开放，因此只在服务器上维护端口号远远不够。。。我已经尝试了很多方式比如 tcpmuxhttpconnect 和 secret_tcp，但是这些都不满足需求。。因此请问有没有合适的方式来满足这类需求？非常感谢诸位的时间和帮助，谢谢

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

@xilu0 commented on GitHub (Aug 12, 2021):

where is the main domain?

@xilu0 commented on GitHub (Aug 12, 2021): where is the main domain?

gitea-mirror commented

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

Author

Owner

@infinitysky commented on GitHub (Aug 13, 2021):

where is the main domain?

sorry I am not sure what you mean,

I did A record configuration to my frp server

@infinitysky commented on GitHub (Aug 13, 2021): > where is the main domain? sorry I am not sure what you mean, I did A record configuration to my frp server

gitea-mirror commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Sep 13, 2021):

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

@github-actions[bot] commented on GitHub (Sep 13, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:43:01 -06:00

[PR #2001] [MERGED] ci: add close stale #4487

gitea-mirror referenced this issue

2026-05-05 14:43:12 -06:00

[PR #2018] [MERGED] bump version to v0.34.1 #4495