Messages

Just a quick question sorry for the double post. Are there plans to move exclusively to hardened BSD as our core or have side by side releases on the same version number and opnsense build? I am very interested in getting on board with this.

That was it! Sorry I guess it didn't click for me on the list. I just thought it was some BSD specific watchdog I guess. Still haven't figured out how I managed to check that box. Thanks a ton! CPU is running much cooler! (these embedded heatsinks are not fantastic. and the thermal paste is terrible too even after re-apply)

yeah currently no one is home im pulling no bandwidth. before this would generally indicate a very low CPU usage .4 .3 etc on the avg load graph. but im talking consistently at 25% the read out via putty is

Code Select Expand



root@Chronos:~ # top -S -P                                                      last pid: 97901;  load averages:  1.02,  1.03,  1.00    up 0+16:46:12  09:24:51
65 processes:  4 running, 60 sleeping, 1 waiting
CPU 0:  2.5% user,  0.0% nice, 23.3% system,  0.6% interrupt, 73.6% idle
CPU 1:  0.0% user,  0.0% nice, 33.1% system,  0.0% interrupt, 66.9% idle
CPU 2:  0.0% user,  0.0% nice, 23.9% system,  0.0% interrupt, 76.1% idle
CPU 3:  0.6% user,  0.0% nice, 27.6% system,  0.6% interrupt, 71.2% idle
Mem: 6228K Active, 128M Inact, 293M Wired, 5700K Cache, 656M Buf, 7393M Free
Swap:

  PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
   11 root          4 155 ki31     0K    64K CPU3    3  46.1H 308.74% idle
   19 root          1 -16 ki-1     0K    16K CPU1    1  16.7H  99.56% idlepoll
33926 root          1  72    0   126M 30936K CPU0    0   0:07   0.39% php-cgi
   12 root         20 -72    -     0K   320K WAIT    2  17:41   0.00% intr
   15 root          1 -16    -     0K    16K -       0   5:04   0.00% rand_harv
7442 root          1  21    0   126M 28396K accept  1   0:07   0.00% php-cgi
    5 root          1 -16    -     0K    16K pftm    0   0:05   0.00% pf purge
2691 root          1  20    0 56708K  7216K kqread  3   0:05   0.00% lighttpd
64916 nobody        1  20    0 19604K  4996K select  3   0:05   0.00% dnsmasq
   16 root         12 -68    -     0K   192K -       0   0:03   0.00% usb
36994 root          1  20    0 16660K  2184K bpf     2   0:02   0.00% filterlog
46710 root          1  20    0 14392K  1952K select  0   0:02   0.00% powerd
4111 root          1  52    0 16988K  2488K wait    1   0:02   0.00% sh



Do you see anything? If the system is constantly under load thats w/e I can understand if their is overhead or something. What is blowing my mind is that the 25% atleast to me isnt represented in the CPU usage stats. the cores themselves show idle states on ly in the 60's and mid 70's However the actual task list doesnt show me what is loading the system. Maybe im missing something simple since im not  used to tops print outs but thats atleast what it appears like to me?

Updated today and now running

OPNsense 15.7_1018-amd64   
FreeBSD 10.2-RELEASE-p1   
LibreSSL 2.2.3

however after the initial and subsequent (2) reboots of the router the CPU usage is sitting at 25% the router itself is running an i3-4130 but it is running warm now with the constant usage. Unfortunetely I am unable to find the process doing it?

Code Select Expand

last pid: 46927;  load averages:  1.21,  1.16,  1.10  up 0+04:47:08    21:25:47
127 processes: 6 running, 101 sleeping, 20 waiting

