Messages

After the upgrade my rules weren't working either. After reading this post I opened my aliases and edited and re-saved each alias and they all started working.

Working perfectly fine now. Thanks!!!!

Ok to run another test I did a fresh install of 21.1 (leaving all settings in their defaults) and after the install it did show dns entries on the interface overview page for the WAN. After upgrading to 21.1.1 the dns entries are no longer shown on the WAN. I've changed no settings and haven't even touched my configuration backup.

The output of that command is:
<dnsallowoverride/>

Incase it matters I'm running inside Hyper-V.

Thank you,

edit: should be 22.1.1 not 21.1.1 (not sure why I'm having so much trouble typing the proper version)

It looks like 22.1.1 doesn't get dns on the wan connection via dhcp. I use dnsmasq for dns lookup as I want to forward my dns queries to my isp and that is what my configuration backup was doing (disabling unbound and enabling dnsmasq). If I disable dnsmasq and re-enable unbound after restoring my backup I can check for updates and dns queries work again.

I have double checked and "Allow DNS server list to be overridden by DHCP/PPP on WAN" is checked.

Is there a patch or fix that I can implement to have my wan get dns from dhcp again?

Thank you,

ok so after restoring my configuration backup my wan interface no longer picks up dns from dhcp. Quite strange.

good point it is usually always DNS  ::)

I just tried a fresh install and everything worked fine, upgrade and plugin installation. After restoring my backup from 21.7.8 I get the same issue so it's a setting being restored from my configuration backup. I'll keep digging.

Thank you,

After updating to 21.1.1 whenever I check for updates the following message is presented: No address record found for the selected mirror.

This is what is shown in the log:

Code Select Expand

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.1 (amd64/OpenSSL) at Wed Feb 16 09:18:03 EST 2022
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/sets/changelog.txz: No address record
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/meta.txz: No address record
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/latest/packagesite.txz: No address record
Unable to update repository OPNsense
Error updating repositories!
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

Have I done something wrong? Is it just taking time for the update and data to be replicated to all mirrors and I should be more patient?

Thank you,

Attached are the results of the sysctl -a | grep rsc from before the speed test and then after the speed test. Also attached are the results of the speed test.

Does anyone have any guidance on how to test udp?

Thank you,

that seems to have done it. Speeds are good with the updated kernel.

I've setup two new test vswitches (one for WAN and one for LAN). Disabled software RSC on both and now my download speeds are great but my upload speeds are still unusable.

I think this might be on to something.

Here is a full all interface packet capture while using speedtest.net. Both my upload and download are being impacted.

Packet Capture: REDACTED BY ADMIN

Thank you,

not that I expected anything to have changed in such a short period of time but I've tested against the full release 22.1 and the problem still exists.

I just tried doing a clean install of freeBSD 13 and then bootstrapping OPNsense. The freeBSD installed fine. Bootstrapping OPNsense went smooth and fast ( https://github.com/opnsense/update#opnsense-bootstrap ).  Once it rebooted and OPNsense was running it's access to the internet slowed the same as with the standard OPNsense install.

Updated to RC2 (took hours with the reduced speed) and the problem still persists.

I've been testing in Hyper-V on Windows 11. Maybe Azure is running a slightly different version of Hyper-V. I'll try spinning up a test VM on a different version of Hyper-V and see if it still happens.

Thank you,