Topics

Hi Team,

Just wondering if anyone else on 23.7 has static nullroutes and whether they're able to propagate those in BGP?

For reference, have tried static redistribution as well as no distribution.
BGP network statements are there of course; also working in 23.1 with no redist defined.

Under System > Routes > Configuration, 10.x.0.0/16 set with next-hop Null4 - 127.0.0.1
Under System > Routes > Status, the static null is present with next-hop 127.0.0.1 and flags USB (UGSB in 23.1)

Notably, per the flags table on below page, the flag G for Gateway is missing.
https://docs.opnsense.org/manual/routes.html#flags

Under Routing > Diagnostics > BGP > IPv4 Routing Table, the above static null is present but shown as invalid.
Under Routing > Diagnostics > General, no route is present for the static null.

The subnet is to act as an aggregate for more specific subnets within the same domain, such as interfaces.
Those propagate properly as /24's

Edit: Sorry, I read the table wrong, originally I said 23.7 flags were UGS, but it's actually USB; missing G for Gateway. Modified above. 23.1 was correct as UGSB
Also added IPv6 nullroutes to my 23.7 instance and the behaviour/flags are identical as IPv4. 23.1 has correct behaviour with both families.

I have an issue with bad torrent performance (potentially related to concurrent connections) that I have today narrowed as being introduced in 21.7.4 ... apologies in advance as a wall of text ensues.

Been sitting on this issue of mine since I first observed it when 21.7.5 was released, many months ago.
Since then, I have periodically failed at attempts to upgrade software from 27.7.1 to a later release. Eventually rolling back and ignoring it for a long period.

Specs:
Proxmox 6.5 to 7.2 . 1000/500M fibre internet.
OPNsense VM: virtio nics, openvswitch bridges, host cpu, 4G RAM, zfs/ufs storage as scsi.

Events:
- 21.7.5 was attempted initially at time of release, but rolled back due to torrent performance issue.
- 22.1 attempted at release also experienced the same problem, resulting in rollback.
- Tried 22.1.6 this weekend, and same issue apparent.
- Tried to settle on 21.7.8, but same issue apparent.
- Determined issue was at or before 21.7.5, when the issue first presented...

Went through versions incrementally, from 21.7.1 until performance obviously deteriorated, which was in 21.7.4.

Between 21.7.3 and 21.7.4 something broke that drastically affects torrent performance.
Any other issue that might be present aren't as obvious as the performance degradation on torrents.
Speedtests appear fine between known good and bad versions, so theorised likely related to volume of connections.

Torrent seeding:
- Reference constant in 21.7.3; ~230 peers -- ~10000-20000 states
- Reference constant in 22.1.6; ~10 peers -- ~4800-6000 states

The presentation of issue is immediately apparent if I boot a 'good' or 'bad' release.
- If I boot a good version, the load ramps quickly. Most obvious is HDD noise lol.
- If I boot a bad version, there is no significant load and connections remain low.

Reading the 21.7.4 notes, nothing seems particularly obvious to me. RSS might be the most relevant, though the notes suggest the capability is introduced but defaults to disabled. I would expect something in driver, kernel or system to be relevant.

Various configurations have been attempted across 3 PVE hosts with different PHY adapters (mostly Intel); I1219-LM, X520-DA2, I225-LM. A Chelsio T520-CR has also been used.

I have not tested on a baremetal system, nor extensively with non-virtio adapters (though have tried e1000 on an earlier occasion without a positive outcome).
Have not tried the native Linux Bridging on testing systems, but have run it historically on non-afllicted versions with no distinct difference in performance.
Tried the tunable for RSS enablement in 21.7.4 (per the release notes) with no apparent success.

I have two VM's (21.7.3_3 and 22.1.6) on my PVE host that I have been booting between to compare outcomes.
Happy to perform any useful tests where time permits.

The reason I open with an apology is due to the length of time I have sat on a problem, and any potential shortfalls in providing enough useful information.
Hoping there is an issue that may either be obvious, or just overlooked while I was digging for information.

Thank you for your patience.

Also, much gratitude to OPNsense contributors. Have been using OPNsense since 19.1 and definitely want to continue doing so.