Messages

Just a not that we eventually figured this problem out. It was due to an overheating fanless switch; after replacing it the issues went away.

It's the little orange cloud button with "Import" hover text in the bottom right corner; it's not very prominent.

It's certainly possible; the patch referenced in the bug report has not been merged to OPNsense yet.

Could you open an issue at https://github.com/opnsense/src with the information you provided here?

It may or may not be in 21.1.3 and it may or may not fix your issue (it did not fix mine, despite initial hope).

For me the PR I mentioned it unfortunately hasn't solved the connection problems. Back to the drawing board!

What sort of hardware do you see the problem with, particular what kind of NICs?

I'm experiencing something similar, see https://forum.opnsense.org/index.php?topic=21145.0

The issue was present for me in 20.7 as well; did you test any versions before 21.1?

Possibly related: https://github.com/opnsense/src/issues/107

This issue may apply to you: https://github.com/opnsense/src/issues/107

If you don't want to update to 21.1 to try the test-kernel, you could test the workarounds mentioned in the referenced pfSense forum thread; most importantly disabling SMP using the tunable kern.smp.disabled=1

This issue may apply to you: https://github.com/opnsense/src/issues/107

If you don't want to update to 21.1 to try the test-kernel, you could test the workarounds mentioned in the referenced pfSense forum thread; most importantly disabling SMP using the tunable kern.smp.disabled=1

hi,

can you tell me, what for a network card you use ?

Because: https://forum.opnsense.org/index.php?topic=21663.0

NIC in use: Intel i210AT. The problems I have sound different from the ones you describe.

I have since updated to OPNsense 21.1.2.

The issue on the WAN connection appears to have been fixed by moving to a different switch port. The issues on the LAN port persist though; there have been fixes related to iflib/igb/VLAN in FreeBSD, so I'm trying to figure out whether any of them may help.

Hi,

I'm experiencing some network problems (see https://forum.opnsense.org/index.php?topic=21145.msg98865#msg98865) where my gut still tells me they may be related to the iflib'ified version of igb(4). I would like to check whether the problems also appear with a stock FreeBSD 12-STABLE kernel, since 12-STABLE contains a slew of fixes in that area that haven't been merged back to OPNsense yet.

Is a stock FreeBSD kernel likely to work with the OPNsense, or does the OPNsense depend on kernel extensions (e.g. tunables etc) not in FreeBSD?

The stunnel part is optional. It's just a way to get an unencrypted connection without transferring everything in the plain over the wire. If this is a small controlled environment you can of course just use plain LDAP on port 389.

I just tried to recreate the config I suggested to send you a screenshot and embarrassingly enough stunnel on OPNsense does not support client mode. Sorry! In pfSense it does.

OK, now I know which plugin I am working on next. This is essential.

So you are really stuck with using plain text LDAP if you want to use tcpdump.

Just to note, there's already a pull request related to this: https://github.com/opnsense/plugins/pull/2166

Good suggestion, I'll give it a try, thanks. Updating to 21.1 did not help in any case.

[We only observe the issues on if1 and if2, never on if3.]

Hi Forum,

I'm trying to debug a curious problem that's been plaguing us for a while now (first time reported to me October 2020). We're seeing regular packet loss / latency spikes for ~30 seconds, which is particularly disrupting during video calls.

Our setup:

PC Engines APU2D4 (co-located) currently running OPNsense 20.7.8 as router/firewall. The system has been in place for 2 years, and we've only seen issues recently.

Interface 1 (if1): WAN
Interface 2 (if2): carries 3 VLANs (our internal network) to our offices in another building
Interface 3 (if3): DMZ

Ifs 1 and 2 are connected to the server room switch, if3 is connected to two servers through our own small switch.

We only observe the issues on if1 and if2, never on if3.

I'm monitoring all three interfaces from OPNsense through monit ping tests to the next available system (upstream router on if1, our own switch on if2, both servers on if3).

Because we only see issues on if1 and if2, e.g. the ones connected to the server room network equipment, I thought the problem could be there. While I'm still monitoring that, I think it can increasingly rule out this possibility.

Things I've (unsuccessfully) tried on the router:
- downgrade to 20.7.4 (the version preceding the first problem report)
- disable flow control (dev.igb.X.fc=0)
- disable TSO (net.inet.tcp.tso=0)

I don't see any suspicious messages in the logs.

My gut feeling is that this may be an issue with the new iflib-ified igb(4), but I'm puzzled that we don't see these issues on if3.

I've though about downgrading to OPNsense 20.1.9 as a test; would that be possible from a 20.7.8-based system, or result in issues with the configuration?

Thanks for reading, if anyone has an idea I'm all ears.

Thanks!