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 - k0ns0l3

#136
19.7 Legacy Series / Re: High memory usage
September 28, 2019, 09:35:16 AM
Try with a new installation,

greeting k0ns0l3

#137
That's not different with me either (apu2,bios v4.10.0.1) :

sysctl dev.cpu | grep cx
dev.cpu.3.cx_method: C1/hlt
dev.cpu.3.cx_usage_counters: 26070037
dev.cpu.3.cx_usage: 100.00% last 37124us
dev.cpu.3.cx_lowest: C2
dev.cpu.3.cx_supported: C1/1/0
dev.cpu.2.cx_method: C1/hlt
dev.cpu.2.cx_usage_counters: 26186025
dev.cpu.2.cx_usage: 100.00% last 21595us
dev.cpu.2.cx_lowest: C2
dev.cpu.2.cx_supported: C1/1/0
dev.cpu.1.cx_method: C1/hlt
dev.cpu.1.cx_usage_counters: 26131339
dev.cpu.1.cx_usage: 100.00% last 52575us
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_supported: C1/1/0
dev.cpu.0.cx_method: C1/hlt C2/io
dev.cpu.0.cx_usage_counters: 1920478 25752212
dev.cpu.0.cx_usage: 6.93% 93.06% last 1677us
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_supported: C1/1/0 C2/2/400


sysctl -a |grep -i cpu
kern.smp.cpus: 4
kern.smp.maxcpus: 256
kern.ccpu: 0
  <cpu count="4" mask="f,0,0,0">0, 1, 2, 3</cpu>
    <cpu count="4" mask="f,0,0,0">0, 1, 2, 3</cpu>
      <cpu count="1" mask="1,0,0,0">0</cpu>
      <cpu count="1" mask="2,0,0,0">1</cpu>
      <cpu count="1" mask="4,0,0,0">2</cpu>
      <cpu count="1" mask="8,0,0,0">3</cpu>
kern.sched.cpusetsize: 32
kern.pin_pcpu_swi: 0
kern.racct.pcpu_threshold: 1
cpu HAMMER
device cpufreq
kern.vt.splash_cpu_duration: 10
kern.vt.splash_cpu_style: 2
kern.vt.splash_ncpu: 0
kern.vt.splash_cpu: 0
vfs.ncpurgeminvnodes: 512
net.inet.tcp.per_cpu_timers: 0
debug.cpufreq.verbose: 0
debug.cpufreq.lowest: 0
debug.acpi.cpu_unordered: 0
kdb.enter.default=textdump set; capture on; run lockinfo; show pcpu; bt; ps; alltrace; capture off; call doadump; reset
hw.ncpu: 4
hw.acpi.cpu.cx_lowest: C2
dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors
dev.cpufreq.0.%parent: cpu0
dev.cpufreq.0.%pnpinfo:
dev.cpufreq.0.%location:
dev.cpufreq.0.%driver: cpufreq
dev.cpufreq.0.%desc:
dev.cpufreq.%parent:
dev.hwpstate.0.%parent: cpu0
dev.acpi_perf.3.%parent: cpu3
dev.acpi_perf.2.%parent: cpu2
dev.acpi_perf.1.%parent: cpu1
dev.acpi_perf.0.%parent: cpu0
dev.cpu.3.temperature: 50.6C
dev.cpu.3.cx_method: C1/hlt
dev.cpu.3.cx_usage_counters: 26079894
dev.cpu.3.cx_usage: 100.00% last 75us
dev.cpu.3.cx_lowest: C2
dev.cpu.3.cx_supported: C1/1/0
dev.cpu.3.%parent: acpi0
dev.cpu.3.%pnpinfo: _HID=none _UID=0
dev.cpu.3.%location: handle=\_PR_.P003
dev.cpu.3.%driver: cpu
dev.cpu.3.%desc: ACPI CPU
dev.cpu.2.temperature: 50.6C
dev.cpu.2.cx_method: C1/hlt
dev.cpu.2.cx_usage_counters: 26194688
dev.cpu.2.cx_usage: 100.00% last 38us
dev.cpu.2.cx_lowest: C2
dev.cpu.2.cx_supported: C1/1/0
dev.cpu.2.%parent: acpi0
dev.cpu.2.%pnpinfo: _HID=none _UID=0
dev.cpu.2.%location: handle=\_PR_.P002
dev.cpu.2.%driver: cpu
dev.cpu.2.%desc: ACPI CPU
dev.cpu.1.temperature: 50.6C
dev.cpu.1.cx_method: C1/hlt
dev.cpu.1.cx_usage_counters: 26140208
dev.cpu.1.cx_usage: 100.00% last 33us
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_supported: C1/1/0
dev.cpu.1.%parent: acpi0
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%location: handle=\_PR_.P001
dev.cpu.1.%driver: cpu
dev.cpu.1.%desc: ACPI CPU
dev.cpu.0.temperature: 50.6C
dev.cpu.0.cx_method: C1/hlt C2/io
dev.cpu.0.cx_usage_counters: 1922372 25761339
dev.cpu.0.cx_usage: 6.94% 93.05% last 31us
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_supported: C1/1/0 C2/2/400
dev.cpu.0.freq_levels: 1000/980 800/807 600/609
dev.cpu.0.freq: 1000
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%location: handle=\_PR_.P000
dev.cpu.0.%driver: cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.%parent:
security.jail.param.cpuset.id: 0




