[GH-ISSUE #3924] QUIC Protocol is not working on FreeBSD #3113

New issue

Closed

opened 2026-05-05 14:00:59 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 14:00:59 -06:00

Owner

Originally created by @hyoseupjang on GitHub (Jan 11, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3924

Bug Description

The QUIC protocol is not working properly in frps for FreeBSD while TCP works fine.

frpc Version

Not Affected

frps Version

Tested on 0.53.2, 0.52.3

System Architecture

FreeBSD/amd64

Configurations

Server side conf

bindPort = 443
quicBindPort = 443

Client side conf

serverAddr = "127.0.0.1"
serverPort = 443
transport.protocol = "quic" #If I comment this line, works well. 
[[proxies]]
name = "test-tcp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 6000

Logs

Server side (Not showing activity)

root@freebsd:~ # ./frps -c frps.toml
2024/01/11 11:31:17 [I] [root.go:102] frps uses config file: frps.toml
2024/01/11 11:31:17 [I] [service.go:200] frps tcp listen on 0.0.0.0:443
2024/01/11 11:31:17 [I] [service.go:226] frps quic listen on quic 0.0.0.0:443
2024/01/11 11:31:17 [I] [root.go:111] frps started successfully

Client side (FreeBSD Localhost)

root@freebsd:~ # ./frpc -c frpc.toml
2024/01/11 11:31:27 [I] [root.go:139] start frpc service for config file [frpc.toml]
2024/01/11 11:31:32 [W] [service.go:131] login to server failed: timeout: no recent network activity
2024/01/11 11:31:32 [I] [root.go:154] frpc service for config file [frpc.toml] stopped

Client side (Linux Remote)

[*****@**** frp]$ ./frpc -c frpc.toml
2024/01/11 11:31:46 [I] [root.go:141] start frpc service for config file [frpc.toml]
2024/01/11 11:31:46 [I] [service.go:287] try to connect to server...
2024/01/11 11:31:51 [W] [service.go:290] connect to server error: timeout: no recent network activity
2024/01/11 11:31:51 [I] [root.go:159] frpc service for config file [frpc.toml] stopped
login to the server failed: timeout: no recent network activity. With loginFailExit enabled, no additional retries will be attempted

Steps to reproduce

Prepare a FreeBSD machine and download frps. (Tested on AWS Lightsail and OPNsense router OS) Freebsd Ports version is also affected.
Test with QUIC configuration. "nc -lu 443" command shows this is not a firewall problem.

Affected area

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

Originally created by @hyoseupjang on GitHub (Jan 11, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3924 ### Bug Description The QUIC protocol is not working properly in frps for FreeBSD while TCP works fine. ### frpc Version Not Affected ### frps Version Tested on 0.53.2, 0.52.3 ### System Architecture FreeBSD/amd64 ### Configurations # Server side conf ``` bindPort = 443 quicBindPort = 443 ``` # Client side conf ``` serverAddr = "127.0.0.1" serverPort = 443 transport.protocol = "quic" #If I comment this line, works well. [[proxies]] name = "test-tcp" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 6000 ``` ### Logs # Server side (Not showing activity) ``` root@freebsd:~ # ./frps -c frps.toml 2024/01/11 11:31:17 [I] [root.go:102] frps uses config file: frps.toml 2024/01/11 11:31:17 [I] [service.go:200] frps tcp listen on 0.0.0.0:443 2024/01/11 11:31:17 [I] [service.go:226] frps quic listen on quic 0.0.0.0:443 2024/01/11 11:31:17 [I] [root.go:111] frps started successfully ``` # Client side (FreeBSD Localhost) ``` root@freebsd:~ # ./frpc -c frpc.toml 2024/01/11 11:31:27 [I] [root.go:139] start frpc service for config file [frpc.toml] 2024/01/11 11:31:32 [W] [service.go:131] login to server failed: timeout: no recent network activity 2024/01/11 11:31:32 [I] [root.go:154] frpc service for config file [frpc.toml] stopped ``` # Client side (Linux Remote) ``` [*****@**** frp]$ ./frpc -c frpc.toml 2024/01/11 11:31:46 [I] [root.go:141] start frpc service for config file [frpc.toml] 2024/01/11 11:31:46 [I] [service.go:287] try to connect to server... 2024/01/11 11:31:51 [W] [service.go:290] connect to server error: timeout: no recent network activity 2024/01/11 11:31:51 [I] [root.go:159] frpc service for config file [frpc.toml] stopped login to the server failed: timeout: no recent network activity. With loginFailExit enabled, no additional retries will be attempted ``` ### Steps to reproduce 1. Prepare a FreeBSD machine and download frps. (Tested on AWS Lightsail and OPNsense router OS) Freebsd Ports version is also affected. 2. Test with QUIC configuration. "nc -lu 443" command shows this is not a firewall problem. ### 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 14:00:59 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:01:02 -06:00

Author

Owner

@g9420 commented on GitHub (Jan 16, 2024):

I'm having this problem too, my system is ubuntu 22

@g9420 commented on GitHub (Jan 16, 2024): I'm having this problem too, my system is ubuntu 22

gitea-mirror commented

2026-05-05 14:01:02 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 7, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Feb 7, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:01:03 -06:00

Author

Owner

@devnoname120 commented on GitHub (Jul 14, 2024):

Edit: never mind for me it was just a firewall issue. Only TCP inbound was whitelisted, once I added UDP to the whitelist it worked.

~~Same problem.~~

frps:

root@ubuntu:~# neofetch
            .-/+oossssoo+/-.               root@ubuntu
        `:+ssssssssssssssssss+:`           -----------
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 24.04 LTS x86_64
    .ossssssssssssssssssdMMMNysssso.       Host: KVM/QEMU (Standard PC (i440FX + PIIX, 1996) pc-i440fx-6.1)
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 6.8.0-38-generic
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 1 day, 14 hours, 32 mins
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 766 (dpkg), 4 (snap)
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.2.21
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Terminal: /dev/pts/2
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   CPU: AMD EPYC-Milan (1) @ 1.996GHz
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   GPU: 00:02.0 Red Hat, Inc. QXL paravirtual graphic card
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Memory: 224MiB / 848MiB
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
  +sssssssssdmydMMMMMMMMddddyssssssss+
   /ssssssssssshdmNNNNmyNMMMMhssssss/
    .ossssssssssssssssssdMMMNysssso.
      -+sssssssssssssssssyyyssss+-
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

frpc:

ubuntu@ubuntu:~$ neofetch
            .-/+oossssoo+/-.               ubuntu@ubuntu
        `:+ssssssssssssssssss+:`           -------------
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 24.04 LTS aarch64
    .ossssssssssssssssssdMMMNysssso.       Host: Apple Mac mini (M1, 2020)
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 6.8.0-1011-asahi-arm
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 13 days, 7 hours, 21 mins
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 1524 (dpkg)
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.2.21
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Terminal: etterminal
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   CPU: (8) @ 2.064GHz
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   Memory: 3772MiB / 7570MiB
+sssshhhyNMMNyssssssssssssyNMMMysssssss+
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
  +sssssssssdmydMMMMMMMMddddyssssssss+
   /ssssssssssshdmNNNNmyNMMMMhssssss/
    .ossssssssssssssssssdMMMNysssso.
      -+sssssssssssssssssyyyssss+-
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

@devnoname120 commented on GitHub (Jul 14, 2024): **Edit**: never mind for me it was just a firewall issue. Only TCP inbound was whitelisted, once I added UDP to the whitelist it worked. --------- ~~Same problem.~~ frps: ``` root@ubuntu:~# neofetch .-/+oossssoo+/-. root@ubuntu `:+ssssssssssssssssss+:` ----------- -+ssssssssssssssssssyyssss+- OS: Ubuntu 24.04 LTS x86_64 .ossssssssssssssssssdMMMNysssso. Host: KVM/QEMU (Standard PC (i440FX + PIIX, 1996) pc-i440fx-6.1) /ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 6.8.0-38-generic +ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 1 day, 14 hours, 32 mins /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 766 (dpkg), 4 (snap) .ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 5.2.21 +sssshhhyNMMNyssssssssssssyNMMMysssssss+ Terminal: /dev/pts/2 ossyNMMMNyMMhsssssssssssssshmmmhssssssso CPU: AMD EPYC-Milan (1) @ 1.996GHz ossyNMMMNyMMhsssssssssssssshmmmhssssssso GPU: 00:02.0 Red Hat, Inc. QXL paravirtual graphic card +sssshhhyNMMNyssssssssssssyNMMMysssssss+ Memory: 224MiB / 848MiB .ssssssssdMMMNhsssssssssshNMMMdssssssss. /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ +sssssssssdmydMMMMMMMMddddyssssssss+ /ssssssssssshdmNNNNmyNMMMMhssssss/ .ossssssssssssssssssdMMMNysssso. -+sssssssssssssssssyyyssss+- `:+ssssssssssssssssss+:` .-/+oossssoo+/-. ``` frpc: ``` ubuntu@ubuntu:~$ neofetch .-/+oossssoo+/-. ubuntu@ubuntu `:+ssssssssssssssssss+:` ------------- -+ssssssssssssssssssyyssss+- OS: Ubuntu 24.04 LTS aarch64 .ossssssssssssssssssdMMMNysssso. Host: Apple Mac mini (M1, 2020) /ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 6.8.0-1011-asahi-arm +ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 13 days, 7 hours, 21 mins /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 1524 (dpkg) .ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 5.2.21 +sssshhhyNMMNyssssssssssssyNMMMysssssss+ Terminal: etterminal ossyNMMMNyMMhsssssssssssssshmmmhssssssso CPU: (8) @ 2.064GHz ossyNMMMNyMMhsssssssssssssshmmmhssssssso Memory: 3772MiB / 7570MiB +sssshhhyNMMNyssssssssssssyNMMMysssssss+ .ssssssssdMMMNhsssssssssshNMMMdssssssss. /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ +sssssssssdmydMMMMMMMMddddyssssssss+ /ssssssssssshdmNNNNmyNMMMMhssssss/ .ossssssssssssssssssdMMMNysssso. -+sssssssssssssssssyyyssss+- `:+ssssssssssssssssss+:` .-/+oossssoo+/-. ```