1. Introduction to Frp
1. What is frp?
frp is a high-performance reverse proxy application that focuses on intranet penetration, supports TCP, UDP, HTTP, HTTPS and other protocols, and supports P2P communication. Intranet services can be exposed to the public network in a safe and convenient manner through the transit of nodes with public network IP.
2. Why use frp?
By deploying the frp server on a node with a public network IP, it is easy to penetrate the intranet service to the public network, and at the same time provide many professional features, including:
- Client server communication supports various protocols such as TCP, QUIC, KCP and Websocket.
- Stream multiplexing of TCP connections is used to carry more requests between a single connection, saving connection establishment time and reducing request delay.
- Load balancing across proxy groups.
- Port multiplexing, multiple services are exposed through the same server port.
- Supports P2P communication, the traffic does not go through the server, and the bandwidth resources are fully utilized.
- Multiple natively supported client plug-ins (static file viewing, HTTPS/HTTP protocol conversion, HTTP, SOCK5 proxy, etc.), which facilitate independent use of the frp client to complete certain tasks.
- The highly scalable server-side plug-in system is easy to expand functions according to its own needs.
- Server and client UI pages.
3. Official information
- Full documentation: https://gofrp.org/docs/
- Download address: https://github.com/fatedier/frp/releases
2. Start building the server
1. Prepare
First, you need a server that can access the external network to build a server. I use an Alibaba Cloud server
and download the latest official version of frp. My server is a window system. I directly download this
frp_0.50.0_windows_amd64.zip
2. Modify the configuration file
After decompressing the downloaded frp, modify the content of the frps.ini file as follows:
[common]
bind_addr = 0.0.0.0
bind_port = 7000
token = 123456
| configuration item | Introduction |
|---|---|
| bind_addr | Server listening address, just 0.0.0.0 |
| bind_port | Server listening port |
| token | The token value used for authentication The client needs to set the same value to pass the authentication |
Official detailed server configuration https://gofrp.org/docs/reference/server-configures/
3. Start the server
direct command start
frps -c frps.ini
The display is as follows, the startup is successful
3. Configure the client
1. Prepare
My client computer is also a window system, so I downloaded frp_0.50.0_windows_amd64.zip directly
2. Modify the configuration file
After the downloaded frp is decompressed, modify the content of the frpc.ini file as follows:
[common]
token = 123456
server_addr = 111.111.111.111
server_port = 7000
admin_addr = 127.0.0.1
admin_port = 7400
admin_user = admin
admin_pwd = admin
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 3000
remote_port = 80
| configuration item | Introduction |
|---|---|
| token | The token value used for authentication needs to be set to the same value on the server side to pass the authentication |
| server_addr | server ip |
| server_port | Server listening port |
| admin_port | Local management panel port, can be set freely |
| admin_user admin_pwd | Local management panel account password |
| local_ip | The local ip to be mapped |
| local_port | The local port to be mapped |
| remote_port | The port to map to the remote |
Official detailed client configuration https://gofrp.org/docs/reference/client-configures/
3. Start the client
direct command start
frpc -c frpc.ini
The display is as follows, the startup is successful
end at last