[GH-ISSUE #4774] virtual_net: (0.62.1) visitors connection not working

gitea-mirror commented

2026-05-05 14:24:53 -06:00

Owner

Copy link

Originally created by @manprint on GitHub (Apr 28, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4774

Bug Description

Hi @fatedier

I am testing the virtual network in the new release 0.62.1.

Client side (target machine), the interface utun0 (100.85.0.1) is allocated correctly and I am able to ping the interface itself: ping 100.85.0.1 -> OK

Visitor side (my laptop), the interface utun0 is allocated but the client is not reachable; ping 100.85.0.1 not working -> KO. Also, pinging the interface itself does not work either: ping 100.85.0.2 -> KO

frpc Version

0.62.1

frps Version

0.62.1

System Architecture

linux/amd64

Configurations

client:

serverAddr = "mydomain.net"
serverPort = 7835
user = "admin"
metadatas.token = "zzzzz"

transport.protocol = "tcp"
transport.tls.enable = false

featureGates = { VirtualNet = true }
virtualNet.address = "100.85.0.1/24"

proxies
name = "client-vnet-test"
type = "stcp"
secretKey = "zzzzzzz"
[proxies.plugin]
type = "virtual_net"

visitors:

serverAddr = "mydomain.net"
serverPort = 7835

user = "admin"
metadatas.token = "zzzzz"

transport.protocol = "tcp"
transport.tls.enable = false

featureGates = { VirtualNet = true }
virtualNet.address = "100.85.0.2/24"

visitors
name = "visitors-vnet-test"
type = "stcp"
serverName = "client-vnet-test"
secretKey = "zzzzzzz"
bindPort = -1
[visitors.plugin]
type = "virtual_net"
destinationIP = "100.85.0.1"

Logs

No errors in log.

Steps to reproduce

start client vnet
start visitors vnet
ping from visitors client ip or visitor ip -> not working
...

Affected area

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

Originally created by @manprint on GitHub (Apr 28, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4774 ### Bug Description Hi @fatedier I am testing the virtual network in the new release 0.62.1. Client side (target machine), the interface utun0 (100.85.0.1) is allocated correctly and I am able to ping the interface itself: ping 100.85.0.1 -> OK Visitor side (my laptop), the interface utun0 is allocated but the client is not reachable; ping 100.85.0.1 not working -> KO. Also, pinging the interface itself does not work either: ping 100.85.0.2 -> KO ### frpc Version 0.62.1 ### frps Version 0.62.1 ### System Architecture linux/amd64 ### Configurations client: serverAddr = "mydomain.net" serverPort = 7835 user = "admin" metadatas.token = "zzzzz" transport.protocol = "tcp" transport.tls.enable = false featureGates = { VirtualNet = true } virtualNet.address = "100.85.0.1/24" [[proxies]] name = "client-vnet-test" type = "stcp" secretKey = "zzzzzzz" [proxies.plugin] type = "virtual_net" visitors: serverAddr = "mydomain.net" serverPort = 7835 user = "admin" metadatas.token = "zzzzz" transport.protocol = "tcp" transport.tls.enable = false featureGates = { VirtualNet = true } virtualNet.address = "100.85.0.2/24" [[visitors]] name = "visitors-vnet-test" type = "stcp" serverName = "client-vnet-test" secretKey = "zzzzzzz" bindPort = -1 [visitors.plugin] type = "virtual_net" destinationIP = "100.85.0.1" ### Logs No errors in log. ### Steps to reproduce 1. start client vnet 2. start visitors vnet 3. ping from visitors client ip or visitor ip -> not working ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [x] Test and Release - [ ] Developer Infrastructure - [x] Client Plugin - [x] Server Plugin - [ ] Extensions - [ ] Others