Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - miroco

#16
General Discussion / Re: Internet randomly dies
August 31, 2021, 06:00:47 PM
I read somewhere in the forum about someone who configured one network port with a different ip-range, to be able to access the box in a situation just like this.

Found it: https://forum.opnsense.org/index.php?topic=23222.0

I set one up with a simple pass rule just in case I lock myself out of the other LAN port.
#18
I'd take Teklager's advice regarding fine-tuning OPNsense and APU2x4 to 1Gbit throughput with a grain of salt, since it's never been updated. On pfSense, however the advice has been upgrade thrice.

The OPNsense advise is not dated, but from a screenshot you can deduce that it's from 2019. The pfSense advice is dated, with the original post from 2019-01-15 with there subsequent updates, 2020-07-19, 2020-10-28 and 2021-02-20

https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/

"Gigabit config for pfSense 2.5.0. No tweaks are required! Don't follow any of the information listed below for pfSense 2.4.5."

If I'm not misinformed both OPNsense 21.1 and pfSense 2.5.0 are based on FreeBSD 12.2. Tuning these two system should consequently be pretty similar.

miroco
#19
Thank you, I appreciate the feedback.


miroco
#20
Are there any plans of having AdGuard Home incorporated into OPNsense official repository?

I'm on LibreSSL flavour.


miroco
#21
If you need to remove a patch, do you still run it a second time?

https://forum.opnsense.org/index.php?topic=4682.msg18201#msg18201


miroco
#22
Have you checked so it's not dpinger causing a false positive?

https://github.com/dennypage/dpinger



miroco
#23
Are "Block private networks" and "Block logon networks" checked on the WAN interface?


miroco
#24
21.1 Legacy Series / Re: Tunables mismatch
February 12, 2021, 12:14:19 AM
Thanx  :)
#25
21.1 Legacy Series / [Solved] Tunables mismatch
February 11, 2021, 08:16:36 PM
I'm experiencing an inconsistency between tunable names and description on the main Tunables page and individual settings.

I reverted to the default tunables, but the inconstancies persist.

An example:
#26
I'm on the v4.13.01, but I have an APU2C4. The upgrade was uneventful.

Did you perform a cold boot after the firmware upgrade?

The fact that two dissimilar files have different checksums is of cause expected.

"Warning: Chip content is identical to the requested image."

It's as if you ran the same upgrade twice.

miroco
#27
This from my APU2C4; I think you just missed the two last characters of the string whilst copying it.

root@opnsense:~ # sysctl -a | grep -E 'dev.(igb|ix|em).*.%desc:'
dev.igb.2.%desc: Intel(R) PRO/1000 PCI-Express Network Driver
dev.igb.1.%desc: Intel(R) PRO/1000 PCI-Express Network Driver
dev.igb.0.%desc: Intel(R) PRO/1000 PCI-Express Network Driver
#28
I have also been scratching my head over this. The system - general log show that DROP .txt file has been fetched, but not the EDROP file. If I on the other hand check under diagnostics and pfTables, both DROP/EDROP are there. The content of the two .txt files that is. Go figure.

miroco
#29
Nice write-up.

May I suggest that you move it to "Tutorials and FAQs"?


miroco
#30
Another Speedtest service gave a very different result. In hindsight, I should have done this from the very beginning. Gotten a second opinion that is. ::)

Some pages still take longer to load, something I guess can be attributet to a different user pattern caused by the ongoing covid-19 pandemic.


miroco