Re: bgpctl sho ri nei terse output vs man page discrepancy
On Sun, Sep 22, 2019 at 04:48:18PM -, Stuart Henderson wrote: > On 2019-09-22, Rachel Roch wrote: > > Hi, > > > > Hopefully I'm not missing something silly here but I've read the paragraph > > in the man page and it only lists 15 variables: > > > > "The printed numbers are the sent and received open, > > sent and received notifications, sent and received > > updates, sent and received keepalives, and sent and > > received route refresh messages plus the current and > > maximum prefix count, the number of sent and received > > updates, and withdraws." > > > > But bgpctl sho ri nei outputs 16 numbers, not 15 ? > > Sent and recevied updates, sent and received withdraws. > > Unfortunately the peer's name/address is missing, which makes it a bit > tricky to use with "group", though it's not very convenient to change the > output format now .. Better now than later. You could add the name/ip to the end. -- :wq Claudio
Re: syspatch says 6.5 patch #011 (libexpat) is malformed
On Mon, Sep 23, 2019 at 12:20:40AM -0400, Bryan Steele wrote: > On Sun, Sep 22, 2019 at 12:42:25PM -0700, Jonathan Thornburg wrote: > > I'm trying to use syspatch to update a firewall (a PC Engines Alix) > > running 6.5-stable/i386, but syspatch dies with an error message saying > > that the patch file contains inappropriate filenames: > > > > # uname -a > > OpenBSD sodium.bkis-orchard.net 6.5 GENERIC#3 i386 > > # cat /etc/installurl > > https://cdn.openbsd.org/pub/OpenBSD > > # ls -gFlk /bsd* > > -rwx-- 2 root wheel 13518991 Sep 10 18:23 /bsd* > > -rwx-- 2 root wheel 13518991 Sep 10 18:23 /bsd.booted* > > -rw--- 1 root wheel 8843776 May 12 16:43 /bsd.rd > > # syspatch -l > > 001_rip6cksum > > 002_srtp > > 004_bgpd > > 005_libssl > > 006_tcpsack > > 007_smtpd > > 010_frag6ecn > > # syspatch -c > > 011_expat > > # syspatch > > Get/Verify syspatch65-011_expat.tgz 100% |**| 546 KB00:00 > > > > Installing patch 011_expat > > > > tar: Pattern matching characters used in file names > > tar: Use --wildcards to enable pattern matching, or --no-wildcards to > > suppress this warning > > tar: @usr/share/relink/kernel/GENERIC.MP/.*@@g: Not found in archive > > tar: Exiting with failure status due to previous errors > > # > > That message is not from OpenBSD's tar(1) implementation. There is a very good reason why GNU utilities installed from ports and packages are prefixed with a 'g', so as to not conflict with utilites from the base system. You changed the system-wide tar to GNU tar, so you should expect there to be fallout. > > Is this a known issue with this patch? Is there an alternate way > > (besides updating from source) to track -stable ?
Re: syspatch says 6.5 patch #011 (libexpat) is malformed
On Sun, Sep 22, 2019 at 12:42:25PM -0700, Jonathan Thornburg wrote: > I'm trying to use syspatch to update a firewall (a PC Engines Alix) > running 6.5-stable/i386, but syspatch dies with an error message saying > that the patch file contains inappropriate filenames: > > # uname -a > OpenBSD sodium.bkis-orchard.net 6.5 GENERIC#3 i386 > # cat /etc/installurl > https://cdn.openbsd.org/pub/OpenBSD > # ls -gFlk /bsd* > -rwx-- 2 root wheel 13518991 Sep 10 18:23 /bsd* > -rwx-- 2 root wheel 13518991 Sep 10 18:23 /bsd.booted* > -rw--- 1 root wheel 8843776 May 12 16:43 /bsd.rd > # syspatch -l > 001_rip6cksum > 002_srtp > 004_bgpd > 005_libssl > 006_tcpsack > 007_smtpd > 010_frag6ecn > # syspatch -c > 011_expat > # syspatch > Get/Verify syspatch65-011_expat.tgz 100% |**| 546 KB00:00 > > Installing patch 011_expat > tar: Pattern matching characters used in file names > tar: Use --wildcards to enable pattern matching, or --no-wildcards to > suppress this warning > tar: @usr/share/relink/kernel/GENERIC.MP/.*@@g: Not found in archive > tar: Exiting with failure status due to previous errors > # That message is not from OpenBSD's tar(1) implementation. > Is this a known issue with this patch? Is there an alternate way > (besides updating from source) to track -stable ?
Re: OpenBSD Project
Am 22.09.19 um 20:52 schrieb Mihai Popescu: >> No. > > Security, privacy or too messy? > Theo's answer was deep going, detailed and terminal. Nothing to add.
6.6-beta - startup suspends until display is connected
Hi, list On my box running snapshots I'm obsering following: startup suspends until display is connected. I've connected displays via HDMI and DP. I couldn't identify for sure where this happens, but looks like the hang comes after disks are mounted. Once display is connected, kbd is set and dhclient is run. Again, it's difficult to tell exactly, as it takes a moment or two for the picture to appear. On 6.5 (and before) it could run headless without issues. In fact, I have a similar box with 6.5 acting as file server in my parents' home. Any ideas where I could look further to debug? dmesg below: OpenBSD 6.6-beta (GENERIC.MP) #315: Wed Sep 18 19:01:31 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8223297536 (7842MB) avail mem = 7961391104 (7592MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9d0 (17 entries) bios0: vendor American Megatrends Inc. version "P1.70" date 02/27/2018 bios0: ASRock N3150-NUC acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT AAFT MCFG SSDT SSDT SSDT UEFI SSDT TPM2 LPIT CSRT acpi0: wakeup devices XHC1(S4) HDEF(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PWRB(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) Celeron(R) CPU N3150 @ 1.60GHz, 1600.37 MHz, 06-4c-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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache tsc_timecounter_init: TSC skew=0 observed drift=0 cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 79MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) TSC skew=0 cpu1: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1600.00 MHz, 06-4c-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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 1MB 64b/line 16-way L2 cache tsc_timecounter_init: TSC skew=0 observed drift=0 cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) TSC skew=-100 cpu2: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1600.00 MHz, 06-4c-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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 1MB 64b/line 16-way L2 cache tsc_timecounter_init: TSC skew=-100 observed drift=0 cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) TSC skew=70 cpu3: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1600.00 MHz, 06-4c-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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 1MB 64b/line 16-way L2 cache tsc_timecounter_init: TSC skew=70 observed drift=0 cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: CLK0, resource for CAMD acpipwrres1 at acpi0: CLK0, resource for CAM1 acpipwrres2 at acpi0: CLK1, resource for CAM2, CAM3 acpipwrres3 at acpi0: USBC, resource for XHC1 acpicmos0 at acpi0 acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 "NTN0530" at acpi0 not configured "BCM2E64" at acpi0 not configured "BCM4752" at acpi0 not configured "SMO91D0" at acpi0 not configured "INT33F7" at acpi0 no
Re: OpenBSD Project
No means no. Sent from my iPhone > On 22 Sep 2019, at 20:54, Mihai Popescu wrote: > > >> >> No. > > Security, privacy or too messy?
syspatch says 6.5 patch #011 (libexpat) is malformed
I'm trying to use syspatch to update a firewall (a PC Engines Alix) running 6.5-stable/i386, but syspatch dies with an error message saying that the patch file contains inappropriate filenames: # uname -a OpenBSD sodium.bkis-orchard.net 6.5 GENERIC#3 i386 # cat /etc/installurl https://cdn.openbsd.org/pub/OpenBSD # ls -gFlk /bsd* -rwx-- 2 root wheel 13518991 Sep 10 18:23 /bsd* -rwx-- 2 root wheel 13518991 Sep 10 18:23 /bsd.booted* -rw--- 1 root wheel 8843776 May 12 16:43 /bsd.rd # syspatch -l 001_rip6cksum 002_srtp 004_bgpd 005_libssl 006_tcpsack 007_smtpd 010_frag6ecn # syspatch -c 011_expat # syspatch Get/Verify syspatch65-011_expat.tgz 100% |**| 546 KB00:00 Installing patch 011_expat tar: Pattern matching characters used in file names tar: Use --wildcards to enable pattern matching, or --no-wildcards to suppress this warning tar: @usr/share/relink/kernel/GENERIC.MP/.*@@g: Not found in archive tar: Exiting with failure status due to previous errors # Is this a known issue with this patch? Is there an alternate way (besides updating from source) to track -stable ? -- -- "Jonathan Thornburg [remove -color to reply]" "He wakes me up every morning meowing to death because he wants to go out, and then when I open the door he stays put, undecided, and then glares at me when I put him out" -- Nathalie Loiseau (French minister for European Affairs, explaining why she named her cat "Brexit")
Re: OpenBSD Project
> No. Security, privacy or too messy?
Re: bgpctl sho ri nei terse output vs man page discrepancy
On 2019-09-22, Rachel Roch wrote: > Hi, > > Hopefully I'm not missing something silly here but I've read the paragraph in > the man page and it only lists 15 variables: > > "The printed numbers are the sent and received open, > sent and received notifications, sent and received > updates, sent and received keepalives, and sent and > received route refresh messages plus the current and > maximum prefix count, the number of sent and received > updates, and withdraws." > > But bgpctl sho ri nei outputs 16 numbers, not 15 ? Sent and recevied updates, sent and received withdraws. Unfortunately the peer's name/address is missing, which makes it a bit tricky to use with "group", though it's not very convenient to change the output format now ..
Re: bgpctl sho ri nei terse output vs man page discrepancy
On Sun, Sep 22, 2019 at 02:08:50PM +0200, Rachel Roch wrote: > Hi, > > Hopefully I'm not missing something silly here but I've read the paragraph in > the man page and it only lists 15 variables: > > "The printed numbers are the sent and received open, > sent and received notifications, sent and received > updates, sent and received keepalives, and sent and > received route refresh messages plus the current and > maximum prefix count, the number of sent and received > updates, and withdraws." > > But bgpctl sho ri nei outputs 16 numbers, not 15 ? > You should read "sent & received withdraws". >
Re: [OpenIKED] Network traffic over VPN site-to-site tunnel stalls few times a day
Thank you Stuart. I can't touch/upgrade these routers, but I have a bunch of Soekris/net5501 that I can use for testing -current. Unfortunately, they are i386. I hope the arch doesn't matter in this case. I'll try -current asap. Am I the only one @misc who's facing this kind of iked issue? Nobody else reports having the same issue here... On Fri, 20 Sep 2019 16:55:02 - (UTC) Stuart Henderson wrote: > On 2019-09-20, radek wrote: > > Hello Patrick, > > I am sorry for the late reply. > > > > I have replaced my ALIX/Soekris production routers with APU1C and with PC > > box (cpu0: Intel(R) Pentium(R) D CPU 2.80GHz, 2810.34 MHz, 0f-06-04). > > Both are running 6.5/amd64 and both are fully syspatched. > > Please try a -current snapshot for starters, quite a number of iked bugs > have been fixed since then including some which would cause connectivity > problems during rekeying. (If you *really* can't update the whole thing, > it should work to build -current iked on a 6.5 system, but no guarantees). > > -- Radek
bgpctl sho ri nei terse output vs man page discrepancy
Hi, Hopefully I'm not missing something silly here but I've read the paragraph in the man page and it only lists 15 variables: "The printed numbers are the sent and received open, sent and received notifications, sent and received updates, sent and received keepalives, and sent and received route refresh messages plus the current and maximum prefix count, the number of sent and received updates, and withdraws." But bgpctl sho ri nei outputs 16 numbers, not 15 ? Any clues ? Rachel
Re: OpenBSD Project
>Sorry guys for continuing this stupid thread, but a small question related >to the racks and hardware from Theo's basement: >There is a photo (probably from that basement) on the main page : >https://www.openbsd.org/images/rack2009.jpg >I assume it is from 2009, so it is quite old, is it possible to see fresh >photos from that basement ??? No.
Re: OpenBSD Project
Sorry guys for continuing this stupid thread, but a small question related to the racks and hardware from Theo's basement: There is a photo (probably from that basement) on the main page : https://www.openbsd.org/images/rack2009.jpg I assume it is from 2009, so it is quite old, is it possible to see fresh photos from that basement ??? Thanks On Sat, Sep 21, 2019 at 2:40 PM Mark Jamsek wrote: > Ingo Schwarze wrote > > Avstin Kim wrote: > > > >> My question is, how is the OpenBSD Project governance structured; > > > > There is no formal structure and no "governance". > > > > ... > > > > If your choice of operating system depends on any kind of formalities > > rather than on technical quality, OpenBSD is not the project you > > are looking for. > > > > Yours, > > Ingo > > This is one of the ardently appealing factors of OpenBSD; technical quality > isn't compromised or superseded by other arbitrary and subjective measures. > > The singular focus on technical quality and correctness is reassuring and > consistently produces a reliable, performant product. > > It's certainly a quality that I find appealing and keeps me looking to > contribute > however I can to the project. > > Ingo articulated this response so well, I wanted to remark on how I feel > the > OpenBSD approach is received—at least for me. And to say thank you for the > many contributions made these last 25 years. > > Thanks. > > > > -- > Sent from: > http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html > >
