syspatch on raspberry pi 3. new kernel?
I just ran syspatch on my Raspberry Pi 3 running OpenBSD 7.0 and the
patches initially appeared to have been applied successfully, including
creating a new kernel and printing the message to reboot to use the new
kernel.
Upon reboot, motd, dmesg, and "sysctl kern.version" still report what I
believe to be the original kernel:
OpenBSD 7.0 (GENERIC) #1280: Thu Sep 30 16:31:07 MDT 2021
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC
That said, the new /bsd (and /bsd.booted) are dated today, as would be
expected following syspatch. The result of "sha256 /bsd" matches the
data in /var/db/kernel.SHA256 (file also dated today as would be
expected). What else? I have also run "syspatch -R" to remove the
updates, rebooted, then ran syspatch again with the same results. And
it seems that /etc/motd is not being updated on boot on this system as I
think usually happens. /var/run/dmesg.boot does appear to be updated
with each boot. /usr/share/relink/kernel/GENERIC.MP/relink.log appears
normal:
(SHA256) /bsd: OK
LD="ld" sh makegap.sh 0xd4d4d4d4 gapdummy.o
ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o
${OBJS}
textdatabss dec hex
10566181611208 829392 12006781b7357d
mv newbsd newbsd.gdb
ctfstrip -S -o newbsd newbsd.gdb
rm -f bsd.gdb
mv -f newbsd bsd
install -F -m 700 bsd /bsd && sha256 -h /var/db/kernel.SHA256 /bsd
Kernel has been relinked and is active on next reboot.
SHA256 (/bsd) =
1e457ddd75e56de0b8cc01607a5d0be6903be07ee0c2baeb440e823a253e68a0
Running syspatch on two other systems (an old Alix/i386 and a vm at
vultr.com) resulted in expected results:
OpenBSD 7.0 (GENERIC) #1: Fri Oct 29 12:02:30 MDT 2021
r...@syspatch-70-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
OpenBSD 7.0 (GENERIC) #1: Fri Oct 29 12:02:41 MDT 2021
r...@syspatch-70-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Any ideas will be greatly appreciated. Am I missing any steps here?
Thanks,
Joe
Following is the latest dmesg from this rpi3:
OpenBSD 7.0 (GENERIC) #1280: Thu Sep 30 16:31:07 MDT 2021
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC
real mem = 956735488 (912MB)
avail mem = 894844928 (853MB)
random: boothowto does not indicate good seed
mainbus0 at root: Raspberry Pi 3 Model B Rev 1.2
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1
D-cache
cpu0: 512KB 64b/line 16-way L2 cache
cpu0: CRC32,ASID16
apm0 at mainbus0
efi0 at mainbus0: UEFI 2.8
efi0: Das U-Boot rev 0x20210100
simplefb0 at mainbus0: 656x416, 32bpp
wsdisplay0 at simplefb0 mux 1
wsdisplay0: screen 0-5 added (std, vt100 emulation)
"system" at mainbus0 not configured
"axi" at mainbus0 not configured
simplebus0 at mainbus0: "soc"
bcmclock0 at simplebus0
bcmmbox0 at simplebus0
bcmgpio0 at simplebus0
bcmaux0 at simplebus0
bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA8 DMA9 DMA10
bcmintc0 at simplebus0
bcmrng0 at simplebus0
pluart0 at simplebus0: console
bcmsdhost0 at simplebus0: 250 MHz base clock
sdmmc0 at bcmsdhost0: 4-bit, sd high-speed, mmc high-speed, dma
dwctwo0 at simplebus0
bcmdog0 at simplebus0
bcmtemp0 at simplebus0
"local_intc" at simplebus0 not configured
sdhc0 at simplebus0
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc1 at sdhc0: 4-bit, sd high-speed, mmc high-speed
simplebus1 at simplebus0: "firmware"
"clocks" at simplebus1 not configured
"expgpio" at simplebus1 not configured
"power" at simplebus0 not configured
"mailbox" at simplebus0 not configured
"gpiomem" at simplebus0 not configured
"fb" at simplebus0 not configured
"vcsm" at simplebus0 not configured
"virtgpio" at simplebus0 not configured
"clocks" at mainbus0 not configured
"phy" at mainbus0 not configured
"arm-pmu" at mainbus0 not configured
agtimer0 at mainbus0: 19200 kHz
"leds" at mainbus0 not configured
"fixedregulator_3v3" at mainbus0 not configured
"fixedregulator_5v0" at mainbus0 not configured
"bootloader" at mainbus0 not configured
dt: 445 probes
usb0 at dwctwo0: USB revision 2.0
sdmmc0: can't enable card
uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
2.00/1.00 addr 1
uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard Microsystems
product 0x9514" rev 2.00/2.00 addr 2
bwfm0 at sdmmc1 function 1
manufacturer 0x02d0, product 0xa9a6 at sdmmc1 function 2 not configured
smsc0 at uhub1 port 1 configuration 1 interface 0 "Standard Microsystems
SMSC9512/14" rev 2.00/2.00 addr 3
smsc0: address b8:27:eb:8b:a1:c7
ukphy0 at smsc0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x0001f0, model 0x000c
umass0 at uhub1 port 5 configuration 1 interface 0 "SanDisk Cruzer Fit"
rev 2.10/1.00 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: removable
serial.07815571750216101493
sd0: 7632MB, 512 bytes/sector, 15630336 sectors
vscsi0 at root
scsibus1 at vscsi0: 256 targets
sof
Re: httpd(8) - PHP: More details in error log
On 2021-10-07 18:28, J. K. wrote: Hi, I have a question to OpenBSD's httpd and PHP. Don't know if this is httpd related or PHP. With the default settings it's hard to debug error with my PHP script, because under /var/www/logs/error.log there is no timestamp or the requested URI. Is there a configuration for httpd or PHP to get more details in the error log? Thanks in advance. BTW: This is my second mail with the same context on this list. But had some troubles with my domain. Kind regards, J. K. My apologies as I am not really answering your question, but here goes. My OpenBSD machine running httpd is solely for learning, and it is low volume. To simplify debugging, I log both access and errors to /var/www/logs/error.log with the following entries in /etc/httpd.conf log access "error.log" log error "error.log" log style forwarded The access information tells me about URI, timestamp, browser/agent, things of that nature. Along with the errors that are logged in the same file, I then can easily associate a PHP error with a URI or timestamp. My php and php-fpm files are unchanged from the defaults. My guess is there are options that can be set in /etc/php-8.0.ini but I have not checked nor made any changes to that file. (I have php/fpm 8.0 installed on my OpenBSD 6.9 system; you might have different versions installed) Anyway, this might be helpful for you in the short term -- until you are able to more correctly log the information you need. -- Joe Barnett
Re: AMD Ryzen
On 2020-06-23 08:56, Gregory Edigarov wrote: Hello, Can somebody tell me overall impressions/success stories of those systems? I am thinking of buying this system as my next desktop for OpenBSD of course, so please share. Most interesting would be dmesgs of some working configurations. Thanks a lot in advance -- With best regards, Gregory Edigarov I have a Ryzen 3 3200G sitting on an ASRock B450M-HDV R4.0 with 16GB RAM, and it seems to run OpenBSD (6.7) very well. I added Window Maker via packages, along with a few others such as firefox-esr, pidgin, qgis, postgresql (both server and client), and a few others, again all from packages. Bear in mind I usually use OpenBSD for network devices rather than on the desktop, but my experiment so far with the above system and config has been very positive -- very stable and responsive when booted into the graphical environment. This machine has no wifi capability, so I cannot comment on that, and I do not have speakers attached, so cannot comment on sound support. This CPU is a somewhat new-ish model with built-in Radeon Vega graphics which gave fits to several Linux distros*, but which seems to work right out of the box with OpenBSD 6.7. *latest Debian, and latest Xubuntu experienced trouble on this machine when in graphical mode, though the latest regular Ubuntu does work nicely with this machine. Good luck, Joe dmesg: OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 14941401088 (14249MB) avail mem = 14475939840 (13805MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe6cc0 (24 entries) bios0: vendor American Megatrends Inc. version "P3.70" date 11/14/2019 bios0: ASRock B450M-HDV R4.0 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG AAFT HPET UEFI SSDT CRAT CDIT SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) GP18(S4) GPP1(S4) PTXH(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 3 3200G with Radeon Vega Graphics, 3593.83 MHz, 17-18-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 3 3200G with Radeon Vega Graphics, 3593.21 MHz, 17-18-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 2, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: AMD Ryzen 3 3200G with Radeon Vega Graphics, 3593.21 MHz, 17-18-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0:
Re: OpenBSD Readonly File System
On 2020-06-09 00:59, Vertigo Altair wrote: Hi Misc, I have a firewall device and I'm using OpenBSD on it. There is an electricity problem where the device runs. Therefore, I have to run the "fsck -y" command regularly at startup due to the electricity problem. To overcome this, I want to use readonly file system. I know there are some projects like "resflash", but I want to do that manually. I have hacked and slashed my way to this kind of configuration for my firewall/gateway and a few other machines -- and with what appears to be good results. Please understand this is almost certainly not supported by the project. I have outlined this at the following URL: https://www.mr72.com/readonlyfs.html I hope this helps. Any feedback will be greatly appreciated. Good luck! Joe My partitions like this; vertigo# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/sd0a 3.9G489M3.2G13%/ /dev/sd0g 91.8G1.0G 86.2G 1%/mypartition /dev/sd0d 989M 12.0K940M 0%/tmp /dev/sd0f 3.9G1.7G2.0G46%/usr /dev/sd0e 3.9G 46.9M3.6G 1%/var I want to / and /usr as readonly, I updated /etc/fstab and I made / and /usr readonly; vertigo# cat /etc/fstab ec347fefe8d05509.b none swap sw ec347fefe8d05509.a / ffs ro 1 1 ec347fefe8d05509.g /mypartition ffs rw,nodev,nosuid 1 2 ec347fefe8d05509.d /tmp ffs rw,nodev,nosuid 1 2 ec347fefe8d05509.f /usr ffs ro,wxallowed,nodev 1 2 ec347fefe8d05509.e /var ffs rw,nodev,nosuid 1 2 On startup following errors comming from /etc/rc; I think errors about /etc/motd are not so important, but are the errors coming from /etc/tty* can cause any problems? If my method is not correct, what is the best way to do this? OpenBSD/amd64 BOOTX64 3.50 boot> booting hd0a:/bsd: 12957000+2753552+327712+0+708608 [807408+128+1024872+749630]=0x1271a18 entry point at 0x1001000 [ using 2583064 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2020 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4151607296 (3959MB) avail mem = 4013170688 (3827MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebf10 (14 entries) bios0: vendor American Megatrends Inc. version "BAR3NA05" date 07/23/2018 bios0: NF533 NF533 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG LPIT HPET SSDT SSDT SSDT UEFI acpi0: wakeup devices XHC1(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(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 J1900 @ 1.99GHz, 2000.37 MHz, 06-37-09 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,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 cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 83MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.01 MHz, 06-37-09 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,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 cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.03 MHz, 06-37-09 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,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 cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.01 MHz, 06-37-09 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,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SM
Re: Alix 2d13 and OpenBSD 6.5 Problems
On 2019-10-01 22:46, Sean Kamath wrote: Hi. I’m hoping someone either has a cluebat or some helpful suggestions beyond “reinstall”. I had an alix 2d13 running OpenBSD 6.3. I finally got around to upgrading to 6.4 (via https://www.openbsd.org/faq/upgrade64.html), and that seemed to go just fine (I used the Upgrading Manually section, since I don’t have (easy) access to the console). I let that run for a day, just to make sure all was well, and then attempted an upgrade to 6.5 (via https://www.openbsd.org/faq/upgrade65.html), again using the “Upgrading Manually” section. This time, between smtpd and relinking the kernel, it appears my Alix board is quickly running out of memory. Within a few seconds the sr rate is in the 20K range. I stopped the ld for relinking, and killed SMTPD in order to finish the install (the makedev ALL, sysmerge, pkg_update -u bits), and that all ran fine. But about 15-20 minutes after a reboot, the box just goes off the network, and there’s not much I can do. I can download and reinstall 6.5, but was hoping to avoid that pain, but I just want to make sure 6.5 has no issues on the Alix boards. . . I cannot comment on the upgrade process, but I have had zero fatal issues running 6.5 on my alix2d13 boards. That said, memory has been getting tighter with more recent OpenBSD versions, and swap (as someone else suggested) should help. I love these reliable boards, but they are starting to show their age (at least relative to how I use them with OpenBSD). Thanks! I’d attach dmesg, but the box is dead again. . . If anyone wants to dive into what’s going on, just let me know what info you want to see. Sean
unbound/dns issue (malformed packets?)
I've been seeing some issues which I believe to be related to dns/resolving. The short of it is that the results of # dig web.whatsapp.com start out as: ; <<>> DiG 9.4.2-P2 <<>> web.whatsapp.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57665 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;web.whatsapp.com. IN A ;; ANSWER SECTION: web.whatsapp.com. 3595IN CNAME mmx-ds.cdn.whatsapp.net. mmx-ds.cdn.whatsapp.net. 55 IN A 31.13.70.49 ;; Query time: 6 msec ;; SERVER: 192.168.254.254#53(192.168.254.254) ;; WHEN: Sun Sep 15 14:46:24 2019 ;; MSG SIZE rcvd: 87 which seems reasonable (and functional), but then soon become: ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.4.2-P2 <<>> web.whatsapp.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40939 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;web.whatsapp.com. IN A ;; ANSWER SECTION: web.whatsapp.com. 3528IN CNAME mmx-ds.cdn.whatsapp.net. mmx-ds.cdn.whatsapp.net. 30772 RESERVED0 A \# 4 1F0D4631 ;; Query time: 2 msec ;; SERVER: 192.168.254.254#53(192.168.254.254) ;; WHEN: Sun Sep 15 14:47:31 2019 ;; MSG SIZE rcvd: 87 At which point I am no longer able to access web.whatsapp.com. Given that whatsapp is a facebook property, I tried the above against facebook.com, www.facebook.com, instagram.com, and www.instagram.com as well. With the exception of instagram.com, the other three (facebook, www.facebook, www.instagram) return a hex (?) formatted version of the IP address, similar to what is seen in the later of the above examples. My thinking is (or was) that there are some issues relating to fb's DNS. From outside of my network, however, other resolvers seem to be able to continually resolve the above names correctly. I don't know what those resolvers are, but specifically I am referring to whatever Linode and DigitalOcean use in the nameservers they provide to their basic Linux vms (I am using the default network config in my vms at Linode and DigitalOcean). I have a suspicion that Linode uses unbound, but I do not know how to verify that. Oh, as far as I can tell, those facebook-family names *seem* to be the only names for which I see this behavior -- all other names that I have tried to run through dig (and nslookup) seem to return reasonable and seemingly correct results. A bit about my (home) network. I have Cox cable internet service, an Arris SBG7580-AC, and an OpenBSD 6.5 machine that sits between the modem and the rest of the network. I(we) do use the modem in router mode (but without using the built-in WiFi) as my wife's work git-up consists of a pre-configured black-box of a Juniper device. Not wanting that device in the rest of our network, I set the modem to "RoutedWithNAT" and the two network devices plug into the modem, but provide two separate networks. For remote ingress into the rest of the network, I set the modem's DMZ to point to the OpenBSD box. My pf.conf does the usual small network stuff including NAT, a bit of redirection, etc. It has changed very little in the past several years. My unbound.conf is also nearly unchanged since I first set it up when OpenBSD dropped bind and replaced it with unbound. My OpenBSD machine provides name resolving for the rest of the network. My unbound.conf follows: server: interface: 0.0.0.0 interface: ::1 do-ip6: no access-control: 0.0.0.0/0 refuse access-control: 127.0.0.0/8 allow access-control: 192.168.0.0/16 allow access-control: 10.0.0.0/24 allow access-control: 172.16.0.0/24 allow access-control: ::0/0 refuse access-control: ::1 allow hide-identity: yes hide-version: yes # ftp://FTP.INTERNIC.NET/domain/named.cache root-hints: "/var/unbound/etc/named.cache" # uncomment to enable DNSSEC auto-trust-anchor-file: "/var/unbound/db/root.key" ### various local-zone, local-data, and local-date-ptr ### remote-control: control-enable: yes control-use-cert: yes control-interface: /var/run/unbound.sock do-ip6, root-hints, and auto-trust-anchor-file are somewhat recent additions to my unbound.conf, but I experience the same behavior with unbound.conf as above, and also when I comment out those three additions (bringing it back to a configuration that has worked for several years). My OpenBSD machine is an APU2 which I have been using without issue for over a year. My backup machine is an ALIX2D3 I think it is called. Other than the APU running amd64, and the ALIX running i386, the machines are otherwise configured exactly the same. The APU2 has been consistently maintained, and this b
Re: Donations
On 12/5/10 5:11 PM, Jamie Paul Griffin wrote: > > if nothing else think about the charges they put on every transaction: you > sell something on ebay, they charge you; you process their payment through > paypal (ebay) they charge you again. they're clearly ripping us all us all > off - fact! and to top it all of the charges have become extortionate. > Perhaps everything should just be (lowercase) free? No charge ever for anything. Heck, if that is how it worked, then this entire discussion would not be taking place as OpenBSD would not need funds to continue its operations (and in that sense I would be greatly relieved, since I would likely have to hear less about Theo's selective outrage. Speaking of that outrage, I think it would be great if he put his money where his mouth is and not accept US dollars in support of OpenBSD... but I am not holding my breath). But things are not free. It takes commerce to produce nearly every material good, as distasteful as that might be to some people. It is called business. No one is forcing anyone to use ebay or paypal. If anyone wants to play in their marketplace, however, they must play by the established rules.
Re: Sending email in Apache chroot?
Sunnz wrote: > I have set up mail and femail and they both works, just not in a chroot. > > Basically I can do `mail m...@myaddress.com` or `/var/www/bin/femail > m...@myaddress.com` and both of then successfully sent an email to > myself. > > But it doesn't work with Apache in the chroot. I was using a PHP script. > > femail-chroot is installed by pkg_add -iv femail-chroot. > > I also tried the following: > > `chroot -g www -u www / /var/www/bin/femail -t -i m...@myaddress.com` works, > but > > `chroot -g www -u www /var/www/ /bin/femail -t -i m...@myaddress.com` > doesn't work, it says: > > femail: non-recoverable failure in name resolution > > I run out of ideas now, what needs to be done? > Many moons ago I had the same situation with mini-sendmail-chroot. Installing mail (?) and sh in the chroot seemed to clear everything up--though I am not sure if that is the optimal solution. -- Joe Barnett joe.barn...@mr72.com http://www.mr72.com/ 623.670.1326
out-of-date ports/packages?
I get the following message when running /usr/ports/infrastructure/build/out-of-date: Collecting installed packages Collecting port versions: complete Collecting port signatures: complete Outdated ports: devel/gettext # expat.4.0 -> expat.5.0 www/php5/extensions,-mysql # mysql-client-5.0.18p0 -> mysql-client-5.0.21 My ports tree is up-to-date against OPENBSD_3_9 (machine is i386, 3.9, patches from errata.html are applied, as are updates to the ports tree). According to pkg-stable.html, all of my packages are up-to-date. To test, I have built and installed /usr/ports/textproc/expat (first) then /usr/ports/devel/gettext (second) from my updated ports tree. Far as I can tell, these are the same versions that were originally installed, and the above message still shows when running out-of-date. As for php5-mysql, trying to build that from the ports tree fails at "configure: error: xpm.h not found." (any idea on how to get this to successfully build will be greatly appreciated -- oh, though this is a server (no X usage), X is installed as it was required to get the webalizer port installed. Far as I can tell xpm.h is usually found as part of X) mysql-server and mysql-client are both up-to-date at 5.0.21 (also built from the updated ports tree). Everything on this machine appears to work very well, and I am wondering if the above out-of-date message is only informational, rather than indicating differences of a substantial nature. Thanks, Joe
uvm_fault in 3.9
My brand new installation of 3.9 (GENERIC, no patches applied as
yet) is failing often with similar type messages:
- start -
uvm_fault(0xd05c2f60, 0xd0dfb000, 0, 3) -> euvm_fault(0xd05c2f60,
0xd0dfb000, 0, 3) -> e
kernel: page fault trap, code-0
Stopped at uvm_fault+0x28c: incl uvmexp+0xf4
ddb>
- end -
"ddb> trace" output is:
- start -
uvm_fault(d60b9294,1c013000,0,1,3) at uvm_fault+0x28c
trap() at trap+0x259
--- trap (number 6) ---
0x1c0138cc:
ddb>
- end -
"ddb> ps" output is:
- start -
PID PPID PGRP UID SFLAGS WAIT COMMAND
*5095 3924 3924 0 7 0x4006 mount
39241 3924 0 3 0x4086 pause sh
1200 0 3 0x100204 crypto_wa crypto
1100 0 3 0x100204 aiodoned aiodoned
1000 0 3 0x100204 syncerupdate
900 0 3 0x100204 cleaner cleaner
800 0 3 0x100204 reaperreaper
700 0 3 0x100204 pgdaemon pagedaemon
600 0 3 0x100204 pftm pfpurge
500 0 3 0x100204 usbtskusbtask
400 0 3 0x100204 usbevtusb0
300 0 3 0x100204 apmev apm0
200 0 3 0x100204 kmalloc kmthread
101 0 3 0x4084 wait init
0 -10 0 3 0x80204 scheduler swapper
ddb>
- end -
This particular output resulted from trace and ps following a crash
during boot, around the time (various) daemons are loading. By
various, sometimes the last loaded/attempted is httpd, another time
it is ntpd, another time it is sshd, etc. This has been tried
several times.
If the machine does manage to boot, it will die/crash in similar
fashion, the common element being uvm_fault. Often this will happen
while trying to update the ports tree or trying to apply the
sendmail patch, but it can happen at any time.
I usually have vm.swapencrypt.enable=1 in /etc/sysctl.conf, but have
tried it with default settings as well with the same result. I have
tried mounting the drives with and without softupdates, again with
the same results.
This machine was fine (running OpenBSD for several years, the latest
being 3.8) until Friday when I did the upgrade. Since then I have
basically swapped out all of the cards, motherboard, memory, power
supply, even drives. Far as I can tell, the power supplied to the
machine is OK, and (again, far as I can tell) the power supplies
themselves are in good working order -- I have had power supplies
fail before and I keep an extra or two on hand just in case.
I have installed several times and this can happen as soon as the
first reboot following installation or after some configuration and
installation of packages has taken place. Currently I was able to
install the packages I normally use, and the machine started acting
up again during updating of the ports tree. At this point the
machine will not fully boot. Following is the dmesg output grabbed
while booting bsd.rd:
OpenBSD 3.9 (RAMDISK_CD) #1025: Thu Mar 2 02:43:29 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: AMD-K6(tm) 3D processor ("AuthenticAMD" 586-class) 401 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
real mem = 267952128 (261672K)
avail mem = 238661632 (233068K)
using 3296 buffers containing 13500416 bytes (13184K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(67) BIOS, date 08/03/99, BIOS32 rev. 0 @
0xfb260
apm0 at bios0: Power Management spec V1.2
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0xb6e8
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdcf0/144 (7 entries)
pcibios0: PCI Exclusive IRQs: 10 11 12
pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C586 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT82C597 PCI" rev 0x04
ppb0 at pci0 dev 1 function 0 "VIA VT82C598 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA Riva TNT" rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 "VIA VT82C586 ISA" rev 0x47
pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA33,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 12971MB, 26564832 sectors
atapiscsi0 at pciide0 channel 0 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom
removable
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
wd1 at pciide0 channel 1 drive 0:
wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd2 at pciide0 channel 1 drive 1:
wd2: 16-sector PIO, LBA, 78167MB, 160086528 sectors
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x02: irq 10
usb0 at uhci0
Re: pre-orders
Greg Thomas wrote: > > Any days that I know I'll be meeting co-workers from around the > country I wear my Blowfish polo. Either the Blowfish or the "Secure > by Default" always catches a few eyes and then I'm off with the spiel. > One of these days I'm going to get a cash donation out of someone > here. I did manage to donate a lowend dual G4 from work. > > Greg > I was *this close* to posting to this list "Why can I not get to https://https.openbsd.org/cgi-bin/order? If they want my money they should at least make sure the farggin' site works!" Well, turns out that instead of redirecting specific https traffic, I was redirecting all https traffic heading to the 68. range (an old rule that never caught me before... is https.openbsd.org hosted on a new sever?). Embarrassing, to be sure, but my laughter and guilt got me through ordering the CDs, the blue polo, the Baby T for my wife (she already uses an OpenBSD powered laptop and still does not know how cool that makes her -- maybe the T will help), and a donation. Keep up the good work. Joe
Re: OpenBSD 3.8+Mysql 5.0.16
Monah Baki wrote: Hi all, I'm installing mysql from source. I know this is an error that has been posted several times: # /usr/local/mysql/bin/mysql -V /usr/local/mysql/bin/mysql: can't load library '../libmysql/.libs/libmysqlclient.so.15.0' # cd /usr/local/mysql/bin # ./mysql -V # ./mysql Ver 14.12 Distrib 5.0.16, for unknown-openbsd3.8 (i386) using EditLine wrapper If I vi the mysql file in /usr/local/mysql/bin: SNIP. @[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@ [EMAIL PROTECTED]/libmysql/.libs/[EMAIL PROTECTED]@mysql_field_count SNIP. Does this mean libmysqlclient.so.15.0 is hardcoded and won't work unless you're in the /usr/local/mysql/bin directory. It works fine as long as long as you start the commands in the /usr/local/mysql/bin directory, if you change directory then you get the error. Thank you I went ahead and did the same (installed 5.0.16 from source) and had similar results, with the exception that even within the mysql/bin directory I still receive that same error. The daemon, however, runs well. I have had good luck, however, with the 5.0.16 build available at mysql.com. It is labeled for OpenBSD 3.7, but runs well on my 3.8 box without modification. Just a thought. Good luck, Joe
log file for OpenNTPD (on FreeBSD)
To which file does OpenNTPD log on a FreeBSD machine? Specifically, I am referring to (i386) machines running both FreeBSD versions 4.7 and 5.4. OpenNTPD is version 3.7p1 (I have tried both installing directly from source, and from [FreeBSD] ports). On my OpenBSD machines OpenNTPD logs to /var/log/daemon. And on my Linux machines OpenNTPD logs to /var/log/messages. But I cannot find the file to which it logs on the above mentioned FreeBSD machines. Bear in mind that all indicators are that it is working very well on FreeBSD, I simply am not able to find the logs. I have checked the archives and have not found much about this... Thanks, Joe
Re: problems adding packages in 3.7
Russell Fulton wrote: > Hi Folks, > I'm getting errors about missing libraries while adding packages to > a 3.7 system. This was a new install with 3.7 so there should not be > any old stuff laying around > > -bash-3.00$ sudo pkg_add > ftp://ftp.openbsd.org/pub/OpenBSD/3.6/packages/i386/recode-3.6p1.tgz > Can't install > ftp://ftp.openbsd.org/pub/OpenBSD/3.6/packages/i386/recode-3.6p1.tgz: > lib not found intl.1.1 > Even by looking in the dependency tree: >libiconv-1.9.2, gettext-0.10.40p2 > Maybe it's in a dependent package, but not tagged with @lib ? > (check with pkg_info -K -L) > If you are still running 3.6 packages, update them. > -bash-3.00$ uname -a > OpenBSD matata.insec.auckland.ac.nz 3.7 GENERIC#50 i386 > > I understand that it can not find lib intl.1.1 and that it has looked > for it in the package dependencies. However I don't understand what it > is suggesting I do with pkg_info (yes I've read the man page). > > A little more guidance would be appreciated. > > Cheers, Russell > It looks like your command is searching for packages in the 3.6 directory, not the 3.7 directory: ftp://ftp.openbsd.org/pub/OpenBSD/3.6/packages/i386/ should be: ftp://ftp.openbsd.org/pub/OpenBSD/3.7/packages/i386/ -- Joe
