Recent posts

#21

Q-Feeds (Threat intelligence) / automatic upgrade api

Last post by RamSense - Today at 07:28:16 AM

I just ordered a plus upgrade. I was already using the free api key.
I noticed that after paying for the upgrade, and received confirmation, it stays free.
Than i read that i have to go into the tip-qfeeds account and edit my free api key to change it to plus.

I think it will be very convenient for the user to have this api altered to this paid version automatically, instead of now manually.
Why would a user want its api to stay free when he/she just ordered an upgrade?

p.s. is there a way to check if my qfeeds plugin is getting the plus feed instead of the free? And should i alter my url in Adguard Home for this plus package? or is there another url only for plus to use in adguard home?

#22

Hardware and Performance / Re: [solved] Intel i226 Firmwa...

Last post by Seimus - Today at 02:38:58 AM

Testing a new N355 system,

It came with the i226-V firmware:

Code Select Expand

[1] igc0: EEPROM V2.22-0 eTrack 0x80000371
[1] igc1: EEPROM V2.22-0 eTrack 0x80000371
[1] igc2: EEPROM V2.22-0 eTrack 0x80000371
[1] igc3: EEPROM V2.22-0 eTrack 0x80000371

Upgraded to 2.32 using the 2MB file, process was without problems.

Code Select Expand

CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

; NIC device
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Controller I226-V
VENDOR: 8086
DEVICE: 125C
SUBVENDOR: 8086
SUBDEVICE: 0000
NVM IMAGE: FXVL_125C_V_2MB_2.32.bin
EEPID: 80000422
RESET TYPE: REBOOT
REPLACES: 80000371
END DEVICE


Code Select Expand

[1] igc0: EEPROM V2.32-0 eTrack 0x80000422
[1] igc1: EEPROM V2.32-0 eTrack 0x80000422
[1] igc2: EEPROM V2.32-0 eTrack 0x80000422
[1] igc3: EEPROM V2.32-0 eTrack 0x80000422


Code Select Expand

[00:004:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)
[00:005:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)
[00:006:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)
[00:007:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)


Thanks for the guide!

Regards,
S.

#23

Hardware and Performance / Re: Shaper Limit on N150/igc -...

Last post by Seimus - Today at 01:00:24 AM

;)

Regards,
S.

#24

25.7, 25.10 Series / Re: IPv6 on a routed network

Last post by nhendriks - Today at 12:56:26 AM

Hmm, changed it and now I can ping 2a02:898:331::1 and 2a02:898:331:1:: from my Proxmox machine but no other even though ICMPv6 is allowed from all sources, still can't ping towards the the internet from my OPNsense machine or any of my VMs. Still complaining about routes not existing :(

#25

Tutorials and FAQs / Re: OPNsense aarch64 firmware ...

Last post by Maurice - Today at 12:46:38 AM

@franco

Looking better? Want to give it a try? Feedback welcome!

https://github.com/opnsense/core/compare/stable/25.7...maurice-w:opnsense-core:stable/25.7

#26

German - Deutsch / Re: Shaper (FlowQueue-CoDel) l...

Last post by FireStorm - Today at 12:07:07 AM

Ich habe hier noch zwei USB-Netzwerkadapter (1x 2,5G und 1x 5Gbit RJ45). Damit könnte ich die igc-Ports testweise umgehen, um zu sehen, ob der Fehler eventuell am Treiber der Intel-Ports liegt. Oder um den oben erwähnten Test durchzuführen.

Äh nein. USB NICs sind prädestiniert dafür mieserabel zu funktionieren und machen mehr Ärger als irgendwas. Da würde ich für irgendwas halbwegs produktives WEIT die Finger davon lassen :)

Danke für den Hinweis!

Dank @Seimus habe ich meine BW verbessert und bekomme jetzt konstant ein Grade A! Wir haben die Config auf Basis der Doku aktualisiert und noch etwas Feintuning betrieben.

Leider konnten wir die Download-Latenz aufgrund der Natur von 5G nicht dauerhaft unter 10ms halten. Ein großes Danke an Seimus für die Hilfe dabei, den Sweet Spot zu finden! :D"

#27

Hardware and Performance / Re: Shaper Limit on N150/igc -...

Last post by FireStorm - Today at 12:04:38 AM

Thanks to @Seimus, I've improved my BW and am now getting a constant Grade A! We updated the config based on the docs and did some fine-tuning.

Unfortunately, because of the nature of 5G, we couldn't get the download latency to stay below 10ms consistently. Big thanks to Seimus for his help finding the sweet spot! :D

#28

25.7, 25.10 Series / Re: Slow server download speed...

Last post by xXHelperXx - November 19, 2025, 11:47:05 PM

I think this is something with the recent version.
2 weeks ago I noticed a slow connection from my end.

The connections is:  NAS > OpnSense > wireguard > Remote Client.
and the System is with i3-1215U that handle everything.

At First I though it's the NAS, but apparently this is something with OPS.
Iperf between the NAS > OPS I getting 2.74 GBytes.
Between OpnSense > wireguard > Remote Client I'm getting average of 53.0 MBytes |  44.5 Mbits/sec.

Before the update to 27.5.x I managed to received 200+ MB with Iperf and transfer files around 22mb/s with the same system and same configuration, nothing changed.
I also try to disable firewall, CrwordSec, IDS, IPS, change MTU, paly with offload settings and add some configuration to the Tunables.
Unfortunately nothing help to solve it.

I believe It's a deeper issue.

#29

25.7, 25.10 Series / Re: Wireguard & LAN-LAN SMB

Last post by JMini - November 19, 2025, 11:11:52 PM

It was a shared folder network permission setting in QNap.
Under Shared folder permissions. It defaults to user & group permissions, but there's also microsoft networking host access in a drop down list.
Once there, only my 10.10.20.* network was entered. So I added the 10.10.40.* network and my WireGuard 10.10.70.* network.

It works like a charm now

#30

25.7, 25.10 Series / Re: SSD get's massively writte...

Last post by senseOPN - November 19, 2025, 11:02:14 PM

Netflow. It's by far the generator of the largest amount of any data you can have on OPNsense. Export Netflow data to an external collector like ElastiFlow

But then again let's assume you write 40 GB per day. With a typical TBW of 200 for a smaller quality SSD that means you get 5.000 guaranteed days of operation or over 13 years.

Many thanks, I will disable NetFlow for now and check if this betters the situation.

While you may be right about the usage, I just don't like the idea that more data get's written to the SSD than I am transferring over the net in the same time.
That is just not right.