FRP+CS then implements the local Kali to receive Shell
Today, I will talk to you about FRP+CS and then realize the local Kali and receive Shell. Many people may not know much about it. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.
Preface
Has anyone seen anything like this?
The group server always hangs up, even if it is restarted, it will hang up again later.
Try to upgrade: the minimum configuration will cost an extra 600. Think about it!
Through the test, it is found that the local virtual machine building group service is very stable. Therefore, whether it is possible to map the local community to the public network IP of vps, so that only the Internet IP of vps is used, and the memory CPU of the local virtual machine is used for performance.
Experimental goal
Open three ports steadily on vps
57757 is a community port (default 50050)
443 is the listening port.
80 is used for web,powershell no file execution.
Frp configuration
The first step is to modify the vps server-side frps.ini configuration.
The second step is to modify the client frpc.ini configuration of the local kali.
Server vps runs the command:. / frps-c frps.ini
Client kali runs the command:. / frpc-c frpc.ini
Then we saw the first result, opening 57757, 443,80 on vps.
Go to CS at this time.
Run the community on kali first.
Try to connect with the client.
The port is not open.
Check, because the frp server vps does not add nohup, so I hung up during the noon break.
Restart.
The frp client kaili is also fine.
The group started successfully.
CS client
Successfully launched:
The rest is when it will be disconnected automatically, because it only consumes the bandwidth of vps and has little impact on the performance of cpu memory, so we think it should be appropriate.
To view the file, sleep 2 is set up for convenience.
The main error report of kali is that the frp server hangs up, and the client connects automatically after the service is up. It seems that the virtual machine kali client is still very stable.
If you want to msf, the client has to add ports.
Restart the client, the impact on the CS is not great, the cs client restart will be the case.
Msf sets the listening port.
Msf settings.
Increase the conversation.
Choose to add sessions.
Msfconsole is online.
After reading the above, do you have any further understanding of FRP+CS and then implementing local Kali receiving Shell? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.