Mem: 134M Active, 248M Inact, 232M Wired, 308K Cache, 125M Buf, 7211M Free
Swap:


  PID USERNAME   PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
   19 root       -16 ki-1     0K    16K CPU2    2 286:23 100.00% [idlepoll]
   11 root       155 ki31     0K    64K CPU1    1 174:53  77.98% [idle{idle: cp
   11 root       155 ki31     0K    64K CPU3    3 172:00  73.88% [idle{idle: cp
   11 root       155 ki31     0K    64K RUN     2 170:11  73.88% [idle{idle: cp
   11 root       155 ki31     0K    64K RUN     0 163:23  72.85% [idle{idle: cp
40278 root        20    0   389M   260M uwait   0  20:56   1.66% /usr/local/bin
40278 root        20    0   389M   260M uwait   2  46:23   1.46% /usr/local/bin
19426 root        52    0   130M 30512K piperd  0   0:02   0.98% /usr/local/bin
2691 root        20    0 56708K  7164K kqread  3   0:01   0.68% /usr/local/sbi
40278 root        20    0   389M   260M uwait   1   1:09   0.10% /usr/local/bin
40278 root        20    0   389M   260M uwait   0  39:37   0.00% /usr/local/bin
40278 root        20    0   389M   260M uwait   2  19:20   0.00% /usr/local/bin
40278 root        20    0   389M   260M uwait   3  18:24   0.00% /usr/local/bin
40278 root        20    0   389M   260M uwait   2  12:54   0.00% /usr/local/bin
40278 root        20    0   389M   260M bpf     2   7:18   0.00% /usr/local/bin
40278 root        20    0   389M   260M bpf     2   7:16   0.00% /usr/local/bin
   12 root       -72    -     0K   320K WAIT    2   4:59   0.00% [intr{swi1: ne
   15 root       -16    -     0K    16K -       3   1:37   0.00% [rand_harvestq



The cores show the usage but the processes dont represent the missing %?

should I manually go through the directories to delete them or is this an automated task of the installer?

Is upgrading to 10.2 after devel builds still useful or have you exhausted 10.2 testing? I noticed today going to 10.2 that it now read .obsolete. in this case should I be sticking with 10.1?

What do you mean by "crypto" status?

I tracked down the CSRF issue last night (it's only on opnsense-devel fortunately), can be fixed via:

# cd /usr/local/www/csrf
# fetch https://raw.githubusercontent.com/opnsense/core/master/src/www/csrf/csrf-magic.js

This is the likely cause for the diagnostics pages misbehaving.

Also not sure what you mean by SMTP... do you mean the notifications?

I'm going to push proper amendments for 15.7.12 (both release and devel) on Monday or Tuesday at the latest.

Hmm it must have been a bug then. Immediately after I updated I was on the new opnsense build but BSD 10.1 before I upgraded back to 10.2 the opnsense main page had or seemed to have had a field for the cryptography used mine specifically said that it was AES-NI but possibly this was not meant to show up?

yes as for SMTP I ment the email notification system. I just applied the CSRF fix. Did you just disable the cache or was it some kind of incompatibility?

What is your build? What does your PS4 report NAT type 2 or? How did you configure it? did you manually configure UPnP or did you just enable it? My PS3 and 360s work with just UPnP enabled I did not manually configure anything.

Thank you! Easy readability is beneficial to everyone!

aw they took away my crypto status on the main page when I updated and then upgraded back to 10.2 :(

OPNsense 15.7_947-amd64   
FreeBSD 10.2-RELEASE-p1   
LibreSSL 2.2.3

I also apprently cant get a system status (pftop) & (Diagnostics: System Activity), Limiter info and anything gathering data in this method gives me the following.

CSRF check failed. Your form session may have expired, or you may not have
        cookies enabled.

when I hit test again my page goes blank and dumps output like a sql debug

Code Select Expand

last pid: 9979; load averages: 0.04, 0.16, 0.14 up 0+00:08:27 19:57:18 125 processes: 5 running, 100 sleeping, 20 waiting Mem: 254M Active, 82M Inact, 217M Wired, 76M Buf, 7272M Free Swap: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 155 ki31 0K 64K CPU3 3 8:21 100.00% [idle{idle: cpu3}] 11 root 155 ki31 0K 64K CPU2 2 8:20 100.00% [idle{idle: cpu2}] 11 root 155 ki31 0K 64K CPU1 1 8:17 100.00% [idle{idle: cpu1}] 11 root 155 ki31 0K 64K RUN 0 8:13 98.29% [idle{idle: cpu0}] 69184 root 22 0 130M 34716K piperd 1 0:08 1.27% /usr/local/bin/php-cgi 41268 root 20 0 289M 203M uwait 0 0:04 0.59% /usr/local/bin/suricata -D -i re0 -i re1 0 root -16 0 0K 160K swapin 3 0:28 0.00% [kernel{swapper}] 41268 root 20 0 289M 203M nanslp 3 0:02 0.00% /usr/local/bin/suricata -D -i re0 -i re1 63601 root 21 0 126M 29040K accept 3 0:01 0.00% /usr/local/bin/php-cgi 12 root -92 - 0K 320K WAIT 1 0:01 0.00% [intr{irq267: re0}] 12 root -92 - 0K 320K WAIT 1 0:01 0.00% [intr{irq268: re1}] 55284 root 20 0 60804K 7072K kqread 3 0:01 0.00% /usr/local/sbin/lighttpd -f /var/etc/lig 41268 root 20 0 289M 203M uwait 0 0:00 0.00% /usr/local/bin/suricata -D -i re0 -i re1 180 root 20 0 115M 30864K accept 0 0:00 0.00% /usr/local/bin/python2.7 /usr/local/opns 41268 root 20 0 289M 203M uwait 2 0:00 0.00% /usr/local/bin/suricata -D -i re0 -i re1 12 root -60 - 0K 320K WAIT 0 0:00 0.00% [intr{swi4: clock}] 41268 root 20 0 289M 203M uwait 1 0:00 0.00% /usr/local/bin/suricata -D -i re0 -i re1 41268 root 20 0 289M 203M uwait 1 0:00 0.00% /usr/local/bin/suricata -D -i re0 -i re1


but it actually is the output I was expecting except well....formatted......and inside the CP.

I also still have an issue with selection on the left hand pane when I scroll down a page on the right.

here is an example

http://recordit.co/f7mGECeRKC

pfinfo doesnt work at all for me.

also if I may ask what exactly is reported and sent via SMTP? I finally got it working but I would like alot communication through this since I prefer email/easier than using a remote logging server for event notification. Can/are we/able to customize/request features or alerts that can be sent via this?

Can't wait to give it a go when my network is less busy! I wanted to mention the help on the various builds. How exactly would you like a report? Is there anything we can do specifically to help opnsense? If I install a beta build and nothing goes wrong and everything is working fine I don't have much to talk about, which is fine but maybe I can be doing something more productive?

Sounds like a great idea!

I actually think it might be a bit difficult since some refer to dynDNS as a service, but adding "service" and "provider" to the outputs seems incredibly tacky.

I see sorry for the confusion I somehow thought it was the dynDNS provider not enough sleep I guess. /cheers

ah ok I misunderstood I thought the card was having issues as well. It does seem like it or there is some kind of North bridge issue. I would keep an eye on the machine over the next several days.