Messages

1

24.1 Legacy Series / Re: [solved] intel x710

« on: April 24, 2024, 11:11:35 am »

I have two servers at home. One is LGA1150 and the other is LGA1151. In each system I have a nVidia graphics card I passthrough to Plex for transcoding, an IBM M1015 SCSI card running IT mode, and a NIC. I have used both an Intel i350 quad port, an Intel x550 (lga1150) and  Intel x710 (LGA1151).

The LGA1151 handles all the cards without issue. I have tried more than one manufacture of the LGA1150 and they all act the same. If I run SR-IOV on the NICs I get the reset errors you see. On the LGA1150s I have to use bridge networking on any NIC I use. Passthrough works but SR-IOV doesn't. If I removed one of the other cards, either the nVidia or the IBM M1015 SR-IOV worked. So the issue you are having might not be the OS and is an issue with your motherboard.

2

24.1 Legacy Series / Re: [solved] intel x710

« on: April 23, 2024, 06:08:38 pm »

 Since I am using passthrough with vlans I had to add a parent, that fixed my connection issues. To clear up the errors I had to redo my PIA Wiregaurd setup. No more errors.

3

24.1 Legacy Series / [solved] intel x710

« on: April 22, 2024, 12:46:45 am »

I am running Opnsense under Proxmox. I had an i350 with 4 ports. I passed one port to the Opnsense VM and set up a 3 member vlan. I upgraded my NIC to a x710 10Gbe and had to reconfigure the NIC. Now when Opnsense starts I get the error below:

ixl0: ixl_del_hw_filters: i40e_aq_remove_macvlan status I40E_ERR_ADMIN_QUEUE_ERROR, error I40E_AQ_RC_ENOENT

What is this telling me and how do I fix it?

4

Hardware and Performance / Re: High CPU-load caused by two sqlite3-processes

« on: February 13, 2024, 08:52:48 pm »

Yes, CPUINFO flages

Code: [Select]

flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti intel_ppin ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts vnmi md_clear flush_l1d
vmx flags       : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs



5

Hardware and Performance / Re: High CPU-load caused by two sqlite3-processes

« on: February 10, 2024, 02:01:50 pm »

I've tried it off and on, no difference. I can turn it off.

6

Hardware and Performance / Re: High CPU-load caused by two sqlite3-processes

« on: February 09, 2024, 10:10:58 pm »

Both the bad and good systems are set to host. Pictures attached

7

Hardware and Performance / Re: High CPU-load caused by two sqlite3-processes

« on: February 09, 2024, 04:47:17 pm »

I am resurrecting this performance thread. I am hitting this issue. Reading through the thread I don't think there was a resolution. Not sure I will get one, but thought I would ask. I have an Asus socket 1151 based x99 motherboard with an 24 x Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz. I have an Intel i350 quad port card, and an IBM 1015 SCSI adapter using IT mode. I have a 6 disk configured with ZFS RAID 10. The system runs well and gets good performance.

I noticed the same issue as the original poster, Opnsense runs as a VM under Proxmox and when I enable Netflow sqlite3 pegs the CPU. I have tried different CPU and Disk controller settings and nothing works. I have another setup almost identical. It is a SuperMicro motherboard with 8 x Intel(R) Xeon(R) CPU E3-1286L v3 @ 3.20GHz (1 Socket), same RAID controller but with an Intel x550 NIC. This system has no issues with the CPU spiking. I added the top outputs from the good and bad systems. If I turn off Netflow no more spikes on the bad system Any ideas?

here is the bad system

Code: [Select]

last pid: 54806;  load averages:  1.22,  1.24,  1.05    up 0+00:26:40  10:32:48
56 processes:  2 running, 54 sleeping
CPU: 12.1% user,  0.0% nice, 51.6% system,  1.0% interrupt, 35.4% idle
Mem: 285M Active, 2953M Inact, 5160K Laundry, 526M Wired, 304M Buf, 123M Free
Swap: 8192M Total, 8192M Free
kill
  PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
