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 r
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 checksum
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:
> >
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
> in
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 adj
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 thread the which along
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 can do your pkg_add -u.
>>> > Think about
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
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
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
What do you see when you do:
disklabel /dev/sd3
Thanks,
Bryan
On Thu, Jun 18, 2015 at 4:35 PM, Ultramedia Libertad 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
&g
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 :
> On 18.06.2015 22:24, Ultramedia Libertad wrote:
>> cd /dev && MAKEDEV sd3
>
> try: c
On 18.06.2015 22:24, Ultramedia Libertad wrote:
> cd /dev && MAKEDEV sd3
try: cd /dev && ./MAKEDEV sd3
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
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
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 up
* Lars Kotthoff [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 release
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 an
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 cer
On Wed, Feb 13, 2008 at 10:56:42PM +0200, Imre Oolberg wrote:
> Hi!
>
> Thank you for your answer but let me put more clearly the question i had.
>
> I have two fdisk partitions, this disk has quite ugly layout but i just
> tried things out (it had at times four OpenBSD instances :)
>
> # fdisk
Hi!
Thank you for your answer but let me put more clearly the question i had.
I have two fdisk partitions, this disk has quite ugly layout but i just
tried things out (it had at times four OpenBSD instances :)
# fdisk sd0
Disk: sd0 geometry: 1044/255/63 [16777216 Sectors]
Offset: 0
Imre Oolberg wrote:
Hallo!
I experimented with OpenBSD 4.2 on i386 platform, made two fdisk
partitions on the same disk, into each of them OpenBSD disklabel,
installed grub from packages and can successfully dualboot.
But i cant figure out if there is a way to access fdisk partition's
diskl
Hallo!
I experimented with OpenBSD 4.2 on i386 platform, made two fdisk
partitions on the same disk, into each of them OpenBSD disklabel,
installed grub from packages and can successfully dualboot.
But i cant figure out if there is a way to access fdisk partition's
disklabel partitions while
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
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
25 matches
Mail list logo
