Was HTTP/3 taken into account with its use of QUIC and UDP when deciding that? I’m wondering what impact that would have not being accelerated.
1 Like
Interesting! In addition to what @jcolp mentioned, if some of these speed tests are using UDP then that would probably expalain the behavior some are seeing.
If it makes sense, it would be nice if that was called out in the release notes to help keep users aware of any potential changes in behavior in regards to the hardware acceleration 
1 Like
Interesting findings on UDP! Does this still fit with by disabling hardware acceleration my speed tests seem to return to normal? Does having hardware acceleration enabled somehow depriotize UDP traffic in 1.4l?
I re-enabled UDP acceleration this morning, and it did improve things. An iperf3 with UDP on my 2.5Gbps connected desktop is now at 2.4Gbps symmetrical.
1 Like
Thanks Jeff
That might be a good option to be added into the GUI so others be made aware of this option
Has anyone gotten any alerts from IPS on this new firmware? I got one immediately after the upgrade but nothing in 10 days. Bitdefender indicates theres still plenty of things getting through.
edit: Toggle off, reset rules, reboot, toggle it all back on, test with testmyids.org, and got alerts now. Not sure what happened between the alert on Nov 14th and today but at least its working.
I’ve generally been getting alerts, although the site I’m at right now didn’t flag anything when I navigated to testmyids.org despite IDS being on 
So I still feel like it’s a bit finicky, although I’d want to test it out a bit more at a few other sites
Yes, I get alerts, and when adding the Block Duration I see iptables rules come and go for for the corresponding duration and Block Level matches. 
Setting it to Low is aggressive and one has to set the notification level to Low and do some "ignore rule/signature* for those most common false positives, otherwise the firewall and event log will be flooded. The last being a major issue now (at least if notification on low level) as there seems to be a cap for the event log shown in the UI (capped at 239).
I haven’t checked up again on the initial response/deletion.
curl to testmyids.org and iptables entries:
root@08-AP6Pro-GndFl:~# curl -v testmyids.org
> GET / HTTP/1.1
> Host: testmyids.org
> User-Agent: curl/7.76.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Accept-Ranges: bytes
< Content-Length: 39
< Content-Type: text/html; charset=utf-8
< Server: Caddy
< Vary: Accept-Encoding
< Date: Thu, 27 Nov 2025 20:13:15 GMT
<
uid=0(root) gid=0(root) groups=0(root)
root@08-AP6Pro-GndFl:~#
root@08-AP6Pro-GndFl:~# curl -v testmyids.org
* Failed to connect to testmyids.org port 80: Operation timed out
curl: (28) Failed to connect to testmyids.org port 80: Operation timed out
root@08-AP6Pro-GndFl:~#
and grep for ips in /var/log/messages
Nov 27 20:13:15.586 01-Route10-Rack daemon.alert ips: run "iptables -A ips -s 152.53.82.239 -d 192.168.1.8 -j DROP"
Nov 27 20:13:15.590 01-Route10-Rack daemon.alert ips: run "iptables -A ips -s 192.168.1.8 -d 152.53.82.239 -j DROP"
root@01-Route10-Rack:~#
and
grep for ips in iptables:
root@01-Route10-Rack:~# iptables -S | grep ips
-N ips
-A forwarding_rule -j ips
-A ips -s 152.53.82.239/32 -d 192.168.1.8/32 -j DROP
-A ips -s 192.168.1.8/32 -d 152.53.82.239/32 -j DROP
root@01-Route10-Rack:~#
@Alta-Jeff CPU usage is spiking up to 88% when performing a speed test with this version. Hardware Acceleration is on (default setting) with IPS on. I did a speed test with no other custom routing, so I almost am using default settings. My internet plan is 500 mbits, this is not even 1G. I’m pretty sure the previous version doesn’t have this issue.
Anyone experiencing the same issue?
Do we have an option to go back to the previous firmware version – 1.4k?
Did you try to re-enable udp acceleration like mentioned here: Route10 Firmware 1.4l Released! - #40 by Alta-Jeff
I didn’t at first. But I tried it, and It didn’t make a difference.
You can reach out to support, or invite me to your site, to downgrade the firmware. However, as long as you run echo 4 > /cfg/alta_bits and reboot, UDP acceleration should be re-enabled, just like in 1.4k.
This fixed my issue.
speed tests are back to normal. CPU% are back to normal. QUIC based traffic seems to be working better as well (which is UDP based as someone else mentioned)