On 2024-05-16 09:42 -04, Dave Voutila wrote:
> Johan Huldtgren writes:
>
>> hello,
>>
>> On 2024-05-16 8:14, Dave Voutila wrote:
>>>
>>> Johan Huldtgren writes:
>> $ doas cat /etc/hostname.vio0
>> inet autoconf
>>
>> # /bin/sh /etc/netstart vio0
>> ifconfig: autoconf not allowed for this AF
>>
On 2024-05-14 13:18 +10, Jonathan Gray wrote:
> hibernate does DVACT_QUIESCE/DVACT_SUSPEND from
> diskconf()/hibernate_resume() before config_process_deferred_mountroot()
> attaches most of the driver. So don't attempt to do anything.
>
> Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_drv.c
>
OCR'ed and edited a bit, there might be mistakes.
Picture: https://dump.sha256.net/dump/unhibernating_panic.jpg
unhibernating & block 50329599 Length 243MB
uvm_fault(0x826b2860, 0x38, 0, 1) →> e
kernel: page fault trap, code=0
Stopped at ttm_resource_manager_evict_all+0x5e: cmpq %rbx,
Committed, thanks!
On 2024-02-24 03:18 +01, Einfach Jemand wrote:
> Hiya,
>
> when working with my OpenBSD-Laptop (running OpenBSD 7.4-current
> (GENERIC.MP) #1667: Wed Feb 7 20:09:35 MST 2024) using unwind in a
> large customer network and having problems resolving some PTRs from
>
On 2024-01-15 09:44 -07, Todd C. Miller wrote:
> On Mon, 15 Jan 2024 17:43:12 +0100, Florian Obser wrote:
>
>> oops, this seems to be better.
>
> I have the same diff. OK millert@
>
> - todd
actually we also have AI_FQDN and localhost is not a FQDN.
Let's just go wi
On 2024-01-15 09:03 -07, Todd C. Miller wrote:
> This looks like fallout from the changes in localhost handling in
> the resolver. It seems strange for getaddrinfo() to return success
> but not set res->ai_canonname when AI_CANONNAME is specified.
>
> - todd
>
oops, this seems to be better.
On 2024-01-13 17:10 UTC, Klemens Nanni wrote:
> On Sat, Jan 13, 2024 at 05:48:43PM +0100, Florian Obser wrote:
>> I think we need to improve debug logging a bit, but I'm pretty sure you
>> are hitting
>>
>> } else
>> checked_resolver-&
On 2024-01-13 15:57 UTC, Klemens Nanni wrote:
> On Sat, Jan 13, 2024 at 04:29:55PM +0100, Florian Obser wrote:
>> On 2024-01-13 01:13 UTC, Klemens Nanni wrote:
>> > The last unwind.conf(5) EXAMPLE does not work for me unless I remove all
>> > three of "DoT",
On 2024-01-13 01:13 UTC, Klemens Nanni wrote:
> The last unwind.conf(5) EXAMPLE does not work for me unless I remove all
> three of "DoT", "oDoT-forwarder" and "forwarder" from preferences; moving
> them to the end or "autoconf" to the front does not work.
What is "unwindctl status" showing?
Nedvedicky wrote:
>> > > Hello,
>> > >
>> > > On Sun, Sep 03, 2023 at 09:26:29PM +0200, Florian Obser wrote:
>> > > > FYI, I'm not using sloppy, and I don't have a network with asymmetric
>> > > > routing
>> > > > at the moment.
Nedvedicky
wrote:
>Hello,
>
>On Sun, Sep 03, 2023 at 06:29:51PM +0200, Alexander Bluhm wrote:
>> On Sun, Sep 03, 2023 at 06:17:12PM +0200, Florian Obser wrote:
>> > On 2023-09-03 18:13 +02, Alexander Bluhm wrote:
>> > > On Sun, Sep 03, 2023 at 05:59:18PM +0200, Alex
On 2023-09-03 18:13 +02, Alexander Bluhm wrote:
> On Sun, Sep 03, 2023 at 05:59:18PM +0200, Alexandr Nedvedicky wrote:
>> Hello,
>>
>> On Sun, Sep 03, 2023 at 05:10:02PM +0200, Alexander Bluhm wrote:
>> > On Sun, Sep 03, 2023 at 04:12:35AM +0200, Alexandr Nedvedicky wrote:
>> > > in my opinion
looks reasonable.
OK florian
On 2023-07-11 21:13 +02, Theo Buehler wrote:
> On Tue, Jul 11, 2023 at 08:35:31PM +0200, Theo Buehler wrote:
>> On Tue, Jul 11, 2023 at 02:32:48PM +0200, Theo Buehler wrote:
>> > On Tue, Jul 11, 2023 at 11:48:57AM +0100, Stuart Henderson wrote:
>> > > I ran into a
Yes, good idea, let's ship 7.4 with the leak!
I'm getting a bit annoyed with unlocking this and rewriting that and then
complete silence when shit breaks.
On 28 June 2023 17:33:01 CEST, Klemens Nanni wrote:
>On Wed, Jun 28, 2023 at 02:38:00PM +0200, Alexander Bluhm wrote:
>> Hi,
>>
>> Since
On 2023-04-13 21:01 +02, "Peter J. Philipp" wrote:
> On Mon, Apr 10, 2023 at 10:17:08AM +0200, Peter J. Philipp wrote:
>> On Sat, Apr 08, 2023 at 08:28:05PM +0200, Peter J. Philipp wrote:
>> /cut
>> > Apr 6 14:43:05 polarstern unwind[97893]: bad packet: too large: 65552 -
>> > pool.ntp.org. IN
On 2023-02-07 13:15 +01, Theo Buehler wrote:
> On Tue, Feb 07, 2023 at 01:00:04PM +0100, Florian Obser wrote:
>>
>> /* RFC3849 */
>> "8.B.D.0.1.0.0.2.ip6.arpa. transparent"
>
> Surely the previous line needs a comma.
argh, this is better and migh
On 2023-02-06 14:33 -05, Ryan Kavanagh wrote:
>>Synopsis: unwind ignores 'force' directive for home.arpa
>>Category: system
>>Environment:
> System : OpenBSD 7.2
> Details : OpenBSD 7.2-current (GENERIC.MP) #1015: Thu Feb 2
> 06:25:57 MST 2023
>
On 2022-06-01 06:57 +02, Florian Obser wrote:
> On 2022-05-31 23:27 +01, Stuart Henderson wrote:
>> I accidentally updated a router to -current instead of 7.1 and hit this.
>> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Hmm? Are you saying
On 2022-05-31 23:27 +01, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
Hmm? Are you saying running just running 'sysupgrade', without any flags, moves
you from 7.0-stable to
On 2022-05-29 18:44 +01, Stuart Henderson wrote:
> On 2022/05/29 19:08, Florian Obser wrote:
>> Nevermind that we don't install libunbound at all.
>
> We do in ports.
Oh, this is about ports. Sorry, carry on, ignore me.
--
I'm not entirely sure you are real.
On 2022-05-29 12:27 -04, Andrew Cagney wrote:
> Per:
>
> --enable-event-api Enable (experimental) pluggable event base
Why? This seems like a good reason to not do it.
> libunbound API installed to unbound-event.h
On 2022-04-27 15:37 -06, Todd C. Miller wrote:
> florian@ committed a fix for this the other day:
>
No, that was for something else. Here the server violates the spec.
In the other diff we were violating the spec.
We should probably just ignore the domainname and hostname if they have
a length <
On 2022-03-09 22:20 +01, Solène Rapenne wrote:
> I see your setup only use one big / partition, this is not a default
> setup and we don't really provide help for such setups because it's
> not a supported setup and nobody is testing it.
>
Out of idle curiosity I just ran sysupgrade on a VM with
On 5 March 2022 18:02:05 CET, Theo de Raadt wrote:
>bug.ig...@aleeas.com wrote:
>
>> > OK so this matches "complex disk layout" and I'm not so surprised thatyou
>> > are having problems with sysupgrade.
>>
>> Haha. I guess you are right.
>>
>> But how did it upgrade it to snapshot then?
>>
T440p machine.
>
>
> dmesg.boot did not contain RAMDISK_CD logs. i rebooted several times
> already. sorry about that.
>
>
> On Sun, Jan 23, 2022 at 05:01:11PM +0100, Florian Obser wrote:
>> The installer sends an email to root with
>> Subject: $(hostname) upgrade log
The installer sends an email to root with
Subject: $(hostname) upgrade log
containing all the information of the upgrade run.
Please show the contents of those mails for an upgrade run with and
without the removable device attached. And indicated which one is which.
There is also a good
On 2022-01-07 08:02 +01, Otto Moerbeek wrote:
> On Thu, Jan 06, 2022 at 04:02:20PM +0100, Florian Obser wrote:
>
>> On 2022-01-06 08:44 +01, Otto Moerbeek wrote:
>> > On Thu, Jan 06, 2022 at 08:38:37AM +0100, Otto Moerbeek wrote:
>> >> Looking at the loop aga
On 2022-01-06 08:44 +01, Otto Moerbeek wrote:
> On Thu, Jan 06, 2022 at 08:38:37AM +0100, Otto Moerbeek wrote:
>> Looking at the loop again and seeing the "maximum length exceeded" I
>> think what has happened is that the loop exited without reading the
>> Date: line and so no call to strptime()
reads OK
On 2021-12-04 20:40 +01, Stefan Sperling wrote:
> On Sat, Dec 04, 2021 at 09:32:40PM +0300, Vitaliy Makkoveev wrote:
>> I think rtm_80211info() could follow the if_link_state_change()
>> way and use task for that.
>
> Indeed. I did not realize that if_link_state_change() schedules a
On 2021-11-20 15:01 +01, Jeremie Courreges-Anglas wrote:
> On Sat, Nov 20 2021, Florian Obser wrote:
>> The application can't know if AD is trustworthy or not, I think we
>> should do this fully in asr(3).
>> I'll send a diff to tech@ that implements glibc's trust-ad
>
The application can't know if AD is trustworthy or not, I think we
should do this fully in asr(3).
I'll send a diff to tech@ that implements glibc's trust-ad
( https://gnutoolchain-gerrit.osci.io/r/c/glibc/+/461 )
On 2021-11-18 08:13 +01, Otto Moerbeek wrote:
> Hi,
>
> And here a sketch of the
Only tangential relevant: RFC 6840:
5.7. Setting the AD Bit on Queries
The semantics of the Authentic Data (AD) bit in the query were
previously undefined. Section 4.6 of [RFC4035] instructed resolvers
to always clear the AD bit when composing queries.
This document defines
No idea how to reproduce this, I'm just running an httpd with debug
symbols and kern.nosuidcoredump=3
Pretty sure this is the crash various people mumbled about.
Smells like a use-after-fruit to me.
Core was generated by `httpd'.
Program terminated with signal SIGABRT, Aborted.
#0 thrkill ()
On 2021-11-01 17:24 +01, Jeremie Courreges-Anglas wrote:
> That was a bit premature, I finally managed to remotely connect to the
> machine. No idea why I couldn't connect to it for so long. Either
> a problem with the provider/router, or something wrong regarding
> riscv64, slaacd and the
On 2021-10-24 13:53 +09, Roc Vallès wrote:
> Sysupgraded my 6.9 personal server to 7.0 tonight. Only IPv6 came up
> (which I have a custom dhcp setup for, as required by my host).
>
> On the daemon log, this shows up:
> Oct 24 02:04:17 momoyo dhcpleased[92859]: parse_dhcp: invalid ports
> used
On 2021-10-20 07:55 +02, Otto Moerbeek wrote:
> On Wed, Oct 20, 2021 at 07:47:30AM +0200, Mischa wrote:
>
>> Unfortunately our joy was short lived. This morning I noticed a lot of
>> Oct 20 07:44:15 name1 nsd[80814]: server 76410 died unexpectedly with status
>> 11, restarting
>>
>> It looks
On 2021-10-15 15:58 +02, Guy Godfroy wrote:
> I have to correct what I said on this patch. It works perfectly
> well. The dynamic IP is just added to the interface, it does not
> replace the dummy one. A simple `ifconfig -A` confirms that.
Great, thanks. I have commited this to -current.
>
> I
On 2021-10-17 16:17 +02, Hiltjo Posthuma wrote:
> Hi,
>
> I noticed in mg when changing permissions while editing a file it will not
> retain the permissions.
This is how emacs behaves as well.
>
> Steps to reproduce:
>
> * mg newscript
> * Write something and save the file.
> * Outside mg
On 2021-10-15 09:17 +02, Guy Godfroy wrote:
>>Synopsis: dhcpleased unable to work on CARP interface
>>Category: system
>>Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021
>
>
On 2021-08-27 09:31 +01, Stuart Henderson wrote:
> On 2021/08/27 09:22, Sebastian Benoit wrote:
>> Maybe this is related:
>> As this box has some large filesystems, we mount them read-only and only go
>> to read-write when we actually need to change contents. For some of the
>> filesystems thats
On 2021-05-04 16:50 +02, Sebastien Marie wrote:
> On Tue, May 04, 2021 at 02:15:05PM +0200, Alexandr Nedvedicky wrote:
>> Hello Sebastien,
>>
>> thank you for additional info about previously working kernel.
>>
>> it looks like your older kernel, which works, might be running without
>> my
On Fri, Apr 16, 2021 at 05:37:29PM +0100, Stuart Henderson wrote:
> On 2021/04/16 17:19, Florian Obser wrote:
> > On Fri, Apr 16, 2021 at 10:42:00AM -0400, Kenneth R Westerback wrote:
> > > On Fri, Apr 16, 2021 at 03:17:45PM +0200, Florian Obser wrote:
> > > > On T
On Fri, Apr 16, 2021 at 11:54:24AM -0400, Kenneth R Westerback wrote:
> On Fri, Apr 16, 2021 at 05:19:38PM +0200, Florian Obser wrote:
> > On Fri, Apr 16, 2021 at 10:42:00AM -0400, Kenneth R Westerback wrote:
> > > On Fri, Apr 16, 2021 at 03:17:45PM +0200, Florian Obser wrote:
&
On Fri, Apr 16, 2021 at 10:42:00AM -0400, Kenneth R Westerback wrote:
> On Fri, Apr 16, 2021 at 03:17:45PM +0200, Florian Obser wrote:
> > On Thu, Apr 15, 2021 at 12:54:44AM +, Lucas wrote:
> > > >Synopsis:dhcpleased(8) doesn't handle underlying chang
On Thu, Apr 15, 2021 at 12:54:44AM +, Lucas wrote:
> >Synopsis:dhcpleased(8) doesn't handle underlying changes in trunk(4)
> >Category:system
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC.MP) #459: Fri Apr 9 11:31:33 MDT
> 2021
>
On Thu, Apr 08, 2021 at 07:47:52AM +0200, Klemens Nanni wrote:
> On Wed, Apr 07, 2021 at 11:16:44PM +, Uwe Werler wrote:
> > >Synopsis: no default route added when dhcp option 121 set
> > >Category: system
> > >Environment:
> > System : OpenBSD 6.9
> > Details : OpenBSD 6.9
On Sat, Mar 06, 2021 at 05:14:37PM +, Mikolaj Kucharski wrote:
> On Sat, Mar 06, 2021 at 09:39:08AM -0700, Theo de Raadt wrote:
> >
> > The ifconfig man page says "inet autoconf" sets a flag. It does not say
> > "sets the flag and brings the interface up". You want to argue against
> > the
On Sat, Mar 06, 2021 at 04:09:50PM +, Raf Czlonka wrote:
> On Sat, Mar 06, 2021 at 08:59:16AM GMT, Florian Obser wrote:
> > your interface is not "UP"
> >
> > > lladdr f0:de:f1:77:c2:c8
> > > index 6 priori
On Sat, Mar 06, 2021 at 06:41:44AM +, Adam Steen wrote:
> >Synopsis:dhcpleased does not acquire a lease
> >Category:networking
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9-beta (GENERIC.MP) #376: Thu Mar 4 21:04:56
> MST 2021
>
On Thu, Jan 14, 2021 at 09:34:49AM -0500, Brad House wrote:
> While working on debugging an issue reported in c-ares, I noticed some test
> case failures in inet_net_pton(). I haven't evaluated most of them, however
> one stood out:
>
> ../test/ares-test-internal.cc:150: Failure
>
On Tue, Jan 12, 2021 at 09:52:03AM -0700, Bob Beck wrote:
>
>
>
> On Tue, Jan 12, 2021 at 05:47:36PM +0100, Florian Obser wrote:
> > On Tue, Jan 12, 2021 at 09:40:51AM -0700, Bob Beck wrote:
> > >
> > > On Tue, Jan 12, 2021 at 04:45:32PM +0100,
On Tue, Jan 12, 2021 at 09:40:51AM -0700, Bob Beck wrote:
>
> On Tue, Jan 12, 2021 at 04:45:32PM +0100, Solene Rapenne wrote:
> > Hello,
> >
> > it seems www.openbsd.org is down since 14h46 UTC
> > If I remember correctly you are the right person to tell about it.
> >
> > Regards
> > Sol??ne
>
On 26 December 2020 17:59:45 CET, Klemens Nanni wrote:
>I use unwind on my notebook where one particular domain must always go
>through one particular resolver; this resolver should should not be
>used for anything else.
>
>Hence I overwrite the default preference list (output of
>`unwind
It might be best if you continue running Ubuntu.
Fixed in rev 1.14 of usr.bin/dig/lib/isc/sockaddr.c by jmatthew.
Sorry for the inconveniences.
On 29 November 2020 13:58:39 CET, Marcus MERIGHI wrote:
>>Synopsis: dig(1)/host(1) "invalid use of multicast address" with TCP
>>Category: user
>>Environment:
> System : OpenBSD
On Thu, Sep 24, 2020 at 12:13:31PM +0200, Mischa wrote:
>
>
> > On 24 Sep 2020, at 09:15, Florian Obser wrote:
> > 3a) does it also shutdown: bisect the hypervisor (tbh I expect the problem
> > here).
>
> 6.8 bsd.rd shuts down
> 6.7 bsd.rd reboots
>
>
Hi Mischa,
On Thu, Sep 24, 2020 at 08:52:55AM +0200, Mischa wrote:
> Hi All,
>
> With the last couple of -current updates I noticed a VM doesn’t come back
> after running sysupgrade, which it used to do.
it's very unlikely that this is a sysupgrade problem.
More likely something in the kernel
On Wed, Apr 22, 2020 at 12:54:40PM +0100, Stuart Henderson wrote:
> and fastcgi_temp* settings). I suspect httpd is in the "buffer as much
> as possible" camp (there are no config options relating to this). If
> that's the case then switching to a different web front-end is likely
> the easiest
I don't know if it is expected behavior. It does not surprise me though.
Since you are asking, what did *you* expect?
On 6 February 2020 00:41:40 CET, jungle Boogie wrote:
>Hi All,
>
>Not sure if this is the expected behavior:
>
>$ ping 1.1.1.1
>PING 1.1.1.1 (1.1.1.1): 56 data bytes
>ping:
On Tue, Feb 04, 2020 at 11:41:14AM +, Raf Czlonka wrote:
> On Mon, Feb 03, 2020 at 07:29:02PM GMT, Florian Obser wrote:
> > On Mon, Feb 03, 2020 at 07:58:24PM +0100, Solene Rapenne wrote:
> > > On Mon, Feb 03, 2020 at 07:52:29PM +0100, Florian Obser wrote:
> > > >
On Mon, Feb 03, 2020 at 07:58:24PM +0100, Solene Rapenne wrote:
> On Mon, Feb 03, 2020 at 07:52:29PM +0100, Florian Obser wrote:
> > On Mon, Feb 03, 2020 at 06:16:54PM +0100, Solene Rapenne wrote:
> > > I re-enabled unwind today (i was using append instead of prepend in
> >
On Mon, Feb 03, 2020 at 06:16:54PM +0100, Solene Rapenne wrote:
> I re-enabled unwind today (i was using append instead of prepend in
> dhclient.conf) and I got a few issues resolving domains, often the first
> time, if I try again I get a result. I'm pretty sure it's not a bug, but
> I have no
Here is an archive of snaps:
https://ftp.hostserver.de/archive/
On 4 January 2020 16:53:59 CET, Chris Bennett
wrote:
>I just don't have any copies of the older snapshots.
>I do have the emails though. Let me check to see which order I used
>from
>the emails.
>
>My method has been to try at home
On Sun, Dec 15, 2019 at 12:02:15AM -0700, Theo de Raadt wrote:
> Or even better, via the typical macro expansion used for this type of
> union, it should use ifr_addr
>
nice one, OK florian@
> Index: slaacd.c
> ===
> RCS file:
On Sat, Dec 07, 2019 at 07:09:17AM +0100, Sebastien Marie wrote:
> Hi,
>
> On an i386 and an aarch64 hosts, I have occasionally the following error in
> syslog:
is there a way to tell which one it is? Does this leave a core file
behind?
>
> Dec 7 06:45:42 joe slaacd: backwards memcpy
> Dec 7
Pretty sure that's the bug, but if not it's still a bug.
OK florian
On 2 December 2019 09:44:54 CET, Otto Moerbeek wrote:
>On Sun, Dec 01, 2019 at 11:57:08PM +0100, Klemens Nanni wrote:
>
>> On Sun, Dec 01, 2019 at 11:41:51PM +0100, Klemens Nanni wrote:
>> > It crashed again:
>> >
>> >Dec
On Sat, Nov 30, 2019 at 01:55:40AM +0100, Klemens Nanni wrote:
> OpenBSD 6.6-current (GENERIC.MP) #494: Thu Nov 28 13:24:18 MST 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> Sitting in the hut with above snapshot, no unwind.conf(5).
> unwind crashed
The next one is good:
Build date: 1573289143 - Sat Nov 9 08:45:43 UTC 2019
On Sat, Nov 09, 2019 at 06:37:58AM -0700, Theo de Raadt wrote:
> Yeah, oops.
>
> Florian Obser wrote:
>
> > I updated my X1 gen2 to
> > Build date: 1573279451 - Sat Nov 9 06:04:1
I updated my X1 gen2 to
Build date: 1573279451 - Sat Nov 9 06:04:11 UTC 2019
and I can no longer type my FDE password.
Booting a miniroot.fs from usb results in the machine hanging at
boot>
This is a known good snapshot:
Build date: 1573140006 - Thu Nov 7 15:20:06 UTC
On Mon, Oct 07, 2019 at 11:16:22AM +0100, Stuart Henderson wrote:
> On 2019/10/07 09:53, Theo Buehler wrote:
> > $ doas /usr/sbin/unbound-anchor -v
> > /var/unbound/db/root.key has content
> > [1570433629] libunbound[28321:0] fatal error: could not open autotrust file
> > for writing,
On Tue, Oct 01, 2019 at 09:46:59PM -0700, jungle boogie wrote:
> Hi All,
>
> I've noticed my auto_upgrade.conf file disappear off the / once the system
> has been upgraded. This has happened on amd64 and arm64 over the past few
> days. Is this a new feature? If so, probably a good idea to mention
On Mon, Sep 23, 2019 at 05:13:10PM +0300, kasimov...@gmail.com wrote:
> >Synopsis:acme-client does not work on IPv6-only host
> >Category:
> >Environment:
> System : OpenBSD 6.5
> Details : OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
>
On Sun, Sep 08, 2019 at 02:43:19PM +0100, Joe Davis wrote:
> On Sun, Sep 08, 2019 at 10:07:54AM +0200, Alexandre Ratchov wrote:
> >
> > Could you check that recording (or "microphone" or whatever it is
> > called) is enabled in the BIOS settings?
> >
> > There's a known problem with many
Committed with a small tweak, thanks!
On July 11, 2019 11:54:33 PM GMT+02:00, Wolf wrote:
>Hello,
>currently openbsd's acme-client breaks RFC 8555 section 6.1, in
>particular sentence
>
>> ACME clients MUST send a User-Agent header field, in accordance with
>> [RFC7231].
>
>Following patch
On Thu, Apr 11, 2019 at 07:01:30PM +0200, Christian Weisgerber wrote:
> My home gateway uses DHCPv6-PD straight out of net/dhcpcd's README.
> dhcpcd requests prefix delegation from the ISP, assigns subnets to
> local interfaces, and rad(8) picks up those addresses and advertises
> the
On Mon, Mar 04, 2019 at 12:51:28AM +0100, Wolf wrote:
> Hi,
> I'm in process of porting acme-client to linux and I might have notice
> small bug in header parsing in http.c.
>
> First, let me warn you that C is not my strongest language, so I might
> very well be wrong, but is looks to me like if
I think you should put it in. It seems to just work.
OK florian fwiw
On Tue, Feb 12, 2019 at 08:56:13AM +0100, Florian Obser wrote:
> On Sun, Feb 10, 2019 at 03:55:32PM -0200, Martin Pieuchot wrote:
> > On 10/02/19(Sun) 10:25, Florian Obser wrote:
> > > on resume I was greete
On Sun, Feb 10, 2019 at 03:55:32PM -0200, Martin Pieuchot wrote:
> On 10/02/19(Sun) 10:25, Florian Obser wrote:
> > on resume I was greeted by:
> > [typed from a photo (http://sha256.net/dump/usbd_fill_deviceinfo.jpg)]
> > kernel: page fault trap, code =0
> > Stopped at
on resume I was greeted by:
[typed from a photo (http://sha256.net/dump/usbd_fill_deviceinfo.jpg)]
kernel: page fault trap, code =0
Stopped at strlcpy+0x35: movzbl 0(%rsi, %rax,1), %ecx
strlcpy(81459c81,0,7f) at strlcpy+0x35
usbd_fill_deviceinfo at usbd_fill_deviceinfo+0x4f
usbioctl at
moved back to tech@ with this diff:
diff --git server_http.c server_http.c
index e05cec56dfc..52698a66b2e 100644
--- server_http.c
+++ server_http.c
@@ -198,7 +198,6 @@ void
server_read_http(struct bufferevent *bev, void *arg)
{
struct client *clt = arg;
- struct
we are heading for printf debugging and tcpdumping...
On October 24, 2018 1:53:18 PM GMT+02:00, "Aaron A. Glenn"
wrote:
>* Hrvoje Popovski [2018-10-23 22:46]:
>> On 23.10.2018. 21:41, Florian Obser wrote:
>> > I'm currently on vacation and can't look into thi
I'm currently on vacation and can't look into this soon.
One thing that comes to mind: do these machines keep proper time or are they
having issues with timer interrupts stopping because of too new KVM version and
missing hypervisor flag (someone with access to a real computer please chip in
e logging: slowcgi_user is logged
> at warn (which I think is too loud), whereas the chroot and socket
> paths are at debug, and the new sock_user setting isn't logged at all.
> I've attached an updated diff that uses debug for all of these.
>
>
> Thanks,
> Andrew
>
> On
On Thu, Aug 02, 2018 at 04:22:35PM -0500, Andrew Daugherity wrote:
> On Wed, Aug 1, 2018 at 6:09 AM Florian Obser wrote:
> >
> > Nice to see it being useful on other systems, too. :)
> >
> > Does this work for you?
> > [diff snipped]
>
> Yes, that w
I_USER);
+ pw = getpwnam(sock_user);
if (pw == NULL)
- lerrx(1, "no %s user", SLOWCGI_USER);
+ lerrx(1, "no %s user", sock_user);
fd = slowcgi_listen(fcgi_socket, pw);
On Tue, Jul 31, 2018 at 06:39:18PM -0500, Andrew Daugher
On Tue, Jul 31, 2018 at 06:39:18PM -0500, Andrew Daugherity wrote:
[...]
> Related: in the same section of code (at the end of my diff actually,
> as context), I noticed that when -u is used, the chroot path is set to
> the target user's home directory instead of /var/www. I found this
>
On Thu, Jul 26, 2018 at 05:31:39PM -0500, andrew.daugher...@gmail.com wrote:
> >Synopsis:slowcgi -u user option does not change socket ownership
> >Category:user
> >Environment:
> System : OpenBSD 6.3
> Details : OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST
https://github.com/freebsd/freebsd/blob/master/usr.sbin/route6d/route6d.c
> [2] https://github.com/NetBSD/src/blob/trunk/usr.sbin/route6d/route6d.c
>
> Am 14.06.2018 um 16:44 schrieb Florian Obser:
> > OK florian@ if someone wants to commit it. Alternatively I take OKs,
> > too :
OK florian@ if someone wants to commit it. Alternatively I take OKs,
too :)
On Thu, Jun 14, 2018 at 04:25:22PM +0200, Barabosch, Thomas wrote:
> Hi there,
>
> while reviewing the code, I may have stumbled upon potential memory
> leaks in usr.sbin/route6d/route6d.c.
>
> I think there is an issue
On Sat, Apr 07, 2018 at 09:44:11PM +0200, Klemens Nanni wrote:
> The latest snapshot's ramdisk fails to configure IPv6 addresses
> automatically after setting the AUTOCONF6 flag on my T5220's egress
> interface.
You mean this used to work (when?) or you mean this is the first time
you tried?
Can
>From what I can gather online hetzner statically allocates a /64 per (v)server.
I suspect they set a static route on the gateway to the link local address.
They know which link local address the (v)server will have since they know
the mac address. However, with RFC 7217 the link local address
On Tue, Apr 03, 2018 at 01:17:06PM +0200, Harald Dunkel wrote:
> Hi folks,
>
> according to the upgrade guide I added "-soii" to hostname.re1.
> It seems to work as expected, but it is not documented in
> hostname.if(5).
tb@ beat me to it :)
I have no opinion one way or the other. Probably best
On Mon, Mar 12, 2018 at 04:05:00PM +0100, Sebastien Marie wrote:
> On Mon, Mar 12, 2018 at 03:26:12PM +0100, Florian Obser wrote:
> > On Mon, Mar 12, 2018 at 11:12:51AM +0100, Sebastien Marie wrote:
> > > Hi,
> > >
> > > I upgraded several hosts (i386 an
On Mon, Mar 12, 2018 at 11:12:51AM +0100, Sebastien Marie wrote:
> Hi,
>
> I upgraded several hosts (i386 and amd64) and the stable ipv6 address
> generated using soii (Semantically Opaque Interface Identifiers)
> changed... (which is relatively annoying as I mostly use ipv6 on my
> local network
On Mon, Nov 13, 2017 at 03:22:19PM +, Heiko wrote:
> pfctl -f /etc/pf.conf
>
> pfctl: DIOCADDRULE: Operation not supported by device
I assure you there is a current snapshot on an arch I'm not telling
you with pf.conf contents I'm not telling you where pf works perfectly
fine.
While the bug report is lacking I agree that we should not go of
to the resolver, we document that flowsrc and flowdst are supposed
to be ip addresses. That hostnames worked here was an accident.
OK florian@
On Wed, Jul 19, 2017 at 12:09:29PM +0200, p...@centroid.eu wrote:
> >Synopsis:
On Mon, Jul 24, 2017 at 03:39:12PM +0200, Martin Pieuchot wrote:
> On 23/07/17(Sun) 17:23, Florian Obser wrote:
> > On Sat, Jul 22, 2017 at 02:05:27PM -, Christian Weisgerber wrote:
> > > On 2017-07-22, Florian Obser <flor...@openbsd.org> wrote:
> > [...]
>
On Mon, Jul 24, 2017 at 03:39:12PM +0200, Martin Pieuchot wrote:
> On 23/07/17(Sun) 17:23, Florian Obser wrote:
> > On Sat, Jul 22, 2017 at 02:05:27PM -, Christian Weisgerber wrote:
> > > On 2017-07-22, Florian Obser <flor...@openbsd.org> wrote:
> > [...]
>
On Sat, Jul 22, 2017 at 02:05:27PM -, Christian Weisgerber wrote:
> On 2017-07-22, Florian Obser <flor...@openbsd.org> wrote:
>
> > reenabling debug output on the ramdisk I see this:
> >
> > engine_dispatch_frontend: IMSG_PROPOSAL_ACK:
On Fri, Jul 21, 2017 at 05:34:41PM +0200, Christian Weisgerber wrote:
> i386 snapshot, Build date: 1500601432 - Fri Jul 21 01:43:52 UTC 2017
>
> I tried to run an install with...
>
> --->
> IPv6 address for em0? (or 'autoconf' or 'none') [none] autoconf
> ...
> DNS nameservers?
1 - 100 of 125 matches
Mail list logo
