Re: Regression (or misconfig on my side?) after OpenOSPFd upgrade (OpenBSD 7.3 -> 7.4)

On 2023-11-07, Laurent CARON wrote: > Hi, > > After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies > using a password are not coming up with the following in /var/log/messages: > > ospfd[55040]: recv_packet: authentication error, neighbor ID X.X.X.X > interface vlanXX > > After

Re: Regression (or misconfig on my side?) after OpenOSPFd upgrade (OpenBSD 7.3 -> 7.4)

Le 07/11/2023 à 10:59, Claudio Jeker a écrit : Ugh. My bad. I forgot that iface->auth_key is not really a string. So the code setting the auth_key would copy too much if you use a password with 8 chars. Using a password with 7 or less chars works fine. As a result of this overflow the

Re: Regression (or misconfig on my side?) after OpenOSPFd upgrade (OpenBSD 7.3 -> 7.4)

On Tue, Nov 07, 2023 at 10:59:48AM +0100, Claudio Jeker wrote: > On Tue, Nov 07, 2023 at 08:21:16AM +0100, Laurent CARON wrote: > > Hi, > > > > After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies using a > > password are not coming up with the following in /var/log/messages: > >

Re: Regression (or misconfig on my side?) after OpenOSPFd upgrade (OpenBSD 7.3 -> 7.4)

On Tue, Nov 07, 2023 at 08:21:16AM +0100, Laurent CARON wrote: > Hi, > > After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies using a > password are not coming up with the following in /var/log/messages: > > ospfd[55040]: recv_packet: authentication error, neighbor ID X.X.X.X >

Regression (or misconfig on my side?) after OpenOSPFd upgrade (OpenBSD 7.3 -> 7.4)

Hi, After upgrading a 7.3 to 7.4 OpenBSD box, I noticed OSPF adjacencies using a password are not coming up with the following in /var/log/messages: ospfd[55040]: recv_packet: authentication error, neighbor ID X.X.X.X interface vlanXX After removing the authentication, I was able to get

Re: upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

On 2016-04-28, Ultramedia Libertad wrote: > with this file that comes by default it worked perfectly, I think the > login.conf file does not work without the first line or comments, or I had > some syntax error'll never know something like that happened to someone in > this

Re: upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

gt;>> > >>> > no. NOTHING NEW here. it has always been complete your base >>> system >>> > upgrade, THEN upgrade packages. sysmerge upgrades the base system. >>> > >>> > AFTER the base system is upgraded, THEN you

Re: upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

On 04/21/16 21:25, Ultramedia Libertad wrote: > hello > > I am upgrade OpenBSD 5.8 to 5.9 and after to reboot > > i have follow errors in remote console : ...[deleting big block of blank lines]... > *init: daemon: unknown class (failed)syslogdsu: daemon: unknown class

Re: upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

On 22.04.2016 03:25, Ultramedia Libertad wrote: > hello > > I am upgrade OpenBSD 5.8 to 5.9 and after to reboot > > i have follow errors in remote console : > > > > > > > > > > > > > > > > > *init: daemon: unknown

upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

hello I am upgrade OpenBSD 5.8 to 5.9 and after to reboot i have follow errors in remote console : *init: daemon: unknown class (failed)syslogdsu: daemon: unknown class (failed)pflogdsu: daemon: unknown class (failed)ntpdsu: daemon: unknown class (failed)starting RPC daemons

Re: upgrade openbsd partition cipher

MAKEDEV now works, thanks but I can not ride my encrypted partition to upgrade openbsd bioctl: could not open /dev/sd3a: device not configured 2015-06-18 15:31 GMT-05:00 Daniel Gillen gillen.dan...@gmail.com: On 18.06.2015 22:24, Ultramedia Libertad wrote: cd /dev MAKEDEV sd3 try: cd /dev

Re: upgrade openbsd partition cipher

What do you see when you do: disklabel /dev/sd3 Thanks, Bryan On Thu, Jun 18, 2015 at 4:35 PM, Ultramedia Libertad meloa...@gmail.com wrote: MAKEDEV now works, thanks but I can not ride my encrypted partition to upgrade openbsd bioctl: could not open /dev/sd3a: device not configured

upgrade openbsd partition cipher

I need help. I have an encrypted Particio and I'm trying to upgrade from my console kvm. But I get the following errors Welcome to the OpenBSD/i386 5.7 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s cd /dev MAKEDEV sd3 sh: MAKEDEV: not found bioctl -c C -l /dev/sd3a

Re: upgrade openbsd partition cipher

On 18.06.2015 22:24, Ultramedia Libertad wrote: cd /dev MAKEDEV sd3 try: cd /dev ./MAKEDEV sd3

Re: upgrade OpenBSD

On Mon, Dec 19, 2011 at 10:34:12PM -0500, Nick Holland wrote: On 12/19/11 15:55, Lars Kotthoff wrote: Hi list, the OpenBSD upgrade pages carry a warning at the top Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases.

upgrade OpenBSD

Hi list, the OpenBSD upgrade pages carry a warning at the top Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases. What's the reason for this warning? I've had a look at the upgrade steps and the only thing that seems to assume a

Re: upgrade OpenBSD

On 12/19/11 15:55, Lars Kotthoff wrote: Hi list, the OpenBSD upgrade pages carry a warning at the top Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases. What's the reason for this warning? I've had a look at the upgrade steps and

Re: upgrade OpenBSD

* Lars Kotthoff li...@larsko.org [2011-12-19 21:57]: the OpenBSD upgrade pages carry a warning at the top Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases. What's the reason for this warning? That's simple: from the previous

Re: upgrade OpenBSD

On 12/19/11 15:55, Lars Kotthoff wrote: Hi list, the OpenBSD upgrade pages carry a warning at the top Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases. What's the reason for this warning? I've had a look at the upgrade

a dual-boot way to upgrade openbsd

Hallo! I would be thankful if somebody comments on the following sequence to upgrade OpenBSD system. The main purpose is to make an upgrade with as little downtime as possible and to have a way to return to the last known working state. Essentially it involves creating temporary dual-boot

Re: a dual-boot way to upgrade openbsd

Imre Oolberg wrote: Hallo! I would be thankful if somebody comments on the following sequence to upgrade OpenBSD system. The main purpose is to make an upgrade with as little downtime as possible and to have a way to return to the last known working state. Essentially it involves creating