56332 root          1 102    0    18M  6848K CPU1     1  24:44  98.09% sqlite3
  290 root          1  52    0    80M    36M accept   1   0:09   1.23% python3.
57397 root          1  52    0    66M    31M accept   1   0:01   1.09% php-cgi
27172 root          1  20    0    14M  3592K CPU0     0   0:05   0.53% top
46649 root          1  20    0    60M    29M accept   1   0:01   0.44% php-cgi
18196 root          1  20    0    60M    27M accept   0   0:00   0.37% php-cgi
63469 root          1  20    0    79M    39M nanslp   1   0:05   0.29% php
20087 root          4  20    0    43M    11M kqread   1   0:01   0.11% syslog-n
92109 root          1  20    0    23M    12M select   0   0:01   0.05% python3.
10100 root          1  20    0    22M  8164K kqread   0   0:00   0.05% lighttpd
21925 root          1  20    0    25M    15M select   1   0:01   0.02% python3.
89645 root          4  52    0    13M  2528K uwait    1   0:00   0.01% dpinger
99645 root          4  52    0    13M  2528K uwait    1   0:00   0.01% dpinger
91164 root          1  20    0    23M    12M select   0   0:00   0.01% python3.
16606 unbound       2  20    0    64M    32M kqread   0   0:01   0.01% unbound
24880 dhcpd         1  20    0    25M  8160K select   0   0:00   0.01% dhcpd
38410 root          1  22    0    13M  2488K wait     1   0:00   0.01% sh


Code: [Select]

last pid: 10041;  load averages:  1.24,  1.23,  1.08    up 0+00:28:42  10:34:50
199 threads:   6 running, 166 sleeping, 27 waiting
CPU 0: 11.3% user,  0.0% nice, 39.7% system,  0.8% interrupt, 48.2% idle
CPU 1: 10.9% user,  0.0% nice, 54.5% system,  1.6% interrupt, 33.1% idle
Mem: 274M Active, 2974M Inact, 5132K Laundry, 525M Wired, 303M Buf, 116M Free
Swap: 8192M Total, 8192M Free
renice
  PID USERNAME    PRI NICE   SIZE    RES STATE    C   TIME     CPU COMMAND
