Using BBR2, QUIC, RACK Congestion Control (CC) protocols in pfSense

[Sergei_Shablovsky]

How to use modern Congestion Control (CC) transmission protocols BBR2, QUIC, RACK into pfSense ?

Or we just need to waiting until FreeBSD developers implement this CC protocols ?

P.S. Even most of iperf3/iperf servers from this official worldwide list, using BBR/CDG

[ ID] Interval           Transfer     Bitrate         Retr
.....skipped.....
CPU Utilization: local/sender 9.6% (0.9%u/8.7%s), remote/receiver 3.7% (0.9%u/2.8%s)
snd_tcp_congestion cdg
rcv_tcp_congestion bbr

[Sergei_Shablovsky]

Good News!

HowTo enable BBR in FreeBSD

Anyway, only CDG CC is better than any other in pfSense / FreeBSD 12.2... (and this list THE SAME AT LEAST 8+ YEARS!!!!)

ls -l /boot/kernel/cc_*

/boot/kernel/cc_cdg.ko
/boot/kernel/cc_chd.ko
/boot/kernel/cc_cubic.ko
/boot/kernel/cc_dctcp.ko
/boot/kernel/cc_hd.ko
/boot/kernel/cc_htcp.ko
/boot/kernel/cc_vegas.ko

[Sergei_Shablovsky]

A little bit of importance of modern CC algorithms:

HTTP/3: the past, the present, and the future

Enjoy a slice of QUIC, and Rust!

The QUICening

how CloudFlare support modern protocols Understanding Cloudflare HTTP/2 and HTTP/3 Support

Using the FreeBSD RACK TCP Stack

[viktor_g]

@sergei_shablovsky
You can create a feature request:
https://docs.netgate.com/pfsense/en/latest/development/feature-requests.html

[Sergei_Shablovsky]

@viktor_g said in Using BBR2, QUIC, RACK Congestion Control (CC) protocols in pfSense:

@sergei_shablovsky
You can create a feature request:
https://docs.netgate.com/pfsense/en/latest/development/feature-requests.html

Thank You for help.

After some declined requests, I am become to a little skeptics about reasonable (on my opinion) features added to pfSense.
But slowly industry pressure make this for me :) Just a little waiting...

BTW, I am a newbie in FreeBSD, so is possible to recompile pfSense CE code with ALL THREE options?
Or, because the modification of TCP/UDP stack are deeply underground, we able to choose only one of them (mean BBR2/BBR or QUIC or RACK) ?

[w0w]

@sergei_shablovsky
I think it's a good idea to create a feature request now. At least it will be traceable.

About recompiling... since FreeBSD 13 uses a lot of new code it is definitely takes some time to make everything work even at Netgate level. I am not newbie in FreeBSD but compiling an own version of pfSense is beyond my capabilities.

[Sergei_Shablovsky]

@viktor_g said in Using BBR2, QUIC, RACK Congestion Control (CC) protocols in pfSense:

@sergei_shablovsky
You can create a feature request:
https://docs.netgate.com/pfsense/en/latest/development/feature-requests.html

Just done.

BTW, I love the pfSense and would be happy if pfSense's product would be best on the market, and of course have all needed features on our “mobile devices world” era.
And not sitting with cubic next 7+ years and waiting...

[w0w]

@sergei_shablovsky
Are you sure that https://www.reddit.com/r/PFSENSE/comments/ajs0qy/quic_protocol/ is really useful? ;)

[Sergei_Shablovsky]

@w0w said in Using BBR2, QUIC, RACK Congestion Control (CC) protocols in pfSense:

@sergei_shablovsky
Are you sure that https://www.reddit.com/r/PFSENSE/comments/ajs0qy/quic_protocol/ is really useful? ;)
On what You skeptics based on?

At the first: I Googling about negative experience with this method and find no any. Please point me to if I am wrong.

I have no such knowledge right now to recompile FreeBSD or pfSense CE with QUIC support, so may be someone doing this and give me results for testing?

[w0w]

@sergei_shablovsky
You can try to post you request at https://forum.netgate.com/category/30/bounties
I would invest too.

[Sergei_Shablovsky]

Recently has a time to read more about BBR implementation progress. Very impressive. Just take a look on graphics “quick vs bbr”

[Sergei_Shablovsky]

Is any news about enabling QUIC in pfSense CE at the end of 2023?

Because around 90% of traffic in the world come to/from mobile gadgets, but we still using old congestion protocols in pfSense (even QUIC available in FreeBSD in that pfSense based, since several years…)