Re: ratble and rdomain support on dhcpd and openvpn

Kapetanakis Giannis wrote: On 15/07/16 22:34, Difan Zhao wrote: Thank you sir! So I probably just stick with my hacking approach and wait for the 6.0. I see that will come in November so not too much waiting. So any idea how the openvpn might start to support rtable or rdomain? Thanks, Difan

Re: ratble and rdomain support on dhcpd and openvpn

On 15/07/16 22:34, Difan Zhao wrote: Thank you sir! So I probably just stick with my hacking approach and wait for the 6.0. I see that will come in November so not too much waiting. So any idea how the openvpn might start to support rtable or rdomain? Thanks, Difan OpeBSD -current

Route via gre0 works different than route via gre{1,2}?

Hi, while debugging a problem with routing via GRE I figured out I have to use `route add $LAN_A $GRE_REMOTE_A` for the route going via gre0 but `route add -iface $LAN_B $GRE_LOCAL_B` for a route via gre1. When I used `route $LAN_B $GRE_REMOTE_B` packets for $LAN_B were send via gre0 (and

Re: ratble and rdomain support on dhcpd and openvpn

Thank you sir! So I probably just stick with my hacking approach and wait for the 6.0. I see that will come in November so not too much waiting. So any idea how the openvpn might start to support rtable or rdomain? Thanks, Difan -Original Message- From: Chris Cappuccio

Re: jot(1) changed behavior

Philippe Meunier wrote: > jot -r 10 1 3 | sort -n | uniq -c > > which the man page clearly indicates should produce something like: > > 24950 1 > 50038 2 > 25012 3 > > which is also more in line with the "generate random floating point > number and truncate to even"

Re: ratble and rdomain support on dhcpd and openvpn

Difan Zhao [difan.z...@pason.com] wrote: > Hi Pierre, > > I just upgraded the soekris box to openbsd 5.9 however I am still having the > problem setting the rtable... > This requires OpenBSD 6.0 which is not yet released. You can use snapshots at

easy-rsa on 5.9: STR_COPY variable has no value

Hi, I've been using easy-rsa on OpenBSD to manage rsa keys for OpenVPN for years, but after I upgraded to 5.9 (and applied all the errata patches up to 020_amap.patch.sig), I get an error when I try to create and sign new certificate: # ./easyrsa build-client-full test.example.org Note: using

Re: jot(1) changed behavior

Theo Buehler wrote: >$ jot -r -p 0 10 1 3 | sort -n | uniq -c >33464 1 >33246 2 >33290 3 According to the man page, "in the absence of -p, the precision is the greater of the numbers begin and end". Since both 1 and 3 have a precision of zero, therefore I would expect your command: jot -r

Re: shm_mkstemp(3) without the file name

Philip Guenther wrote: Well, I am amazed. I guess I just have to do some more investigation into workarounds for this, as RAM-based tmpfs file systems will get full very quickly with shared memory segments, and large segments result in high disk activity when munmap() is called. And SysV shared

Re: shm_mkstemp(3) without the file name

On Fri, Jul 15, 2016 at 1:56 AM, wrote: > Ted Unangst wrote: >> >> bytevolc...@safe-mail.net wrote: >>> >>> I see where you are coming from, but what I am getting at is, where in >>> the POSIX standard does it say that it needs to be anywhere in the file >>> system at

Re: shm_mkstemp(3) without the file name

Ted Unangst wrote: bytevolc...@safe-mail.net wrote: I see where you are coming from, but what I am getting at is, where in the POSIX standard does it say that it needs to be anywhere in the file system at all? If it is shared memory, then surely this doesn't require backing up. Oh. It doesn't

Re: jot(1) changed behavior

> The second exmaple: > > $ jot -r -p 0 10 0.5 3.5 | sort -n | uniq -c > 25120 0 > 49882 2 > 24998 4 > > So I'd says there are real bugs introduced with the latest commit. > > -Otto > Indeed, this is bad. The following patch lets the code fall back to the old version in the cases