Topics

Hi,

After reading the following topic about how-to setup a Shaper to get rid of bufferbloat: https://docs.opnsense.org/manual/how-tos/shaper_bufferbloat.html#quantum

Regarding the correct value for "Quantum" its stated:

The proper value of Quantum should be no more or less than is the WAN MTU.

However, while this might sound clear. This is still too ambiguous for me.

I have fiber connection from my ISP using PPPoE, which is 1500 bytes.
However PPPoE has a connection overhead of 8 Bytes, so the WAN interface with VLAN 6 tag has a MTU of 1508.
So I have set 1508 MTU on my WAN interface (Identifier: opt1, device: ppoe0).

But that is not all, I also have a 'WAN RAW' interface configured as well (Identifier: opt6, device: ax0). Which has the overhead of the VLAN of 4 bytes, meaning that MTU setting is 1512.

Meaning "WAN MTU" term is too ambiguous for me. So what value should I use now for quantum; 1500, 1508 or 1512?

I guess 1512 in my case. Right or not? This could be written more clearly.

Thanks in advance!

Kind regards,
Melroy van den Berg

Dmesg kernel crash using OPNsense 24.10.1 Business (fully up to date). I use both IPv4 and IPv6 (dual stack), nothing special about my setup and no additional package installed. And using the official Deciso hardware:

Code Select Expand

<7>cannot forward src fe80:6::99bc:8c8c:d836:c182, dst 2620:2d:4000:1::2a, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::99bc:8c8c:d836:c182, dst 2620:2d:4000:1::2b, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::99bc:8c8c:d836:c182, dst 2620:2d:4000:1::23, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::99bc:8c8c:d836:c182, dst 2620:2d:4002:1::197, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::99bc:8c8c:d836:c182, dst 2620:2d:4002:1::198, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a01:111:f100:9001::1761:9097, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42::485, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42::485, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42::485, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:200::485, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2620:1ec:bdf::67, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2a04:4e42:400::485, nxt 17, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2606:50c0:8001::154, nxt 6, rcvif ax1, outif pppoe0
<7>cannot forward src fe80:6::e486:95ff:fe5b:1003, dst 2606:50c0:8003::154, nxt 6, rcvif ax1, outif pppoe0


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xfffff809e2afe000
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff810baf61
stack pointer         = 0x28:0xfffffe001d772cd0
frame pointer         = 0x28:0xfffffe001d772d00
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (if_io_tqg_0)
rdi: 000000082c140000 rsi: 0000000000000001 rdx: 0000000000000011
rcx: 000000002b95d7ff  r8: 000000002b95e000  r9: fffffe001d773000
rax: fffff801b69be000 rbx: fffffe00d9baa000 rbp: fffffe001d772d00
r10: 0000000000000000 r11: 0000000000000000 r12: 0000000000000010
r13: fffff80004007800 r14: 0000000000000000 r15: 0000000000000000
trap number = 12
panic: page fault
cpuid = 0
time = 1736267408
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe001d7729c0
vpanic() at vpanic+0x131/frame 0xfffffe001d772af0
panic() at panic+0x43/frame 0xfffffe001d772b50
trap_fatal() at trap_fatal+0x40b/frame 0xfffffe001d772bb0
trap_pfault() at trap_pfault+0x46/frame 0xfffffe001d772c00
calltrap() at calltrap+0x8/frame 0xfffffe001d772c00
--- trap 0xc, rip = 0xffffffff810baf61, rsp = 0xfffffe001d772cd0, rbp = 0xfffffe001d772d00 ---
axgbe_isc_rxd_available() at axgbe_isc_rxd_available+0xc1/frame 0xfffffe001d772d00
iflib_rxeof() at iflib_rxeof+0xc5/frame 0xfffffe001d772e00
_task_fn_rx() at _task_fn_rx+0x72/frame 0xfffffe001d772e40
gtaskqueue_run_locked() at gtaskqueue_run_locked+0x14e/frame 0xfffffe001d772ec0
gtaskqueue_thread_loop() at gtaskqueue_thread_loop+0xc2/frame 0xfffffe001d772ef0
fork_exit() at fork_exit+0x7f/frame 0xfffffe001d772f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe001d772f30
--- trap 0xe9939ae2, rip = 0x61d4934a6d94934e, rsp = 0xc6e30806caa30802, rbp = 0x7adc2428769c242c ---
KDB: enter: panic

Reason unknown to me.

[Where is the 24.10 Production Series forum?]

I only see 24.7 Production Series forum (and 24.1).

Where is the 24.10 Production Series forum?

Ik ben mogelijk van plan om DEC3842 aan te schaffen voor in m'n 19" server rack.

Echer, ondanks dat de server rack in de garage staat, wil ik niet al te veel lawaai hebben.
Kan iemand mij vertellen hoeveel decibel deze server maakt in idle? En hoeveel db tijdens normaal/gemiddelde load? Zit er een goeie fan control op?

Helaas kon ik helemaal niks vinden over geluidsdruk op de product omschrijving op de site: https://shop.opnsense.com/product/dec3842-opnsense-rack-security-appliance/ maar ook niet in de brochure: https://shop.opnsense.com/wp-content/uploads/2023/12/DEC3842_52_62.pdf

Alvast bedankt!

Groet,
Melroy van den Berg