Re: OpenBSD 6.2 (up2date with syspatch) - HANGING

rel and stable here. Eat it”. //mxb > 21 dec. 2017 kl. 23:19 skrev Maxim Bourmistrov : > > > Fixed in HEAD?! - my ass. Whom puts HEAD into prod?! Not me any more, that's > for sure. > IS LIKE DROPPING A TURBO ENGINE INTO CAR WITH NO WHEELS. > > I can dig into this

Re: OpenBSD 6.2 (up2date with syspatch) - HANGING

; 21 dec. 2017 kl. 23:07 skrev Maxim Bourmistrov : > > Solved?1 > > What abt OPTIONS in relay_http.c ? > Solved? > Maybe in HEAD.(?) > I have to hand-rolle this in src for 6.2 to have it working. > —> toread=0; > You know. > > //mxb > >> 21 dec.

Re: OpenBSD 6.2 (up2date with syspatch) - HANGING

Solved?1 What abt OPTIONS in relay_http.c ? Solved? Maybe in HEAD.(?) I have to hand-rolle this in src for 6.2 to have it working. —> toread=0; You know. //mxb > 21 dec. 2017 kl. 22:40 skrev Janne Johansson : > > 2017-12-21 21:58 GMT+01:00 Maxim Bourmistrov <mailto:m...@alu

Re: relayd/ctl alternative control socket

But what about people not running relay on rdomain, but rather just want to run separate instances of relayd ? > 28 nov. 2017 kl. 16:06 skrev Sebastian benoit > : > > Hi, > > your diff looks good, but i would rather do it the way bgpd/bgpctl do it: > > there the default is /var/run/bgpd.so

Re: relayd: 6.1-stable and relay_http.c rev 1.58

size 0, to read -2 relay_splice: session 1: splice dir 2, nothing to read -2 relay web_test, session 1 (1 active), 0, 172.17.2.21 -> 172.16.1.30:80, done, OPTIONS //mxb > 27 nov. 2017 kl. 20:20 skrev Maxim Bourmistrov : > > Here is setup which reproduces this problem. Also exists in 6.2.

Re: relayd: 6.1-stable and relay_http.c rev 1.58

ONS GET GET With the rev. current for 6.2: relay web_test, session 1 (1 active), 0, 172.17.2.21 -> 172.16.1.30:80, done, OPTIONS //mxb > 22 okt. 2017 kl. 21:02 skrev Maxim Bourmistrov : > > >> 22 okt. 2017 kl. 20:16 skrev Maxim Bourmistrov : >> >> Hey, >>

Re: relayd: 6.1-stable and relay_http.c rev 1.58

> 22 okt. 2017 kl. 20:16 skrev Maxim Bourmistrov : > > Hey, > with rev 1.58 OPTIONS in relay_http.c got broken > or at least logic inside relay_read_http(). > Quick fix it to cre->toread=0 and break, but this is probably not what should > be there. > > In my tes

relayd: 6.1-stable and relay_http.c rev 1.58

Hey, with rev 1.58 OPTIONS in relay_http.c got broken or at least logic inside relay_read_http(). Quick fix it to cre->toread=0 and break, but this is probably not what should be there. In my test case, from the client side I do an OPTIONS request, followed by a couple of GET. GET in the middle

relayd - multiple instances

Hello, Are there plans for relayd to run multiple instances? Eg. dropping socket to a configurable location. Regards

Re: relayd: incomplete response from a TLS-accelerated apache

Compiling relayd with -DDEBUG=3 and watching the output gave me nothing. No errors what so ever about out of buffers or something else. However, removing 'socket buffer 65536’ solved my problem. Br > 8 maj 2017 kl. 13:27 skrev Maxim Bourmistrov : > > Hey, > I investigate a

relayd: incomplete response from a TLS-accelerated apache

Hey, I investigate a problem were TLS-asselerated machine response is incomplete. I was able to reproduce this on OpenBSD 5.9, 6.0 and 6.1. Test on 5.8 is about to be. Following env I have: relay1: relayd machine web1: apache 2.2.31 serving the request client1: requester relay1 is configured fo

Re: OpenBSD 6.1: relayd does not start more than 3 processes

> 5 maj 2017 kl. 15:55 skrev Maxim Bourmistrov : > > >> 5 maj 2017 kl. 14:41 skrev Hiltjo Posthuma : >> >> On Fri, May 05, 2017 at 12:30:56PM +0200, Maxim Bourmistrov wrote: >>> >>> Hey, >>> on OpenBSD 6.0-stable I have following configura

Re: OpenBSD 6.1: relayd does not start more than 3 processes

> 5 maj 2017 kl. 14:41 skrev Hiltjo Posthuma : > > On Fri, May 05, 2017 at 12:30:56PM +0200, Maxim Bourmistrov wrote: >> >> Hey, >> on OpenBSD 6.0-stable I have following configuration for relayd: >> >> snip——— >> interva

OpenBSD 6.1: relayd does not start more than 3 processes

Hey, on OpenBSD 6.0-stable I have following configuration for relayd: snip——— interval 10 timeout 1200 prefork 15 log all —— Respective login.conf to spawn more relayd procs: relayd:\ :maxproc-max=31:\ :maxproc-cur=15:\ :openfiles=65536:\

OSPFd stucks in EXCHG/EXSTA

Hey, ospfd on 6.0-stable stucks in EXCHG/EXSTA while neighboring with Dell N3048 switch. According to some documentation around, this is due to MTU mismatch. This is not in my case. N3048: system jumbo mtu 1512 obsd: trunk1: flags=8943 mtu 1500 lladdr 00:25:90:78:62:b6 descript

Re: traceroute TOS

Thanks, useful(at least for me). On Apr 5, 2011, at 5:57 PM, Stuart Henderson wrote: > On 2011/04/05 16:51, Stuart Henderson wrote: >> if -t is used, display a notice when the TOS changes en-route. >> ok? > > oh, it's better with a (contrived) example: > > $ traceroute -nt 7 naiad > traceroute to

Re: Allegations regarding OpenBSD IPSEC

Theo, this thread is DEAD. Drop it. No one believes in "backdoors" planted into OpenBSD. I se commits - you dig all over the place. If "backdoor" existed, then it is gone cause of this digging. Without proof its just a plain BS. P.S. I lost my interest for a while ago now. On Dec 17, 2010, at

Re: rt2661_select_antenna()-diff

typo, noted. I will not spam this list with a new diff. On 6 jun 2009, at 18.12, Maxim Bourmistrov wrote: Hello, diff below adds missing antenna selection to rt2661. rt2x00.serialmonkey.com used as reference. //maxim Index: rt2661.c

rt2661_select_antenna()-diff

Hello, diff below adds missing antenna selection to rt2661. rt2x00.serialmonkey.com used as reference. //maxim Index: rt2661.c === RCS file: /cvs/src/sys/dev/ic/rt2661.c,v retrieving revision 1.48 diff -u -p -r1.48 rt2661.c --- rt26

login_paswd.c: cosmetic diff

This diff just adds endpwdnet() info login_passwd.c This is probably not needed as we will exit() anyway later on. diff-- --- login_passwd.c.orig Tue Aug 1 12:12:10 2006 +++ login_passwd.c Sat May 9 13:54:32 2009 @@ -57