greeting k0ns0l3
#138
try this command :

sysctl dev.cpu | grep cx
sysctl -a |grep -i cpu


greeting k0ns0l3
#139
German - Deutsch / Re: vulnerable ...
August 27, 2019, 05:28:42 PM
Quote from: fabian on August 27, 2019, 03:37:12 PM
nghttp klingt nach nginx oder haproxy, die eine Abhängigkeit haben. Der Beschreibung nach kann man dir den Webserver / Load Balancer abschießen aber kommt zumindest nicht ins Netz.

Das mit ClamAV ist kritischer, da ZIP-Bomben die ganze Appliance lahm legen können.

Das sind beides externe Ports - d. h. die werden sicher beim nächsten Update gefixt werden.

Danke für die Unterstützung ;)
#140
German - Deutsch / vulnerable ...
August 27, 2019, 01:48:31 PM
Hallo  8),
wenn ich das Security Audit durchführe kommen folgende Fehler:

Audit erledigt.

***GOT REQUEST TO AUDIT SECURITY***
Fetching vuln.xml.bz2: .......... done
clamav-0.101.2,1 is vulnerable:
clamav -- multiple vulnerabilities
CVE: CVE-2019-12900
CVE: CVE-2019-12625
WWW: https://vuxml.freebsd.org/freebsd/dbd1f627-c43b-11e9-a923-9c5c8e75236a.html

libnghttp2-1.39.1_1 is vulnerable:
nghttp2 -- multiple vulnerabilities
CVE: CVE-2019-9513
CVE: CVE-2019-9511
WWW: https://vuxml.freebsd.org/freebsd/121fec01-c042-11e9-a73f-b36f5969f162.html

2 problem(s) in the installed packages found.
***DONE***

Danke für Eure Erläuterung!

MfG k0ns0l3
#141
direct upgrade possible 19.1 => 19.7 ?

Kind regards k0ns0l3  8)
#142
THX  ;D
#143
19.7 release date   ::)

Kind regards k0ns0l3
#144
19.1 Legacy Series / Re: IGMPv3 (SSM)
June 20, 2019, 02:43:08 PM
Quote from: DoomSalamander on June 17, 2019, 12:26:06 AM
I also tried skywalker007's setup and it doesn't work. While I do get an image it will stutter after a few seconds. I have the 401 receiver connected directly to opnsense. The same result happends if I connect the 401 with a igmpv3 ready zyxel switch. The switch works fine if I use my draytek as a normal router and use it's built in igmp.

My setup is draytek 165 -> opnsense pppoe login with vlan7 -> 401 receiver

the same thing to me  :-[
#145
German - Deutsch / Re: [Gelöst]vnstat
June 13, 2019, 06:15:37 PM
Neustart von von opnsense :


/usr/local/etc/rc.d/vnstat restart

vnstat not running? (check /var/run/vnstat/vnstat.pid).
vnstat: Created the database for the additional interface igb0
vnstat: Created the database for the additional interface igb2
vnstat: Created the database for the additional interface igb1

Starting vnstat.
Zero database found, exiting.
/usr/local/etc/rc.d/vnstat: WARNING: failed to start vnstat

MfG k0ns0l3
#146
German - Deutsch / Re: [Gelöst]vnstat
June 12, 2019, 09:10:27 PM
ganz normale neu start ohne fehler,komisch  :-\ aber neue start von opnsense startet vnstat nicht mehr  >:(
#147
German - Deutsch / Re: [Gelöst]vnstat
June 12, 2019, 01:36:46 PM
/usr/local/etc/rc.d/vnstat restart

Stopping vnstat.
Starting vnstat.


nichts außergewöhnliches aufgefallen  8),

MfG k0ns0l3
#148
19.1 Legacy Series / Re: IGMPv3 (SSM)
June 12, 2019, 06:00:47 AM
@gliddie: attitude of apu2 and opnsense or home network ,

Regards k0ns0l3  8)

#149
German - Deutsch / Re: [Gelöst]vnstat
June 12, 2019, 05:54:42 AM
Genau  :(
#150
German - Deutsch / Re: [Gelöst]vnstat
June 11, 2019, 02:27:45 PM
immer nach dem neustart :

Jun 11 14:15:24 root: /usr/local/etc/rc.d/vnstat: WARNING: failed to start vnstat


Durch das Zurücksetzen von vnstat läuft wieder aber dann sind die flüchtigen vnstat daten weg  :-\

vnstatd[84203]: Monitoring: igb2 (1000 Mbit) igb0 (1000 Mbit) igb1 (1000 Mbit)

MfG k0ns0l3