[GH-ISSUE #3097] If Microsoft KM-TEST is installed

gitea-mirror commented

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

Owner

Copy link

Originally created by @Junsen2356579199 on GitHub (Sep 11, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3097

Describe the feature request

frpc.ini
server_addr = Microsoft KM-TEST ipv4 ip address
frpc Unable to start
can be excluded or bypassed Microsoft KM-TEST ?
or specify a network device to run ?

Describe alternatives you've considered

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 @Junsen2356579199 on GitHub (Sep 11, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3097 ### Describe the feature request frpc.ini server_addr = Microsoft KM-TEST ipv4 ip address frpc Unable to start can be excluded or bypassed Microsoft KM-TEST ? or specify a network device to run ? ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@fatedier commented on GitHub (Sep 11, 2022):

I have no idea about Microsoft KM-TEST and can't help you. Maybe you can google the solution.

@fatedier commented on GitHub (Sep 11, 2022): I have no idea about Microsoft KM-TEST and can't help you. Maybe you can google the solution.

gitea-mirror commented

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

Author

Owner

Copy link

@Becods commented on GitHub (Sep 12, 2022):

Fill in your Microsoft KM-TEST Loopback ip in the server_addr

@Becods commented on GitHub (Sep 12, 2022): Fill in your Microsoft KM-TEST Loopback ip in the server_addr

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Oct 13, 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 (Oct 13, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified