Re: access rdomain0 localhost from rdomainN
On 2023-05-14, Joel Carnat wrote: I have unbound listening on lo0 (127.0.0.1, rdomain0) and resolv.conf configured with "nameserver 127.0.0.1". You can also have unbound(8) listen on lo1. Without more information-for example, showing what pf.conf(5) contains- there is no way we can help you. I have two rdomain(4)s, and I have no issue pinging both lo(4) interfaces (both interfaces have the IPv6 and IPv4 loopback addresses assigned to them): router$ ping6 -nc1 ::1 PING ::1 (::1): 56 data bytes 64 bytes from ::1: icmp_seq=0 hlim=64 time=0.056 ms --- ::1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.056/0.056/0.056/0.000 ms router$ ping -nc1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.054 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.054/0.054/0.054/0.000 ms router$ ping6 -V1 -nc1 ::1 PING ::1 (::1): 56 data bytes 64 bytes from ::1: icmp_seq=0 hlim=64 time=0.048 ms --- ::1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.048/0.048/0.048/0.000 ms router$ ping -V1 -nc1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.043 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.043/0.043/0.043/0.000 ms Is it possible to access lo0 from other rdomains? There shouldn't be anything you have to do to access the loopback interface within its own rdomain; however if you want to access an interface that is part of a separate rdomain, you will likely need to instruct pf to use a separate rtable(4).
Re: 7.3 vmm/vmd shutdown page flush behavior?
--- Original Message --- On Sunday, May 14th, 2023 at 5:00 PM, Dave Voutila wrote: > not jacinda ardern not.jacinda.ard...@proton.me writes: > > > Perhaps it's just me, but upon upgrading to 7.3, I noticed that when VMs > > shut down, there appears to be a flurry of disk activity right after the > > VM OS shuts down, which seems like page flushing of mapped and/or cached > > pages. I seem to also not recall as high a value for cached memory usage > > in 7.2, but perhaps I just never really looked before. > > > Pretty sure you mean -current and you're following snapshots, right? If > so, I just introduced changes to resolve this that may not be in the > latest snaps yet. > > If you're seeing this on a 7.3-stable/release system, I'd be a bit > surprised. Yes, apologies --- I was experimenting with the snapshots in front of 7.3, and that is where I saw the problem. I'd be curious to see the changes if you have a link handy, I don't know much about the vmm subsystem.
Re: 7.3 vmm/vmd shutdown page flush behavior?
not jacinda ardern writes: > Perhaps it's just me, but upon upgrading to 7.3, I noticed that when VMs > shut down, there appears to be a flurry of disk activity right after the > VM OS shuts down, which seems like page flushing of mapped and/or cached > pages. I seem to also not recall as high a value for cached memory usage > in 7.2, but perhaps I just never really looked before. Pretty sure you mean -current and you're following snapshots, right? If so, I just introduced changes to resolve this that may not be in the latest snaps yet. If you're seeing this on a 7.3-stable/release system, I'd be a bit surprised. -dv
access rdomain0 localhost from rdomainN
Hi, I have configured rdomain 1 and bound daemons (httpd and relayd) to it. They work as expected but I still have issues with DNS resolving on localhost. I have unbound listening on lo0 (127.0.0.1, rdomain0) and resolv.conf configured with "nameserver 127.0.0.1". When I try to use it from my other rdomain, the connection (from nslookup or dig) is not possible. Even pinging the IP is not working: # route -T 0 exec ping -n -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.138 ms # route -T 1 exec ping -n -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes --- 127.0.0.1 ping statistics --- 1 packets transmitted, 0 packets received, 100.0% packet loss I can still ping external IPs though: # route -T 1 exec ping -n -c 1 9.9.9.9 PING 9.9.9.9 (9.9.9.9): 56 data bytes 64 bytes from 9.9.9.9: icmp_seq=0 ttl=58 time=0.453 ms I have tried using the "reject" and "pf" examples from the rdomain manpage but it doesn't solve my issue. I'm not even sure I understood what it was supposed to do :) Is it possible to access lo0 from other rdomains? Thanks, Joel C.
7.3 vmm/vmd shutdown page flush behavior?
Perhaps it's just me, but upon upgrading to 7.3, I noticed that when VMs shut down, there appears to be a flurry of disk activity right after the VM OS shuts down, which seems like page flushing of mapped and/or cached pages. I seem to also not recall as high a value for cached memory usage in 7.2, but perhaps I just never really looked before. Some details: 11th gen intel cpu pci-e ssd, nothing special softdep enabled on drive with disk images qcow2 images mix of linux/openbsd (6.x kernels, 7.2/7.3 obsd) disk images exceed system memory vm memory is < 50% of system memory happens with a single vm some vm instances do have swap configured but doesn't seem to get used I'd be curious if anyone else had noticed something similar, or if there were some obvious tuning settings I didn't see in a quick peek at the FAQ. Eg does the vmm/vmd subsystem prefer specific mount options. Thanks.
Re: Pkg_add Python version and LibreSSL seem to be incompatible in OpenBSD 7.3
Thank you Otto! pip install urllib3==1.26.15 replaced the v2 version with the latest non v2 version, and now my scripts work again. On 5/14/23 14:34, Otto Moerbeek wrote: On Sun, May 14, 2023 at 12:25:28PM -0400, Judah Kocher wrote: After updating one of my routers to OpenBSD 7.3, my python scripts that update various public DNS records when my public IP changes started failing with generic segfaults. I did see the note in the OpenBSD Upgrade Guide about 3.10 being the new default so I ran pkg_add -u which updated python to 3.10 and now the same scripts fail but with this error: ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with LibreSSL 3.7.2. See: https://github.com/urllib3/urllib3/issues/2168 The included github link mentions that older versions of SSL are no longer usable with the urllib library but makes no mention of LibreSSL. Some web searching has not turned up any details around this. I also do not see python 3.9 as an installable option via pkg_add, just 3.10 and 3.11. Does this mean that installing python via pkg_add installs a python version that is incompatible with LibreSSL? When I look at the info for the OpenSSL package it includes this warning: This package is not intended for general-purpose use in OpenBSD - it is present for test/comparison purposes, and occasionally to provide support for applications which cannot be made compatible with LibreSSL (mostly due to use of removed APIs); in the latter case care must be taken - it will conflict if library dependencies use LibreSSL libraries. What would be the best way to resolve this issue? I would guess that plenty of others are using python with OpenBSD so there must be a recommended resolution, but I have not found it documented anywhere yet. Thanks! Judah The problem is very likely a version of urllib3 installed via pip, and has little to do with the python version itself. -Otto -- Judah Kocher Assistant Chief Cochranville Fire Company 484-266-9257
Re: Pkg_add Python version and LibreSSL seem to be incompatible in OpenBSD 7.3
On Sun, May 14, 2023 at 12:25:28PM -0400, Judah Kocher wrote: > After updating one of my routers to OpenBSD 7.3, my python scripts that > update various public DNS records when my public IP changes started failing > with generic segfaults. I did see the note in the OpenBSD Upgrade Guide > about 3.10 being the new default so I ran pkg_add -u which updated python to > 3.10 and now the same scripts fail but with this error: > > ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' > module is compiled with LibreSSL 3.7.2. See: > https://github.com/urllib3/urllib3/issues/2168 > > The included github link mentions that older versions of SSL are no longer > usable with the urllib library but makes no mention of LibreSSL. > > Some web searching has not turned up any details around this. I also do not > see python 3.9 as an installable option via pkg_add, just 3.10 and 3.11. > Does this mean that installing python via pkg_add installs a python version > that is incompatible with LibreSSL? When I look at the info for the OpenSSL > package it includes this warning: > > This package is not intended for general-purpose use in OpenBSD - it > is present for test/comparison purposes, and occasionally to provide > support for applications which cannot be made compatible with LibreSSL > (mostly due to use of removed APIs); in the latter case care must be > taken - it will conflict if library dependencies use LibreSSL libraries. > > What would be the best way to resolve this issue? I would guess that plenty > of others are using python with OpenBSD so there must be a recommended > resolution, but I have not found it documented anywhere yet. > > > Thanks! > > Judah > The problem is very likely a version of urllib3 installed via pip, and has little to do with the python version itself. -Otto
Pkg_add Python version and LibreSSL seem to be incompatible in OpenBSD 7.3
After updating one of my routers to OpenBSD 7.3, my python scripts that update various public DNS records when my public IP changes started failing with generic segfaults. I did see the note in the OpenBSD Upgrade Guide about 3.10 being the new default so I ran pkg_add -u which updated python to 3.10 and now the same scripts fail but with this error: ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with LibreSSL 3.7.2. See: https://github.com/urllib3/urllib3/issues/2168 The included github link mentions that older versions of SSL are no longer usable with the urllib library but makes no mention of LibreSSL. Some web searching has not turned up any details around this. I also do not see python 3.9 as an installable option via pkg_add, just 3.10 and 3.11. Does this mean that installing python via pkg_add installs a python version that is incompatible with LibreSSL? When I look at the info for the OpenSSL package it includes this warning: This package is not intended for general-purpose use in OpenBSD - it is present for test/comparison purposes, and occasionally to provide support for applications which cannot be made compatible with LibreSSL (mostly due to use of removed APIs); in the latter case care must be taken - it will conflict if library dependencies use LibreSSL libraries. What would be the best way to resolve this issue? I would guess that plenty of others are using python with OpenBSD so there must be a recommended resolution, but I have not found it documented anywhere yet. Thanks! Judah
Re: vi - inability to search backwards for ?
On 2023-05-13 20:53:01 -0700, Kastus Shchuka wrote: > Have you tried using ?[\?] in extended mode? It works for me. Yes, that's already in the blog posting and is a bit more to type and remember than a ?\?
LibreOffice JRE Error
$ uname -a OpenBSD Leo.my.domain 7.3 GENERIC.MP#1125 amd64 With libreoffice-java-7.5.1.2v installed and enabled, I get the following error message when using LibreOffice: $ libreoffice CarolyAddress.odt [0.009s][warning][os,thread] Attempt to protect stack guard pages failed (0x7848f9a5f000-0x7848f9a63000). # # A fatal error has been detected by the Java Runtime Environment: # Native memory allocation (mprotect) failed to protect 16384 bytes for memory to guard stack pages This error only happens when loading *.odt or *.ods files. It does not happen when loading *.odp presentation documents. If I disable the JRE, by uncehcking the box in Tools->Options->Advanced, then LibreOffice does not show any errors. LibreOffice did not show this error on OpenBSD 7.2. I use OpenBSD as a desktop and probably use LibreOffice several times a week. Any advice on how to fix this would be greatly appreciated. My computer is a Lenovo T440. I ran a hardware diagnostics test on the laptop and it passed all tests. -- Kind regards, Jonathan
