Re: LDPD Crashing
To elaborate, after enabling ldpd with - I have observed the
following in the log output:
Mar 3 00:58:37 mpls-gw ldpd[77048]: nbr_fsm: event SESSION CLOSE
resulted in action CLOSE SESSION and changing state for lsr-id
100.92.64.68 from OPERATIONAL to PRESENT
Mar 3 00:58:37 mpls-gw ldpd[77048]: session_close: closing session
with lsr-id 100.92.64.68
Mar 3 00:58:37 mpls-gw ldpd[9902]: label decision engine exiting
Mar 3 00:58:37 mpls-gw ldpd[54245]: kernel routing table decoupled
Mar 3 00:58:37 mpls-gw ldpd[54245]: waiting for children to terminate
Mar 3 00:58:37 mpls-gw ldpd[54245]: ldp engine terminated; signal 10
Mar 3 00:58:37 mpls-gw ldpd[54245]: terminating
On Sun, Mar 3, 2019 at 12:32 AM Henry Bonath wrote:
>
> Hello, I am still working through some issues with trying to use
> OpenBSD as a Virtual MPLS PE in a multi-tenant hosted IaaS
> environment.
>
> I am running OpenBSD 6.4 in a Hyper-V environment.
>
> I recently started seeing one of my LDP adjacencies flapping, so I
> replace that particular P device with a Cisco ASR 920. So currently,
> my OpenBSD machine is OSPF and LDP Neighbors with the ASR 920, which
> connects to a provider circuit, and then terminates to a Cisco router
> at the customer premise running as a PE with a VRF connecting to the
> CE.
>
> Now, I am getting a crash in LDP happening after about 15 minutes:
> ldp engine terminated; signal 10 shows up in /var/log/messages
>
> here's my ldpd.conf:
> =
> router-id 100.92.127.120
>
> address-family ipv4 {
> interface hvn0
> }
> =
>
> Thanks in advance!
LDPD Crashing
Hello, I am still working through some issues with trying to use
OpenBSD as a Virtual MPLS PE in a multi-tenant hosted IaaS
environment.
I am running OpenBSD 6.4 in a Hyper-V environment.
I recently started seeing one of my LDP adjacencies flapping, so I
replace that particular P device with a Cisco ASR 920. So currently,
my OpenBSD machine is OSPF and LDP Neighbors with the ASR 920, which
connects to a provider circuit, and then terminates to a Cisco router
at the customer premise running as a PE with a VRF connecting to the
CE.
Now, I am getting a crash in LDP happening after about 15 minutes:
ldp engine terminated; signal 10 shows up in /var/log/messages
here's my ldpd.conf:
=
router-id 100.92.127.120
address-family ipv4 {
interface hvn0
}
=
Thanks in advance!
Re: Black screen when starting Xorg with Dell XPS 13 9350
Thanks for the help, Fred. Unfortunately, I'm still getting a black screen. I didn't previously have a ~/.xsession, but I created one with the following contents: export LANG=en_US.UTF-8 export ENV=$HOME/.kshrc xrdb -merge $HOME/.Xresources xsetroot -solid dimgray xidle & LANG= xclock -strftime "%a %e %b %Y %H:%M" & xset b off setxkbmap -option ctrl:nocaps exec cwm I also removed machdep.allowaperture=1 from /etc/sysctl.conf. When I booted with this configuration, I got a black screen and the Xorg.0.log gave: [13.242] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [13.242] linear framebuffer access unavailable [13.312] (--) Using wscons driver on /dev/ttyC4 [13.370] X.Org X Server 1.19.6 Release Date: 2017-12-20 [13.370] X Protocol Version 11, Revision 0 [13.370] Build Operating System: OpenBSD 6.4 amd64 [13.370] Current Operating System: OpenBSD c12h17n2o4p.my.domain 6.4 GENERIC.MP#7 amd64 [13.370] Build Date: 25 October 2018 11:39:05PM [13.370] [13.370] Current version of pixman: 0.34.0 [13.370] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [13.370] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [13.370] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 2 19:00:38 2019 [13.372] (==) Using config directory: "/etc/X11/xorg.conf.d" [13.373] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [13.374] (==) No Layout section. Using the first Screen section. [13.374] (==) No screen section available. Using defaults. [13.374] (**) |-->Screen "Default Screen Section" (0) [13.374] (**) | |-->Monitor "" [13.375] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [13.375] (**) | |-->Device "drm" [13.375] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [13.375] (==) Automatically adding devices [13.375] (==) Automatically enabling devices [13.375] (==) Not automatically adding GPU devices [13.375] (==) Max clients allowed: 256, resource mask: 0x1f [13.382] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [13.382] (==) ModulePath set to "/usr/X11R6/lib/modules" [13.383] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [13.383] (II) Loader magic: 0x35f44c71000 [13.383] (II) Module ABI versions: [13.383] X.Org ANSI C Emulation: 0.4 [13.383] X.Org Video Driver: 23.0 [13.383] X.Org XInput driver : 24.1 [13.383] X.Org Server Extension : 10.0 [13.383] (--) PCI:*(0:0:2:0) 8086:1916:1028:0704 rev 7, Mem @ 0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64 [13.383] (II) LoadModule: "glx" [13.386] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [13.400] (II) Module glx: vendor="X.Org Foundation" [13.400] compiled for 1.19.6, module version = 1.0.0 [13.400] ABI class: X.Org Server Extension, version 10.0 [13.400] (II) LoadModule: "intel" [13.400] (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so [13.405] (II) Module intel: vendor="X.Org Foundation" [13.405] compiled for 1.19.6, module version = 2.99.916 [13.405] Module class: X.Org Video Driver [13.405] ABI class: X.Org Video Driver, version 23.0 [13.405] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [13.406] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [13.406] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [13.406] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 [13.408] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20151010 [13.410] (WW) intel(0): Unknown chipset [13.410] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2 [13.410] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [13.410] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [13.410] (==) intel(0): RGB weight 888 [13.410] (==) intel(0): Default visual is TrueColor [13.411] (**) intel(0): Option "TearFree"
Re: Black screen when starting Xorg with Dell XPS 13 9350
The problem is with the ACPI stack, it's known not to work with this laptop (I have the same one). It worked for one release (6.1 iirc) and then a regression was introduced that stopped it from working. hth Noth On 03/03/2019 01:01, Fred Crowson wrote: do you have an .xsession file in your /home/ directory? machdep.allowaperture=1 should not be needed for xenodm to work... I once had a similar issue where the X server would start with a black screen until I toggled either the keyboard brightness setting or the keyboard shortcut for internal / external monitor. hth Fred On Sat, 2 Mar 2019 at 23:13, Bryan Avery wrote: I have been unable to start X with a new install of OpenBSD on my laptop. I am a beginner with OpenBSD. This is a Skylake laptop with Intel 520 QHD graphics. During boot, the console shows with underscan, then the resolution increases (but is still less than native), then goes black upon starting Xorg. If I disable xenodm, the console is visible and I am able to login on the laptop. The first time I enabled and started xenodm, the screen went black. I was able to connect through SSH and retrieve the Xorg.0.log which told me to add machdep.allowaperture=1 to /etc/sysctl.conf which I did, but the screen went black again after I rebooted. I am not able to understand what went wrong from looking at the dmesg and Xorg.0.log. I have tested this with and without a config in /etc/X11/xorg.conf.d and get the same result. I am currently using /etc/X11/xorg.conf.d/intel.conf with contents: Section "Device" Identifier "drm" Driver "intel" Option "TearFree" "true" EndSection dmesg: OpenBSD 6.4 (GENERIC.MP) #7: Thu Feb 28 18:56:25 CET 2019 r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8433565696 (8042MB) avail mem = 8168701952 (7790MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe (94 entries) bios0: vendor Dell Inc. version "1.9.0" date 08/31/2018 bios0: Dell Inc. XPS 13 9350 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT DBGP DBG2 SSDT BOOT SSDT UEFI SSDT MSDM SSDT SLIC TCPA DMAR BGRT ASF! acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2295.40 MHz, 06-4e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.66 MHz, 06-4e-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.65 MHz, 06-4e-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.65 MHz, 06-4e-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE
Re: Black screen when starting Xorg with Dell XPS 13 9350
do you have an .xsession file in your /home/ directory? machdep.allowaperture=1 should not be needed for xenodm to work... I once had a similar issue where the X server would start with a black screen until I toggled either the keyboard brightness setting or the keyboard shortcut for internal / external monitor. hth Fred On Sat, 2 Mar 2019 at 23:13, Bryan Avery wrote: > > I have been unable to start X with a new install of OpenBSD on my > laptop. I am a beginner with OpenBSD. This is a Skylake laptop with > Intel 520 QHD graphics. During boot, the console shows with underscan, > then the resolution increases (but is still less than native), then > goes black upon starting Xorg. If I disable xenodm, the console is > visible and I am able to login on the laptop. The first time I enabled > and started xenodm, the screen went black. I was able to connect > through SSH and retrieve the Xorg.0.log which told me to add > machdep.allowaperture=1 to /etc/sysctl.conf which I did, but the > screen went black again after I rebooted. I am not able to understand > what went wrong from looking at the dmesg and Xorg.0.log. I have > tested this with and without a config in /etc/X11/xorg.conf.d and get > the same result. I am currently using /etc/X11/xorg.conf.d/intel.conf > with contents: > > Section "Device" > Identifier "drm" > Driver "intel" > Option "TearFree" "true" > EndSection > > dmesg: > > OpenBSD 6.4 (GENERIC.MP) #7: Thu Feb 28 18:56:25 CET 2019 > > r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8433565696 (8042MB) > avail mem = 8168701952 (7790MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe (94 entries) > bios0: vendor Dell Inc. version "1.9.0" date 08/31/2018 > bios0: Dell Inc. XPS 13 9350 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT > SSDT DBGP DBG2 SSDT BOOT SSDT UEFI SSDT MSDM SSDT SLIC TCPA DMAR BGRT > ASF! > acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) > PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) > PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2295.40 MHz, 06-4e-03 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 23MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.66 MHz, 06-4e-03 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.65 MHz, 06-4e-03 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.65 MHz, 06-4e-03 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,A
Black screen when starting Xorg with Dell XPS 13 9350
I have been unable to start X with a new install of OpenBSD on my laptop. I am a beginner with OpenBSD. This is a Skylake laptop with Intel 520 QHD graphics. During boot, the console shows with underscan, then the resolution increases (but is still less than native), then goes black upon starting Xorg. If I disable xenodm, the console is visible and I am able to login on the laptop. The first time I enabled and started xenodm, the screen went black. I was able to connect through SSH and retrieve the Xorg.0.log which told me to add machdep.allowaperture=1 to /etc/sysctl.conf which I did, but the screen went black again after I rebooted. I am not able to understand what went wrong from looking at the dmesg and Xorg.0.log. I have tested this with and without a config in /etc/X11/xorg.conf.d and get the same result. I am currently using /etc/X11/xorg.conf.d/intel.conf with contents: Section "Device" Identifier "drm" Driver "intel" Option "TearFree" "true" EndSection dmesg: OpenBSD 6.4 (GENERIC.MP) #7: Thu Feb 28 18:56:25 CET 2019 r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8433565696 (8042MB) avail mem = 8168701952 (7790MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe (94 entries) bios0: vendor Dell Inc. version "1.9.0" date 08/31/2018 bios0: Dell Inc. XPS 13 9350 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT DBGP DBG2 SSDT BOOT SSDT UEFI SSDT MSDM SSDT SLIC TCPA DMAR BGRT ASF! acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2295.40 MHz, 06-4e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.66 MHz, 06-4e-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.65 MHz, 06-4e-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2294.65 MHz, 06-4e-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 6
Current thinking on OpenBSD "router" "firewall" role separation ?
Hi, I would be interested to find out the community's view on whether separating "router" and "firewall" roles is still a good thing or whether developments in recent iterations of OpenBSD would permit aggregation whilst maintaining integrity and security ? If you forgive my attempt at ASCII art (which I hope survives internet mangling), this would be representative of what I would do for a "traditional" setup: (BGP) (BGP) | | ["router"] ["router"] | \ / | | \ / | | / \ | | / \ | ["firewall"] ["firewall"] • The routers talk full BGP externally and default-route BGP to the firewalls. • The firewalls talk offer VRRP internally and also BGP default-route internally to those that can talk BGP • The firewalls also offer other internal services such as NTP etc.• The firewalls also act as a VPN endpoint externally using a combination of iked, ifstated and other stuff to make it work • The firewalls are very much perimeter firewalls, they don't do detailed content handling such as mail etc., that is done elsewhere Various factors have led to a hardware refresh for this kit, and as part of that I'm curious as to whether I can consolidate without (a) loosing the benefits of the split model and (b) introducing too much un-necessary additional complexity. Thanks ! Rachel
Re: spamd and low priority MX
Hi Thuban, On Sat, 2 Mar 2019 09:20:42 +0100 Thuban wrote: > On the server with the highest priority (lower MX), I must set "-M > nn.nn.nn.nn" where nn.nn.nn.nn is the IP of a lower priority MX? Where nn.nn.nn.nn is the public IP of a fake backup MX server, which *DOES* have an SMTP daemon running, which 450/451 soft defers _ALL_ mail. > If there is more than 1 backup MX (lower priority), does the -M > flag can be called more than once? Just once, e.g: $ dig Britvault.Co.UK MX +short 12 smtp.Britvault.Co.UK. <--- real primary MX 144 mx-backup.smtp.Britvault.Co.UK. <--- real backup MX 666 highlisting.smtp.Britvault.Co.UK. <--- fake backup MX The fake's public IP address needs to be another IP address, on a real MX machine (an alias or another network port). This sort of fake DNS MX record is called highlisting. (Works well with greylisting.) Having a fake primary DNS MX record is called nolisting. (Practically has to be on the real primary MX server. Doesn't work great with greylisting.) Greylisting is in between no & high listing. But it doesn't need more DNS records, more public IP addresses, a deferring daemon, nor TCP rejection on port 25. Yet it does introduce delays. There is also unlisting... All these tricks reduce spam, and all have operational problems. Nolisting + highlisting is a viable alternative to greylisting: Primary MX only:57% (DNSBL:98%) MX backup only: 20% (DNSBL:90%) Nolisting + multiple fake highlisters killed 98% of spam for this bloke: http://blog.whitesites.com/Stop-Spam-with-fake-MX-records__633764658986714568_blog.htm Some articles to read:- http://wiki.apache.org/spamassassin/OtherTricks http://wiki.junkemailfilter.com/index.php/Project_tarbaby http://nolisting.org/ https://en.wikipedia.org/wiki/Nolisting http://www.junkemailfilter.com/spam/how_it_works.html Cheers, -- Craig Skinner | http://linkd.in/yGqkv7
spamd and low priority MX
Hello, I ran into the spamd "-M" flag in the manpage, and I'm not sure to understand it correctly. On the server with the highest priority (lower MX), I must set "-M nn.nn.nn.nn" where nn.nn.nn.nn is the IP of a lower priority MX ? If there is more than one backup MX (lower priority), does the -M flag can be called more than once ? Am I wrong ? Regards. thuban
