Try with a new installation,
greeting k0ns0l3
greeting k0ns0l3
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 Menusysctl 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
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.
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
Jun 11 14:15:24 root: /usr/local/etc/rc.d/vnstat: WARNING: failed to start vnstat
vnstatd[84203]: Monitoring: igb2 (1000 Mbit) igb0 (1000 Mbit) igb1 (1000 Mbit)