[GH-ISSUE #2765] xtcp is not supported in frps

gitea-mirror commented

2026-05-05 13:25:29 -06:00

Owner

Originally created by @CyberFoxHax on GitHub (Jan 18, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2765

Bug Description

i followed the p2p instruction on the front page and all i get is: "xtcp is not supported in frps"

frpc Version

0.38.0

frps Version

0.38.0

System Architecture

Windows 10 x64

Configurations

Remote machine

[p2p_rdp]
type = xtcp
sk = abcdefg
local_ip = 127.0.0.1
local_port = 3389

My machine

[p2p_rdp_visitor]
type = xtcp
role = visitor
server_name = p2p_rdp
sk = abcdefg
bind_addr = 127.0.0.1
bind_port = 6000

Logs

No response

Steps to reproduce

No response

Affected area

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

Originally created by @CyberFoxHax on GitHub (Jan 18, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2765 ### Bug Description i followed the p2p instruction on the front page and all i get is: "xtcp is not supported in frps" ### frpc Version 0.38.0 ### frps Version 0.38.0 ### System Architecture Windows 10 x64 ### Configurations Remote machine ``` [p2p_rdp] type = xtcp sk = abcdefg local_ip = 127.0.0.1 local_port = 3389 ``` My machine ``` [p2p_rdp_visitor] type = xtcp role = visitor server_name = p2p_rdp sk = abcdefg bind_addr = 127.0.0.1 bind_port = 6000 ``` ### Logs _No response_ ### Steps to reproduce _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:25:29 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:25:33 -06:00

Author

Owner

@CyberFoxHax commented on GitHub (Jan 18, 2022):

doing some digging on my own

if cfg.BindUDPPort > 0 {
	var nc *nathole.Controller
	address := net.JoinHostPort(cfg.BindAddr, strconv.Itoa(cfg.BindUDPPort))
	nc, err = nathole.NewController(address)
	if err != nil {
		err = fmt.Errorf("Create nat hole controller error, %v", err)
		return
	}
	svr.rc.NatHoleController = nc
	log.Info("nat hole udp service listen on %s", address)
}

293003fcdb/server/service.go (L267)

according to this piece, as long as there's an entry for bind_udp_port and it's value is greater than 0, it should log either success or failure for the NAT service.

But neither is logged.

@CyberFoxHax commented on GitHub (Jan 18, 2022): doing some digging on my own ```go if cfg.BindUDPPort > 0 { var nc *nathole.Controller address := net.JoinHostPort(cfg.BindAddr, strconv.Itoa(cfg.BindUDPPort)) nc, err = nathole.NewController(address) if err != nil { err = fmt.Errorf("Create nat hole controller error, %v", err) return } svr.rc.NatHoleController = nc log.Info("nat hole udp service listen on %s", address) } ``` https://github.com/fatedier/frp/blob/293003fcdb6a090f9e2919b8e7d1224ab1e41549/server/service.go#L267 according to this piece, as long as there's an entry for bind_udp_port and it's value is greater than 0, it should log either success or failure for the NAT service. But neither is logged.

gitea-mirror commented

2026-05-05 13:25:33 -06:00

Author

Owner

@Looomo commented on GitHub (Jan 19, 2022):

add bind_udp_port = 7000 to your frps.ini.
make it looks like this:
[common]
bind_port = 7000
bind_udp_port = 7000

@Looomo commented on GitHub (Jan 19, 2022): add bind_udp_port = 7000 to your frps.ini. make it looks like this: [common] bind_port = 7000 bind_udp_port = 7000

gitea-mirror commented

2026-05-05 13:25:34 -06:00

Author

Owner

@CyberFoxHax commented on GitHub (Jan 19, 2022):

same

i think perhaps xtcp is a plugin that needs to be installed somehow?

@CyberFoxHax commented on GitHub (Jan 19, 2022): same i think perhaps xtcp is a plugin that needs to be installed somehow?

gitea-mirror commented

2026-05-05 13:25:35 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 19, 2022):

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 (Feb 19, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.