56332 root        103    0    18M  6848K RUN      0  26:42  97.69% /usr/local/b
   11 root        155 ki31     0B    32K RUN      0  13:11  47.86% [idle{idle:
   11 root        155 ki31     0B    32K RUN      1  13:02  33.67% [idle{idle:
    0 root        -16    -     0B   528K swapin   0   0:16   0.00% [kernel{swap
   12 root        -60    -     0B   432K WAIT     1   0:14   0.81% [intr{swi4:
   12 root        -76    -     0B   432K WAIT     0   0:08   0.74% [intr{swi0:
    4 root        -16    -     0B    32K RUN      0   0:06   0.17% [cam{doneq0}
63469 root         20    0    79M    37M nanslp   0   0:05   0.28% /usr/local/b
   12 root        -88    -     0B   432K WAIT     1   0:02   0.17% [intr{irq32:
   12 root        -88    -     0B   432K WAIT     0   0:02   0.11% [intr{irq31:
46649 root         20    0    60M    29M accept   0   0:02   0.43% /usr/local/b
  290 root         52    0    80M    36M accept   0   0:01   0.13% /usr/local/b
    7 root        -16    -     0B    48K psleep   1   0:01   0.02% [pagedaemon{
    5 root        -16    -     0B    16K pftm     0   0:01   0.03% [pf purge]
    0 root        -76    -     0B   528K -        1   0:01   0.01% [kernel{if_c
21925 root         20    0    25M    15M select   1   0:01   0.02% /usr/local/b

the good box

Code: [Select]

last pid: 78271;  load averages:  0.46,  0.37,  0.34                                                                                                                                                                                                            up 0+15:18:28  10:39:08
197 threads:   3 running, 164 sleeping, 30 waiting
CPU 0: 10.6% user,  0.0% nice,  5.1% system,  0.8% interrupt, 83.5% idle
CPU 1: 15.3% user,  0.0% nice,  5.5% system,  1.6% interrupt, 77.6% idle
Mem: 95M Active, 2357M Inact, 58M Laundry, 712M Wired, 391M Buf, 774M Free
Swap: 8192M Total, 4500K Used, 8187M Free

  PID USERNAME    PRI NICE   SIZE    RES STATE    C   TIME     CPU COMMAND
   11 root        155 ki31     0B    32K CPU0     0 880:05  84.73% [idle{idle: cpu0}]
   11 root        155 ki31     0B    32K RUN      1 877:28  78.89% [idle{idle: cpu1}]
85899 root         39    0    54M    26M select   0  11:51  26.94% /usr/local/bin/python3 /usr/local/opnsense/scripts/netflow/flowd_aggregate.py (python3.9)
    0 root        -76    -     0B   560K -        0   7:36   3.34% [kernel{wg_tqg_0}]
   12 root        -60    -     0B   480K WAIT     0   6:27   0.68% [intr{swi4: clock (0)}]
   12 root        -92    -     0B   480K WAIT     1   5:33   1.85% [intr{irq30: virtio_pci4}]
    0 root        -76    -     0B   560K -        1   4:09   1.79% [kernel{wg_tqg_1}]
30271 root         20    0    79M    44M nanslp   1   2:31   0.28% /usr/local/bin/php /usr/local/opnsense/scripts/routes/gateway_watcher.php interface routes alarm
    4 root        -16    -     0B    32K -        0   0:50   0.53% [cam{doneq0}]
    0 root        -92    -     0B   560K -        0   0:37   0.05% [kernel{dummynet}]
   17 root         16    -     0B    16K syncer   0   0:33   0.00% [syncer]
    5 root        -16    -     0B    16K pftm     1   0:24   0.08% [pf purge]
    6 root        -16    -     0B    16K -        1   0:13   0.05% [rand_harvestq]
    7 root        -16    -     0B    48K psleep   0   0:11   0.02% [pagedaemon{dom0}]
74591 unbound      20    0  1421M   943M kqread   0   0:11   0.01% /usr/local/sbin/unbound -c /var/unbound/unbound.conf{unbound}
65902 root         20    0    23M    11M select   1   0:10   0.01% /usr/local/bin/python3 /usr/local/opnsense/scripts/syslog/lockout_handler (python3.9)
65605 root         20    0    23M    11M select   0   0:09   0.04% /usr/local/bin/python3 /usr/local/sbin/configctl -e -t 0.5 system event config_changed (python3.9)
   12 root        -88    -     0B   480K WAIT     1   0:07   0.19% [intr{irq28: virtio_pci1}]
39250 root         20    0    17M  2104K nanslp   1   0:04   0.01% /usr/local/bin/dpinger -f -S -r 0 -i WG_PIA_GW -B 10.6.207.112 -p /var/run/dpinger_WG_PIA_GW.pid -u /var/run/dpinger_WG_PIA_GW.sock -s 1s -l 4s -t 60s -d 1 10.6.128.1{dpinger}
55727 root         20    0    13M  2104K bpf      1   0:04   0.02% /usr/local/sbin/filterlog -i pflog0 -p /var/run/filterlog.pid
85129 root         20    0    25M    15M select   0   0:04   0.02% /usr/local/bin/python3 /usr/local/opnsense/scripts/dhcp/unbound_watcher.py --domain photis.net (python3.9)
 6752 root         20    0    39M    14M kqread   1   0:04   0.01% /usr/local/sbin/syslog-ng -f /usr/local/etc/syslog-ng.conf -p /var/run/syslog-ng.pid{syslog-ng}
85402 root         20    0    22M    11M kqread   1   0:03   0.00% /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
    9 root         20    -     0B    64K sdflus   0   0:03   0.06% [bufdaemon{/ worker}]
75708 root         23    0    13M  2164K wait     1   0:03   0.01% /bin/sh /var/db/rrd/updaterrd.sh
39250 root         20    0    17M  2104K accept   0   0:03   0.00% /usr/local/bin/dpinger -f -S -r 0 -i WG_PIA_GW -B 10.6.207.112 -p /var/run/dpinger_WG_PIA_GW.pid -u /var/run/dpinger_WG_PIA_GW.sock -s 1s -l 4s -t 60s -d 1 10.6.128.1{dpinger}
28286 dhcpd        20    0    25M    12M select   1   0:02   0.01% /usr/local/sbin/dhcpd -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid vtnet0_vlan100 vtnet0_vlan200
39250 root         20    0    17M  2104K sbwait   0   0:02   0.00% /usr/local/bin/dpinger -f -S -r 0 -i WG_PIA_GW -B 10.6.207.112 -p /var/run/dpinger_WG_PIA_GW.pid -u /var/run/dpinger_WG_PIA_GW.sock -s 1s -l 4s -t 60s -d 1 10.6.128.1{dpinger}
   12 root        -72    -     0B   480K WAIT     0   0:02   0.00% [intr{swi1: pfsync}]
86877 _flowd       20    0    12M  1812K select   1   0:01   0.00% flowd: net (flowd)
97592 root         20    0    13M  2208K nanslp   1   0:01   0.01% /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP -B 71.184.134.32 -p /var/run/dpinger_WAN_DHCP.pid -u /var/run/dpinger_WAN_DHCP.sock -s 1s -l 4s -t 60s -d 1 71.184.134.1{dpinger}
69260 root         20    0    23M  8288K select   1   0:01   0.01% /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf{ntpd}
    9 root         21    -     0B    64K psleep   1   0:01   0.00% [bufdaemon{bufdaemon}]
97592 root         20    0    13M  2208K accept   0   0:01   0.00% /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP -B 71.184.134.32 -p /var/run/dpinger_WAN_DHCP.pid -u /var/run/dpinger_WAN_DHCP.sock -s 1s -l 4s -t 60s -d 1 71.184.134.1{dpinger}
    9 root         20    -     0B    64K -        1   0:01   0.00% [bufdaemon{bufspacedaemon-0}]
    9 root         20    -     0B    64K -        1   0:01   0.01% [bufdaemon{bufspacedaemon-1}]
   16 root        -16    -     0B    16K vlruwt   0   0:01   0.00% [vnlru]
    7 root        -16    -     0B    48K umarcl   0   0:01   0.00% [pagedaemon{uma}]
   12 root        -72    -     0B   480K WAIT     1   0:01   0.00% [intr{swi1: netisr 0}]
84024 nobody       20    0    12M  1556K sbwait   1   0:00   0.00% /usr/local/bin/samplicate -s 127.0.0.1 -p 2055 127.0.0.1/2056
97592 root         20    0    13M  2208K sbwait   0   0:00   0.00% /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP -B 71.184.134.32 -p /var/run/dpinger_WAN_DHCP.pid -u /var/run/dpinger_WAN_DHCP.sock -s 1s -l 4s -t 60s -d 1 71.184.134.1{dpinger}
80186 root        -16    -     0B    32K sleep    1   0:00   0.00% [ng_queue{ng_queue0}]
    0 root        -92    -     0B   560K -        0   0:00   0.00% [kernel{vtnet0 txq 0}]
    0 root        -76    -     0B   560K -        1   0:00   0.00% [kernel{softirq_1}]
48406 root         20    0    19M  9664K select   1   0:00   0.01% sshd: root@pts/0 (sshd)
71735 root         20    0    14M  3480K CPU1     1   0:00   0.05% top -aSCHIP
 6752 root         20    0    39M    14M kqread   0   0:00   0.06% /usr/local/sbin/syslog-ng -f /usr/local/etc/syslog-ng.conf -p /var/run/syslog-ng.pid{syslog-ng}
78271 root         23    0    12M  1700K nanslp   0   0:00   0.04% sleep 1

vmstat -i bad system

Code: [Select]

root@crawford:~ # vmstat -i
interrupt                          total       rate
irq1: atkbd0                           2          0
irq4: uart0                        40926         19
irq20: virtio_pci0                  2070          1
cpu0:timer                        351580        164
cpu1:timer                        274393        128
irq25: igb0:rxq0                   25481         12
irq26: igb0:rxq1                   22513         10
irq27: igb0:aq                         3          0
irq31: virtio_pci3                184943         86
irq32: ahci0                       43443         20
irq34: virtio_pci1                     1          0
irq36: virtio_pci2                     1          0
Total                             945356        440

vmstat -i good system
             

Code: [Select]

root@crawford:~ # vmstat -i
interrupt                          total       rate
irq1: atkbd0                           2          0
irq4: uart0                         2833          0
irq20: virtio_pci0                 26438          0
cpu0:timer                       5711126        103
cpu1:timer                       1021849         18
irq28: virtio_pci1                384911          7
irq30: virtio_pci4               6396264        115
irq31: virtio_pci4                   348          0
irq32: ahci0                      632325         11
irq34: virtio_pci2                    61          0
irq36: virtio_pci3                     1          0
Total                           14176158        256


8

23.7 Legacy Series / Re: Remove Parent Interface

« on: January 31, 2024, 10:31:12 pm »

Franco, thanks for the reply. Since I have a single VLAN adapter (WAN, LAN. GUEST) and do WAN MAC spoofing. Do I still need a Parent for this setup?

9

23.7 Legacy Series / Remove Parent Interface

« on: January 31, 2024, 09:57:29 pm »

IIRC back in 22.x due to a bug we had to create a Parent interface for vlan WAN connections or turn on Promiscuous mode. I have read this was fixed and no longer necessary. I tried removing the the Parent on one a system and when I do the WAN interface no longer works. It receives a DHCP address from the WAN but I can't ping anything. I tried deleting the Parent then run the interface wizard to redefine the interface to no avail.

What are the proper steps to removed the Parent to get things working? 

10

23.7 Legacy Series / Re: Assistance Needed: Routing Issue with OPNsense Firewall and Cisco Layer 3 Switch

« on: December 06, 2023, 07:48:09 pm »

To be clear the Cisco port is a trunk and not an access vlan?

11

23.7 Legacy Series / Re: Wireguard no more work

« on: December 01, 2023, 12:13:55 pm »

all other clients can connect over fqdn without any problem.
like "myddns.com:10240 or other port forwarded.

Can you snip out from the client logs the connection failure. It would be interesting to see what it shows. If possible you could also do a Wireshark/tcpdump from the client to see the handshake.

12

23.7 Legacy Series / Re: Wireguard no more work

« on: November 30, 2023, 08:28:07 pm »

are the clients using FQDNs or IP addresses to connect? Are they going to the correct Opnsense wan address?

13

23.7 Legacy Series / Re: Wireguard no more work

« on: November 30, 2023, 12:17:01 pm »

You are probably having the same issues as other users >

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

Reapply your NAT settings & FW Rules

Regards,
S.

Can you be more specific about your issue? Is this an issue with endpoints connecting to your Opnsense Wireguard instance? Or is the issue endpoints behind Opnsense not being able to use a Wireguard tunnel to a VPN provider?

14

23.7 Legacy Series / Re: [solved] PIA Wireguard Tunnel

« on: November 28, 2023, 12:17:40 pm »

After verifying the new script worked on my test system I installed the new script on my production system before upgrading. This time the upgrade went perfectly. I suggest anyone using the FingerlessGlov3s script for PIA, save yourself some time and pull it down before you go from 23.7.7x to 23.7.8/9..

15

23.7 Legacy Series / Re: [solved] PIA Wireguard Tunnel

« on: November 28, 2023, 01:10:55 am »

noted.