"Recent posts
#1
26.7 Series / Re: Asking for Sanity Check be...
Last post by bamf - Today at 09:03:17 PMQuote from: Chiny on Today at 06:52:09 PMSo, proof the plugin worked ?
Yes, your microcode has been updated and the version is correct. After updating your bootloader you can enable early loading and verify in dmesg as described in the mentioned thread:
Code Select
dmesg | awk '/---<<BOOT>>---/{boot=""} {boot=boot $0 "\n"} END{print boot}' | fgrep microcode #2
26.7 Series / Re: speedtest - poor download ...
Last post by OPNenthu - Today at 09:01:16 PMFor context, does this only affect the SFP+ ports (Intel X710) on the VP2420?
Asking because I recall reading somewhere that the 'igc' driver does RSS by default and those tunables would not be needed for the 2.5GbE interfaces. Can confirm that, at least on the V1410 that I own with all i226-V NICs, that is indeed the case. I have 4 RX/TX queues active with the default tunables.
Asking because I recall reading somewhere that the 'igc' driver does RSS by default and those tunables would not be needed for the 2.5GbE interfaces. Can confirm that, at least on the V1410 that I own with all i226-V NICs, that is indeed the case. I have 4 RX/TX queues active with the default tunables.
#3
26.7 Series / Re: speedtest - poor download ...
Last post by Patrick M. Hausen - Today at 08:36:28 PMThere's a section in the documentation for that:
https://docs.opnsense.org/troubleshooting/performance.html
Looks like you could set "maxthreads" to -1 to use however many cores your system has automatically. And you should possibly check "bits".
https://docs.opnsense.org/troubleshooting/performance.html
Looks like you could set "maxthreads" to -1 to use however many cores your system has automatically. And you should possibly check "bits".
#4
26.7 Series / Re: speedtest - poor download ...
Last post by topuli - Today at 08:30:42 PMthey are not there per default.
you have to create them.
in the opnsense webgui go to system/settings/tunables
in the right bottom section click the plus button.
an edit tunable window appears.
tunable is the name of the tunable variable
value of course the value
and description what ever you like
t.
you have to create them.
in the opnsense webgui go to system/settings/tunables
in the right bottom section click the plus button.
an edit tunable window appears.
tunable is the name of the tunable variable
value of course the value
and description what ever you like
t.
#5
26.7 Series / Re: speedtest - poor download ...
Last post by mekano - Today at 08:13:55 PMAre those settings in the tunable section ? I don't see them there. i have the same vp2420 as you. Thank you
#6
26.7 Series / speedtest - poor download thro...
Last post by topuli - Today at 07:40:46 PMjust wanted to leave a short note because i ran in an issue after upgrading from 26.1.11 to 26.7.1 on a protectli vp2420.
after upgrading i noticed that the download throuput was roughly half of befor the upgrade.
i also noticed a increased rtt, rttd times during the speedtest.
first i blamed the internet provider of course ;) . as an old it vetran i have learnd that the root cause is always the network (just a joke).
turned out that following settings solved the problem:
net.isr.bindthreads: 1
net.isr.numthreads: 4
net.isr.maxthreads: 4
the original values:
net.isr.bindthreads: 0
net.isr.maxthreads: 1
net.isr.numthreads: 1
if i think about it, the original values dont make much sense for a 4 core system but worked for 26.1.11. However they did not for 26.7.1
keep in mind this is for a protectli vp2420 4 cores.
have a good time
t.
after upgrading i noticed that the download throuput was roughly half of befor the upgrade.
i also noticed a increased rtt, rttd times during the speedtest.
first i blamed the internet provider of course ;) . as an old it vetran i have learnd that the root cause is always the network (just a joke).
turned out that following settings solved the problem:
net.isr.bindthreads: 1
net.isr.numthreads: 4
net.isr.maxthreads: 4
the original values:
net.isr.bindthreads: 0
net.isr.maxthreads: 1
net.isr.numthreads: 1
if i think about it, the original values dont make much sense for a 4 core system but worked for 26.1.11. However they did not for 26.7.1
keep in mind this is for a protectli vp2420 4 cores.
have a good time
t.
#7
26.7 Series / Re: mDNS forwarding between tw...
Last post by IsaacFL - Today at 07:33:01 PMYou will also need firewall rules to allow printing in addition to the MDNS. MDNS just locates the printers address.
#8
General Discussion / Re: Super strange Bridge issue...
Last post by clst - Today at 07:31:04 PMThanks for the reply.
I also have a few switches but my OPNSense box has 5 2.5G ports and I wouldn't want those to go to waste.
Yeah, the phone is a bit weird. I am guessing the internal memory is too full to grab a lot of packets. That's not really a big concern.
STUN shouldn't matter because the PBX is reachable on the internal network in the same subnet as the phone.
I'll try a packet capture on the OPNSense. It might be something odd with the NAT rules for the upstream trunk. Those shouldn't do anything to the LAN/Bridge and there is nothing in the log, but maybe it does.
Phone might be doing SIP over UDP and the PC over TCP even if using the same settings.
I was just confused that the bridge with a rule to "allow all" acts differently than the bridge with packet filtering off. Only thing I can imagine acting differently is the NAT (I think that also is completely disabled with filtering off).
Sorry for the vague details but I didn't want to just dump my whole config and I really can't think of the relevant settings. So I was trying to fish for a "Oh yeah, that's what happened to me" type answer. Thanks for the input. If I find anything I'll be sure to post again.
I also have a few switches but my OPNSense box has 5 2.5G ports and I wouldn't want those to go to waste.
Yeah, the phone is a bit weird. I am guessing the internal memory is too full to grab a lot of packets. That's not really a big concern.
STUN shouldn't matter because the PBX is reachable on the internal network in the same subnet as the phone.
I'll try a packet capture on the OPNSense. It might be something odd with the NAT rules for the upstream trunk. Those shouldn't do anything to the LAN/Bridge and there is nothing in the log, but maybe it does.
Phone might be doing SIP over UDP and the PC over TCP even if using the same settings.
I was just confused that the bridge with a rule to "allow all" acts differently than the bridge with packet filtering off. Only thing I can imagine acting differently is the NAT (I think that also is completely disabled with filtering off).
Sorry for the vague details but I didn't want to just dump my whole config and I really can't think of the relevant settings. So I was trying to fish for a "Oh yeah, that's what happened to me" type answer. Thanks for the input. If I find anything I'll be sure to post again.
#9
26.7 Series / System Backup - os-git-backup ...
Last post by IsaacFL - Today at 07:22:32 PMI recently installed the os-git-backup for system backup. I created a private repository on GitHub and have it working via SSH to GitHub.
I do have the firewall log outgoing port 22 and I notice that it is going out via the Tayga interface. It works, but that seems odd as the Opnsense router has working IPv4?
I do have the firewall log outgoing port 22 and I notice that it is going out via the Tayga interface. It works, but that seems odd as the Opnsense router has working IPv4?
#10
26.7 Series / Re: Asking for Sanity Check be...
Last post by Chiny - Today at 06:52:09 PMOK, all that gave me an idea. This worked for my Intel N100.
Uninstall the Intel microcode plugin, reboot.
I suspect 0x0000000e must be the microcode version loaded by the BIOS.
Reinstall the Intel microcode plugin, reboot.
Microcode version 0x00000021; which according to the Intel words is the latest version of microcode for my N100.
So, proof the plugin worked ?
Uninstall the Intel microcode plugin, reboot.
Code Select
sudo kldload cpuctl
sudo cpucontrol -m 0x8b /dev/cpuctl0
MSR 0x8b: 0x0000000e 0x00000000I suspect 0x0000000e must be the microcode version loaded by the BIOS.
Reinstall the Intel microcode plugin, reboot.
Code Select
sudo cpucontrol -m 0x8b /dev/cpuctl0
MSR 0x8b: 0x00000021 0x00000000Microcode version 0x00000021; which according to the Intel words is the latest version of microcode for my N100.
So, proof the plugin worked ?
