Hello,
On Mon, Jul 01, 2019 at 09:11:28PM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> "route-to" is used with the interface used for the next hop. But if
> it is used with a source address track (sticky-address), it sometimes
> output the packet to wrong interface.
>
> Example:
>
> pass in quic
Hey there. I thought to put this here, instead of openbsd-misc, as it's a
suggestion more than a question I think. Let me know if a more discussion
mailer would be better.
Following troubles I've been having getting a sparc64 to boot from a softraid
mirror (https://marc.info/?l=openbsd-sparc&m=1
No functional change intended, just simplify the code.
OK?
martijn@
Index: enqueue.c
===
RCS file: /cvs/src/usr.sbin/smtpd/enqueue.c,v
retrieving revision 1.115
diff -u -p -r1.115 enqueue.c
--- enqueue.c 31 May 2018 21:06:12 -
I totally forgot about the instance where blink-and-insert can be called
from the mg startup file. My previous diff broke that instance. So this
diff reverts my change but adds a man page line to blink-and-insert (and
comment).
ok?
Index: def.h
With the recently committed kern_event.c,v1.105 there aren't any
timespecfix() callers left.
ok?
Index: kern/kern_time.c
===
RCS file: /cvs/src/sys/kern/kern_time.c,v
retrieving revision 1.119
diff -u -p -r1.119 kern_time.c
--- kern/
Mon, Jun 24, 2019 at 11:43:15AM +0300, Eygene Ryabinkin wrote:
> Mon, Jun 17, 2019 at 04:15:10PM +0300, Eygene Ryabinkin wrote:
> > Sun, Jun 09, 2019 at 11:44:10AM -0300, Martin Pieuchot wrote:
> > > In that case would it makes sense to apply the so-called unicast
> > > check to `ifp', the incoming
On 01/07/19(Mon) 09:05, Moritz Buhl wrote:
> Hi,
>
> I started porting some NetBSD libc tests. They use atf which is a lot more
> than necessary for most tests.
> Attached is a passing test file for access(2). I would continue the same
> way with the other tests if people say it is ok to work arou
Hi,
"route-to" is used with the interface used for the next hop. But if
it is used with a source address track (sticky-address), it sometimes
output the packet to wrong interface.
Example:
pass in quick inet proto tcp from any to 192.168.0.10 port 80 \
keep state (sloppy) route-to source
> Date: Thu, 27 Jun 2019 15:08:00 +0300
> From: Paul Irofti
>
> Hi,
>
> Here is an initial diff, adapted from NetBSD, that synchronizes TSC
> clocks across cores.
>
> CPU0 is the reference clock and all others are skewed. During CPU
> initialization the clocks synchronize by keeping a registry
Hello,
On Mon, Jul 01, 2019 at 02:45:12PM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> The source address tracking (sticky-address) is kept dulring there are
> states which refer it. This is mentioned in pf.conf(5). This is true
> for translation(nat-to, rdr-to) but it was not true for
> routing(ro
On Sun, Jun 30, 2019 at 04:54:28PM +0200, Martijn van Duren wrote:
> Found by Mischa Peters by running some experimental code of mine.
>
> When chaining two proc-based filters together the second proc will not
> get its parameter correctly, since lka_filter_process_response won't get
> a parameter
Hi,
I started porting some NetBSD libc tests. They use atf which is a lot more
than necessary for most tests.
Attached is a passing test file for access(2). I would continue the same
way with the other tests if people say it is ok to work around atf this
way. I only changed two includes in t_acces
Hi,
while testing arm hardware on OpenBSD I noticed that some floating point
operations cause failures of other tests.
In fact the current libm is incorrect according to the ISO C Std Annex
G. I found this out after porting some FreeBSD lib msun tests. Many edge
cases for complex floating point op
13 matches
Mail list logo
