Re: problems with hoststated and relayd

2008-03-07 Thread Reyk Floeter
On Thu, Mar 06, 2008 at 08:58:01PM +0100, Sebastian Reitenbach wrote: > Reyk Floeter <[EMAIL PROTECTED]> wrote: > > btw., did you test it with the latest code from -current? > > the sparch64 was installed from a snapshot not very long ago: > OpenBSD 4.2-current (GENERIC.MP) #113: Wed Feb 13 20:47

Re: problems with hoststated and relayd

2008-03-06 Thread Sebastian Reitenbach
Reyk Floeter <[EMAIL PROTECTED]> wrote: > btw., did you test it with the latest code from -current? the sparch64 was installed from a snapshot not very long ago: OpenBSD 4.2-current (GENERIC.MP) #113: Wed Feb 13 20:47:18 MST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC.MP t

Re: problems with hoststated and relayd

2008-03-05 Thread Reyk Floeter
btw., did you test it with the latest code from -current? On Mon, Mar 03, 2008 at 07:37:53PM +0100, Sebastian Reitenbach wrote: > Reyk Floeter <[EMAIL PROTECTED]> wrote: > > hi! > > > > it tested your config and it works fine without problems, there is no > > bug in relayd here... > > > > ...yo

Re: problems with hoststated and relayd

2008-03-03 Thread Wijnand Wiersma
Hi Reyk, thank you for your reply. Reyk Floeter schreef: On Mon, Mar 03, 2008 at 10:29:30AM +0100, Wijnand Wiersma wrote: Sebastian Reitenbach wrote: Also a http redirect did not work. I get a timeout in the browser. With tcpdump I see incoming SYN packets to port 80, but they are not an

Re: problems with hoststated and relayd

2008-03-03 Thread Sebastian Reitenbach
Reyk Floeter <[EMAIL PROTECTED]> wrote: > hi! > > it tested your config and it works fine without problems, there is no > bug in relayd here... > > ...you seem to make a common mistake: > > > forward to port http mode hash \ > > check http "/" code 200 > > you expect t

Re: problems with hoststated and relayd

2008-03-03 Thread Sebastian Reitenbach
Hi, Reyk Floeter <[EMAIL PROTECTED]> wrote: > On Mon, Mar 03, 2008 at 10:29:30AM +0100, Wijnand Wiersma wrote: > > Sebastian Reitenbach wrote: > > > > > > > > Also a http redirect did not work. I get a timeout in the browser. With > > >tcpdump I see incoming SYN packets to port 80, but they are

Re: problems with hoststated and relayd

2008-03-03 Thread Reyk Floeter
hi! it tested your config and it works fine without problems, there is no bug in relayd here... ...you seem to make a common mistake: > forward to port http mode hash \ > check http "/" code 200 you expect that the webservers always return the HTTP error code 200 OK. t

Re: problems with hoststated and relayd

2008-03-03 Thread Reyk Floeter
On Mon, Mar 03, 2008 at 10:29:30AM +0100, Wijnand Wiersma wrote: > Sebastian Reitenbach wrote: > > > > > Also a http redirect did not work. I get a timeout in the browser. With > >tcpdump I see incoming SYN packets to port 80, but they are not answered: > > > > > > > I am having the same prob

Re: problems with hoststated and relayd

2008-03-03 Thread John Johansson
On Mon Mar 03, 2008 at 07:45:00 +0100, Sebastian Reitenbach wrote: > Hi, > > this is the first time I play around with hoststated/relayd. > I have a stateful web application, and try to use hoststated/relayd in front > of it. Because the application is stateful, the client has to be redirected > t

Re: problems with hoststated and relayd

2008-03-03 Thread Wijnand Wiersma
Sebastian Reitenbach wrote: Also a http redirect did not work. I get a timeout in the browser. With tcpdump I see incoming SYN packets to port 80, but they are not answered: I am having the same problem with Feb 25 snapshot. It seems no rdr rules are getting loaded into PF. And I wa

problems with hoststated and relayd

2008-03-02 Thread Sebastian Reitenbach
Hi, this is the first time I play around with hoststated/relayd. I have a stateful web application, and try to use hoststated/relayd in front of it. Because the application is stateful, the client has to be redirected to the same instance for the session lifetime. The session id is encoded as GET