Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
As an additional note; I upgraded my server yesterday from (amd64) OpenBSD 7.3 to 7.4 by sysupgrade tool (remotely - unattended way). Is it possible that the upgrade process created trouble with TLS, SSL libraries? It was completed without any "visible" issue, as far as I can tell. Regards. Mark , 3 Şub 2024 Cmt, 10:34 tarihinde şunu yazdı: > Hi again, > > I completely removed Postfix and installed the official stable package > "postfix-3.7.9p0-sasl2-mysql", but the problem persists. > > P.S.: The issue only happens with incoming mails from Gmail servers. > > (Well, I do have the needed lines recommended in smtp-smuggling page, the > ones for "works with all versions".) > > > Herbert J. Skuhra , 3 Şub 2024 Cmt, 10:28 tarihinde > şunu yazdı: > >> On Sat, Feb 03, 2024 at 09:19:47AM +0300, Mark wrote: >> > An experimental, unstable package in packages-stable? >> > >> > An outdated and potentially vulnerable software in the latest OpenBSD >> > 7.4-stable? >> > >> > I must really have been missing something here... >> >> Just a few links: >> >> >> https://github.com/openbsd/ports/blob/master/mail/postfix/snapshot/Makefile >> http://ftp.porcupine.org/mirrors/postfix-release/index.html#experimental >> https://www.postfix.org/smtp-smuggling.html >> >> -- >> Herbert >> >>
Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
Hi again, I completely removed Postfix and installed the official stable package "postfix-3.7.9p0-sasl2-mysql", but the problem persists. P.S.: The issue only happens with incoming mails from Gmail servers. (Well, I do have the needed lines recommended in smtp-smuggling page, the ones for "works with all versions".) Herbert J. Skuhra , 3 Şub 2024 Cmt, 10:28 tarihinde şunu yazdı: > On Sat, Feb 03, 2024 at 09:19:47AM +0300, Mark wrote: > > An experimental, unstable package in packages-stable? > > > > An outdated and potentially vulnerable software in the latest OpenBSD > > 7.4-stable? > > > > I must really have been missing something here... > > Just a few links: > > https://github.com/openbsd/ports/blob/master/mail/postfix/snapshot/Makefile > http://ftp.porcupine.org/mirrors/postfix-release/index.html#experimental > https://www.postfix.org/smtp-smuggling.html > > -- > Herbert > >
Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
On Sat, Feb 03, 2024 at 09:19:47AM +0300, Mark wrote: > An experimental, unstable package in packages-stable? > > An outdated and potentially vulnerable software in the latest OpenBSD > 7.4-stable? > > I must really have been missing something here... Just a few links: https://github.com/openbsd/ports/blob/master/mail/postfix/snapshot/Makefile http://ftp.porcupine.org/mirrors/postfix-release/index.html#experimental https://www.postfix.org/smtp-smuggling.html -- Herbert
Unable to connect to WiFi on new OpenBSD installation
Hello, I installed OpenBSD on a T490. I can't connect to WiFi. I'm not sure if it's because the device is not supported. In the dmesg I see the following line: "Intel Wi-Fi 6 AX201" rev 0x00 at pci0 dev 20 function 3 not configured I ran fw_update, and I can see the iwx-* files under /etc/firmware. I'm not sure what to do next. The installed OpenBSD version (from uname -a) is 7.4 GENERIC.MP#2 i386.
Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
An experimental, unstable package in packages-stable? An outdated and potentially vulnerable software in the latest OpenBSD 7.4-stable? I must really have been missing something here... Herbert J. Skuhra , 3 Şub 2024 Cmt, 09:04 tarihinde şunu yazdı: > On Fri, Feb 02, 2024 at 08:44:45PM -0600, Brian Conway wrote: > > On Fri, Feb 2, 2024, at 6:44 PM, Herbert J. Skuhra wrote: > > > On Sat, Feb 03, 2024 at 03:00:10AM +0300, Mark wrote: > > >> Hi. > > >> > > >> It seems that the recent Postfix update under 7.4-amd64, > > >> (package: postfix-3.8.20221007p12-sasl2-mysql) breaks TLS connections, > > >> coming from Gmail servers, throwing a TLS library problem. > > >> > > >> Here's the log output; > > >> > > >> postfix/smtpd[32879]: connect from mail-yw1-f178.google.com > [209.85.128.178] > > >> > > >> postfix/smtpd[7374]: Trusted TLS connection established from > > >> mail-lf1-f45.google.com[209.85.167.45]: TLSv1.3 > > >> with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 > > >> server-signature ECDSA (prime256v1) server-digest SHA256 > client-signature > > >> RSA-PSS (2048 bits) client-digest SHA256 > > >> > > >> postfix/smtpd[7374]: warning: TLS library problem: error:0A000126:SSL > > >> routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:308: > > >> postfix/smtpd[7374]: lost connection after STARTTLS from > > >> mail-lf1-f45.google.com[209.85.167.45] > > >> postfix/smtpd[7374]: disconnect from mail-lf1-f45.google.com > [209.85.167.45] > > >> ehlo=1 starttls=1 commands=2 > > >> > > >> Before updating the package, I had postfix-3.8.20221007p11, and it > had no > > >> such problem. > > > > > > Why do you run such an outdated postfix snapshot? > > > > That is the latest version that is supported/available in > packages-stable: > > > > https://cdn.openbsd.org/pub/OpenBSD/7.4/packages-stable/amd64/ > > Yeah, sadly! But no reason to install/run outdated and potentially > vulnerable server software. :-) > > Postfix 3.8.20221007 is an old development snapshot (experimental!). It > should be either updated or removed. Latest version as of today is > postfix-3.9-20240129. There are also updates available for postfix35 > (3.5.24) and postfix (3.7.10/3.8.5). > > -- > Herbert > >
Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
On Fri, Feb 02, 2024 at 08:44:45PM -0600, Brian Conway wrote: > On Fri, Feb 2, 2024, at 6:44 PM, Herbert J. Skuhra wrote: > > On Sat, Feb 03, 2024 at 03:00:10AM +0300, Mark wrote: > >> Hi. > >> > >> It seems that the recent Postfix update under 7.4-amd64, > >> (package: postfix-3.8.20221007p12-sasl2-mysql) breaks TLS connections, > >> coming from Gmail servers, throwing a TLS library problem. > >> > >> Here's the log output; > >> > >> postfix/smtpd[32879]: connect from mail-yw1-f178.google.com[209.85.128.178] > >> > >> postfix/smtpd[7374]: Trusted TLS connection established from > >> mail-lf1-f45.google.com[209.85.167.45]: TLSv1.3 > >> with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 > >> server-signature ECDSA (prime256v1) server-digest SHA256 client-signature > >> RSA-PSS (2048 bits) client-digest SHA256 > >> > >> postfix/smtpd[7374]: warning: TLS library problem: error:0A000126:SSL > >> routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:308: > >> postfix/smtpd[7374]: lost connection after STARTTLS from > >> mail-lf1-f45.google.com[209.85.167.45] > >> postfix/smtpd[7374]: disconnect from mail-lf1-f45.google.com[209.85.167.45] > >> ehlo=1 starttls=1 commands=2 > >> > >> Before updating the package, I had postfix-3.8.20221007p11, and it had no > >> such problem. > > > > Why do you run such an outdated postfix snapshot? > > That is the latest version that is supported/available in packages-stable: > > https://cdn.openbsd.org/pub/OpenBSD/7.4/packages-stable/amd64/ Yeah, sadly! But no reason to install/run outdated and potentially vulnerable server software. :-) Postfix 3.8.20221007 is an old development snapshot (experimental!). It should be either updated or removed. Latest version as of today is postfix-3.9-20240129. There are also updates available for postfix35 (3.5.24) and postfix (3.7.10/3.8.5). -- Herbert
Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
On Fri, Feb 2, 2024, at 6:44 PM, Herbert J. Skuhra wrote: > On Sat, Feb 03, 2024 at 03:00:10AM +0300, Mark wrote: >> Hi. >> >> It seems that the recent Postfix update under 7.4-amd64, >> (package: postfix-3.8.20221007p12-sasl2-mysql) breaks TLS connections, >> coming from Gmail servers, throwing a TLS library problem. >> >> Here's the log output; >> >> postfix/smtpd[32879]: connect from mail-yw1-f178.google.com[209.85.128.178] >> >> postfix/smtpd[7374]: Trusted TLS connection established from >> mail-lf1-f45.google.com[209.85.167.45]: TLSv1.3 >> with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 >> server-signature ECDSA (prime256v1) server-digest SHA256 client-signature >> RSA-PSS (2048 bits) client-digest SHA256 >> >> postfix/smtpd[7374]: warning: TLS library problem: error:0A000126:SSL >> routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:308: >> postfix/smtpd[7374]: lost connection after STARTTLS from >> mail-lf1-f45.google.com[209.85.167.45] >> postfix/smtpd[7374]: disconnect from mail-lf1-f45.google.com[209.85.167.45] >> ehlo=1 starttls=1 commands=2 >> >> Before updating the package, I had postfix-3.8.20221007p11, and it had no >> such problem. > > Why do you run such an outdated postfix snapshot? That is the latest version that is supported/available in packages-stable: https://cdn.openbsd.org/pub/OpenBSD/7.4/packages-stable/amd64/ Brian Conway Owner RCE Software, LLC
Re: New postfix-3.8.20221007p12 broken TLS for Gmail servers?
On Sat, Feb 03, 2024 at 03:00:10AM +0300, Mark wrote: > Hi. > > It seems that the recent Postfix update under 7.4-amd64, > (package: postfix-3.8.20221007p12-sasl2-mysql) breaks TLS connections, > coming from Gmail servers, throwing a TLS library problem. > > Here's the log output; > > postfix/smtpd[32879]: connect from mail-yw1-f178.google.com[209.85.128.178] > > postfix/smtpd[7374]: Trusted TLS connection established from > mail-lf1-f45.google.com[209.85.167.45]: TLSv1.3 > with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 > server-signature ECDSA (prime256v1) server-digest SHA256 client-signature > RSA-PSS (2048 bits) client-digest SHA256 > > postfix/smtpd[7374]: warning: TLS library problem: error:0A000126:SSL > routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:308: > postfix/smtpd[7374]: lost connection after STARTTLS from > mail-lf1-f45.google.com[209.85.167.45] > postfix/smtpd[7374]: disconnect from mail-lf1-f45.google.com[209.85.167.45] > ehlo=1 starttls=1 commands=2 > > Before updating the package, I had postfix-3.8.20221007p11, and it had no > such problem. Why do you run such an outdated postfix snapshot? -- Herbert
New postfix-3.8.20221007p12 broken TLS for Gmail servers?
Hi. It seems that the recent Postfix update under 7.4-amd64, (package: postfix-3.8.20221007p12-sasl2-mysql) breaks TLS connections, coming from Gmail servers, throwing a TLS library problem. Here's the log output; postfix/smtpd[32879]: connect from mail-yw1-f178.google.com[209.85.128.178] postfix/smtpd[7374]: Trusted TLS connection established from mail-lf1-f45.google.com[209.85.167.45]: TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256 postfix/smtpd[7374]: warning: TLS library problem: error:0A000126:SSL routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:308: postfix/smtpd[7374]: lost connection after STARTTLS from mail-lf1-f45.google.com[209.85.167.45] postfix/smtpd[7374]: disconnect from mail-lf1-f45.google.com[209.85.167.45] ehlo=1 starttls=1 commands=2 Before updating the package, I had postfix-3.8.20221007p11, and it had no such problem. Any idea? Regards. Mark.
Re: how to play bytebeat on openbsd?
back when i used to mess with these, i frequently used `sox` to play the 8-bit samples. it can do the sample conversion for you to whatever the system needs. On Fri, Feb 2, 2024 at 11:08 AM Omar Polo wrote: > > On 2024/02/02 18:41:46 +, beecdadd...@danwin1210.de wrote: > > hello > > > > I've tried for hours to play bytebeat as everyone else > > > > I cannot find anything on the entire internet > > > > all I got is `cat a.out >> /dev/speaker)` as root.. a.out is compiled code > > , a > > loop and `putchar(t*((t>>12|t>>8)&63>>4));`.. this doesn't sound nearly > > the > > same as it does to other people > > it's also slow, not fast > > I don't think it makes sense to feed speaker(4) with an executable code. > > Haven't seen the code, but based on your description I guess it should > be more like > > $ ./a.out | doas tee /dev/speaker > > or at least that's my guess, my crystall ball don't always works > correctly. >
Re: Problem sound
On 2024-02-02, Manfred Koch wrote: > Hi all, > > I'm a newbie in openbsd. I use the xfce Desktop but without sound. I > have enabled sndiod_enable=YES > in /etc/rc.conf.local. Further I tried pulseaudio without success. > What's about dbus-daemon? > > Perhaps you can help me, to find a solution? If you're trying to use audio over HDMI, AFAIK that won't work, you'll need to use line out or headphone. Otherwise: send a dmesg, it might give more clues. (Just paste the complete dmesg straight into an email). > Are you knowing a mailinglist for newbies in openbsd? misc@ is just fine for this. -- Please keep replies on the mailing list.
Re: how to play bytebeat on openbsd?
On 2024/02/02 18:41:46 +, beecdadd...@danwin1210.de wrote: > hello > > I've tried for hours to play bytebeat as everyone else > > I cannot find anything on the entire internet > > all I got is `cat a.out >> /dev/speaker)` as root.. a.out is compiled code , a > loop and `putchar(t*((t>>12|t>>8)&63>>4));`.. this doesn't sound nearly the > same as it does to other people > it's also slow, not fast I don't think it makes sense to feed speaker(4) with an executable code. Haven't seen the code, but based on your description I guess it should be more like $ ./a.out | doas tee /dev/speaker or at least that's my guess, my crystall ball don't always works correctly.
Re: how to play bytebeat on openbsd?
there is this video with some C code https://youtube.com/watch?v=GtQdIYUtAHg these are some examples On Fri, February 2, 2024 6:41 pm, beecdadd...@danwin1210.de wrote: > hello > > I've tried for hours to play bytebeat as everyone else > > > I cannot find anything on the entire internet > > > all I got is `cat a.out >> /dev/speaker)` as root.. a.out is compiled code , > a loop and `putchar(t*((t>>12|t>>8)&63>>4));`.. this doesn't sound nearly > the same as it does to other people it's also slow, not fast > > man speaker doesn't help much aucat also doesn't seem to be for this > > do I need PCM? All videos I found people writting in C++, a bytebeat player > was for Windows > > please help > >
how to play bytebeat on openbsd?
hello I've tried for hours to play bytebeat as everyone else I cannot find anything on the entire internet all I got is `cat a.out >> /dev/speaker)` as root.. a.out is compiled code , a loop and `putchar(t*((t>>12|t>>8)&63>>4));`.. this doesn't sound nearly the same as it does to other people it's also slow, not fast man speaker doesn't help much aucat also doesn't seem to be for this do I need PCM? All videos I found people writting in C++, a bytebeat player was for Windows please help
Re: OT: Against one more IT convention to defend "proprietary stuff"
Correct, the problem is that one. And not adding more hilarious stuff to the fire could be awesome for most. Feb 2, 2024 10:20:22 Louis Brauer : >> what do you think? > > I think that this is a mailing list about OpenBSD, not US politics. But I may > be mistaken. > N0\/\/@r€Z > -- > /\/\@rk€T
Re: Problem sound
El Fri, 2 Feb 2024 14:43:59 +0100 Manfred Koch escribió: > Hi all, > > I'm a newbie in openbsd. I use the xfce Desktop but without sound. I > have enabled sndiod_enable=YES > in /etc/rc.conf.local. Further I tried pulseaudio without success. > What's about dbus-daemon? > > Perhaps you can help me, to find a solution? > Are you knowing a mailinglist for newbies in openbsd? > > I would appreciate for any tips. > > Thank you > > Manfred Koch > Hi, welcome! First, you don´t need pulseaudio for audio work, sndiod is enough. Give a look to FAQ for audio problems https://www.openbsd.org/faq/faq13.html#confaudio -- * Dios en su cielo, todo bien en la Tierra
Re: Problem sound
Did you try to turn up the volume? Kyle > On Feb 2, 2024, at 9:03 AM, Manfred Koch wrote: > > Hi all, > > I'm a newbie in openbsd. I use the xfce Desktop but without sound. I have > enabled sndiod_enable=YES > in /etc/rc.conf.local. Further I tried pulseaudio without success. What's > about dbus-daemon? > > Perhaps you can help me, to find a solution? > Are you knowing a mailinglist for newbies in openbsd? > > I would appreciate for any tips. > > Thank you > > Manfred Koch >
Problem sound
Hi all, I'm a newbie in openbsd. I use the xfce Desktop but without sound. I have enabled sndiod_enable=YES in /etc/rc.conf.local. Further I tried pulseaudio without success. What's about dbus-daemon? Perhaps you can help me, to find a solution? Are you knowing a mailinglist for newbies in openbsd? I would appreciate for any tips. Thank you Manfred Koch
Re: HUNSN routers - N100 I226-V
Kapetanakis Giannis [bil...@edu.physics.uoc.gr] wrote: > Has anyone tried these HUNSN mini pcs/routers with multiple interfaces? > > I'm thinking of getting one for home routing. Does it work with OpenBSD? > (dmesg?) > > Performance? Will it route/firewall at 1Gbps? Intel N100 seems to be low on > TDP and gives numbers. > > Any problems with I226? I've read about issues with I225 in the past. > Some of the N100 boards are missing options in the BIOS like default power-on from what I've read. I have a couple and my complaint is the build quality is poor. I got 8 units and at least 1 is questionable. USB ports blink on and off when you breathe on it and probably more, i haven't spent much time yet. I don't know if these are the same as the HUNSN brand, just some shitty manufacturer, or something else. I haven't even looked to see if the BIOS has power-on default yet. I don't have a ton of experience with them but my early and late i225 boards don't seem to have the problems under if_igc that they have under Windows where the chip isn't initialized, shuts off, whatever. I had nothing but trouble with cards based on the early realtek 2.5gbps chips, despite kevlo's attempts to improve if_rge. I ended up throwing them away before his last round of fixes. My i225 and i226 are consistently good for whatever that's worth. I'd expect i226 to be ok. Chris
Re: vmd silently exits (after 7.4 upgrade)
Dave Voutila writes: > "Piotr K. Isajew" writes: > >> Hello, >> >> I'm observing this on one of my machines (which I seldom use >> nowadays) after upgrading it to 7.4. The machine had existing >> vm.conf setup which worked for me in the past. >> >> Now "rcctl start vmd" reports: >> vmd(ok) >> >> but just after that executing "vmctl status" gives: >> vmctl: connect: /var/run/vmd.sock: Connection refused >> >> and there is no vmd process running. >> >> When I try to start vmd from command line, it generates some >> output, but it is not really helpful in determining what could be >> the problem: >> >> /usr/sbin/vmd -d -v -v -v -v -v -v -v -v -v -v -v >> vmd: startup >> vmd: vm_register: registering vm 1 >> vmd: /etc/vm.conf:18: vm "lindev" registered (disabled) >> vmd: vmd_configure: setting staggered start configuration to parallelism: 4 >> and delay: 30 >> vmd: vmd_configure: starting vms in staggered fashion >> vmd: start_vm_batch: starting batch of 4 vms >> vmd: start_vm_batch: not starting vm lindev (disabled) >> vmd: start_vm_batch: done starting vms >> vmd: vmd: getgrnam > > Run sysmerge. You're missing the new _vmd group introduced in 7.4: > > $ grep vmd /etc/group > _vmd:*:107: > err...also check the agentx group. That is probably the actual missing group in this case: $ grep agentx /etc/group _agentx:*:92: >> vmd: exiting >> control: config_getconfig: control retrieving config >> control: control exiting, pid 33268 >> # priv: config_getconfig: priv retrieving config >> priv: priv exiting, pid 1161 >> vmm: config_getconfig: vmm retrieving config >> vmm: vmm exiting, pid 48824 >> >> >> dmesg excerpt >> OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023 >> >> r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> cpu0: Intel(R) Xeon(R) CPU E31225 @ 3.10GHz, 3093.12 MHz, 06-2a-07, patch >> 002f >> 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN >> >> cpu0: using VERW MDS workaround (except on vmm entry) >> vmm0 at mainbus0: VMX/EPT
dhcpcd not obtaining ipv6 /48
Hello, I have an edgerouter lite 3 running octeon for the past few years. The connection is dual-stack. On the ipv6 side, there's two prefixes: for the ND side, a /64 let's call it 2a02:8011: for the DP (delegation prefix) it's a /48 let's call it 2a02:8010. v6 IPs from the /48 are distributed to the DMZ. on the edgerouter: cnmac2 is not used cnmac0 points to the dmz and has ipv4 assigned manually pppoe0 is on cnmac1 and it always has, as expected, ipv6 from the ND prefix. cnmac1 points to the dmz and has ipv4 and, normally, ipv6, and the ipv6 would be from the PD prefix. This *used* to work and stopped working sometime while at 7.3. It's at 7.4 now. Sometimes it would stop working and a reboot would fix it. I'm unsure if it's a misconfiguration at my end or if it's an ISP problem. The problem persists even if pf is stopped. Please can anyone advise? hostname.pppoe0 === inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \ pppoedev cnmac1 authproto chap \ authname 'REDACTED' authkey 'REDACTED' up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 inet6 eui64 !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 ### hostname.cnmac1 === mtu 1508 inet6 autoconf up ### hostname.cnmac0 === inet my.real.ipv4.router.ip 255.255.255.248 NONE ### The problem is cnmac1 isn't getting its DHCP-DP /48 as expected. It does get an ipv6 but it's inet6 fe80::f29f:c2ff:fe10:488f%cnmac1 prefixlen 64 scopeid 0x2 and that's it. Additionally: Fri Feb 02 14:29:27 root@axs /etc # rcctl stop dhcpcd dhcpcd(ok) Fri Feb 02 14:30:18 root@axs /etc # rcctl start dhcpcd dhcpcd(timeout) Fri Feb 02 14:31:00 root@axs /etc # rcctl check dhcpcd dhcpcd(ok) Fri Feb 02 14:32:13 root@axs /etc # rcctl restart dhcpcd dhcpcd(ok) dhcpcd(timeout) Here's /etc/dhcpcd.conf ### Fri Feb 02 14:32:58 root@axs /etc # cat /etc/dhcpcd.conf ipv6only noipv6rs duid persistent option rapid_commit require dhcp_server_identifier script "" allowinterfaces pppoe0 cnmac0 cnmac1 interface pppoe0 ipv6rs ia_na 1 ia_pd 2/::48 cnmac0/1 ### dmesg [ using 762280 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-2023 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 7.4 (GENERIC.MP) #1382: Tue Oct 10 09:43:29 MDT 2023 dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC.MP real mem = 536870912 (512MB) avail mem = 520994816 (496MB) random: good seed from bootblocks mainbus0 at root: board 20002 rev 2.18, model CN3xxx/CN5xxx cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu0: cache L1-I 32KB 4 way D 16KB 64 way, L2 128KB 8 way cpu1 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu1: cache L1-I 32KB 4 way D 16KB 64 way, L2 128KB 8 way clock0 at mainbus0: int 5 octcrypto0 at mainbus0 iobus0 at mainbus0 simplebus0 at iobus0: "soc" octciu0 at simplebus0 octsmi0 at simplebus0 octpip0 at simplebus0 octgmx0 at octpip0 interface 0 cnmac0 at octgmx0: port 0 RGMII, address f0:9f:c2:10:48:8e atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2 cnmac1 at octgmx0: port 1 RGMII, address f0:9f:c2:10:48:8f atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2 cnmac2 at octgmx0: port 2 RGMII, address f0:9f:c2:10:48:90 atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2 com0 at simplebus0: ns16550a, 64 byte fifo com0: console dwctwo0 at iobus0 base 0x118006800 irq 56 usb0 at dwctwo0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev 2.00/1.00 addr 1 octrng0 at iobus0 base 0x14000 irq 0 umass0 at uhub0 port 1 configuration 1 interface 0 "USB SanDisk 3.2Gen1" rev 2.10/1.00 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: removable serial.078155838107b4280bcc sd0: 29340MB, 512 bytes/sector, 60088320 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on sd0a (d02ce061c45edca4.a) swap on sd0b dump on sd0b WARNING: CHECK AND RESET THE DATE! ### Thanks in advance for any assistance --
Re: vmd silently exits (after 7.4 upgrade)
"Piotr K. Isajew" writes: > Hello, > > I'm observing this on one of my machines (which I seldom use > nowadays) after upgrading it to 7.4. The machine had existing > vm.conf setup which worked for me in the past. > > Now "rcctl start vmd" reports: > vmd(ok) > > but just after that executing "vmctl status" gives: > vmctl: connect: /var/run/vmd.sock: Connection refused > > and there is no vmd process running. > > When I try to start vmd from command line, it generates some > output, but it is not really helpful in determining what could be > the problem: > > /usr/sbin/vmd -d -v -v -v -v -v -v -v -v -v -v -v > vmd: startup > vmd: vm_register: registering vm 1 > vmd: /etc/vm.conf:18: vm "lindev" registered (disabled) > vmd: vmd_configure: setting staggered start configuration to parallelism: 4 > and delay: 30 > vmd: vmd_configure: starting vms in staggered fashion > vmd: start_vm_batch: starting batch of 4 vms > vmd: start_vm_batch: not starting vm lindev (disabled) > vmd: start_vm_batch: done starting vms > vmd: vmd: getgrnam Run sysmerge. You're missing the new _vmd group introduced in 7.4: $ grep vmd /etc/group _vmd:*:107: > vmd: exiting > control: config_getconfig: control retrieving config > control: control exiting, pid 33268 > # priv: config_getconfig: priv retrieving config > priv: priv exiting, pid 1161 > vmm: config_getconfig: vmm retrieving config > vmm: vmm exiting, pid 48824 > > > dmesg excerpt > OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023 > > r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > cpu0: Intel(R) Xeon(R) CPU E31225 @ 3.10GHz, 3093.12 MHz, 06-2a-07, patch > 002f > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > > cpu0: using VERW MDS workaround (except on vmm entry) > vmm0 at mainbus0: VMX/EPT
Re: OT: Against one more IT convention to defend "proprietary stuff"
> what do you think? I think that this is a mailing list about OpenBSD, not US politics. But I may be mistaken. Louis
OT: Against one more IT convention to defend "proprietary stuff"
Hello, Couple of stuff to consider around the american proprietary software venture & dream: 1) as everyone know "proprietary" is globally loosing appeal and streaving selling from cheap apps to discounts on support timeslots 2) in a world where western warez are banned from a decade and westerners CEOs doubts and fear selling any new tech addressed to kill "The Software Industry" 3) and when eastern "slaves" invest always more money and time in getting knowledge by the american universities 4) and westerners (including CIA yuppies) are passing lots of time on social networks and lux beeches, 5) at a time when professors are still teaching to our youngsters about the famous one free market. Frankly, spending more time in conventions on the american software economical crisis sounds overwhelming, what do you think? > N0\/\/@r€Z > -- > /\/\@rk€T
Re: vmd silently exits (after 7.4 upgrade)
On Fri, Feb 02, 2024 at 08:28:42AM +0100, Piotr K. Isajew wrote: > Hello, > > I'm observing this on one of my machines (which I seldom use > nowadays) after upgrading it to 7.4. The machine had existing > vm.conf setup which worked for me in the past. > > Now "rcctl start vmd" reports: > vmd(ok) > > but just after that executing "vmctl status" gives: > vmctl: connect: /var/run/vmd.sock: Connection refused > > and there is no vmd process running. > > When I try to start vmd from command line, it generates some > output, but it is not really helpful in determining what could be > the problem: > > /usr/sbin/vmd -d -v -v -v -v -v -v -v -v -v -v -v > vmd: startup > vmd: vm_register: registering vm 1 > vmd: /etc/vm.conf:18: vm "lindev" registered (disabled) > vmd: vmd_configure: setting staggered start configuration to parallelism: 4 > and delay: 30 > vmd: vmd_configure: starting vms in staggered fashion > vmd: start_vm_batch: starting batch of 4 vms > vmd: start_vm_batch: not starting vm lindev (disabled) > vmd: start_vm_batch: done starting vms > vmd: vmd: getgrnam caused by missing _agentx group. _agentx:*:92: -ml > vmd: exiting > control: config_getconfig: control retrieving config > control: control exiting, pid 33268 > # priv: config_getconfig: priv retrieving config > priv: priv exiting, pid 1161 > vmm: config_getconfig: vmm retrieving config > vmm: vmm exiting, pid 48824 > > > dmesg excerpt > OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023 > > r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > cpu0: Intel(R) Xeon(R) CPU E31225 @ 3.10GHz, 3093.12 MHz, 06-2a-07, patch > 002f > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > > cpu0: using VERW MDS workaround (except on vmm entry) > vmm0 at mainbus0: VMX/EPT >
