Re: haproxy resolvers, DNS query not send / result NXDomain not expected

On Tue, Sep 8, 2015 at 7:58 AM, Baptiste wrote: >>> Hi, >>> >>> I wonder why the code send the TCP port in the DNS query... >>> I'm currently installing an opnsense and I'll try to reproduce the >>> problem. >>> >>> I've not used FreeBSD since 5.4 version :) >>> >>> Baptiste >>

7.8USD----720P AHD Camera

    Grace Le Sales manager   Skype: graceliyan09  whatsapp: +86-136 3284 7386Mobile:+86 136 3284 7386 Email: gr...@aopvision.com  **SHENZHEN ANNIDIGITAL TECHNOLOGY CO.,LTD. (aopvision)Add:2F, D Block, No.7 Building East, Shangxue Hi-tech Industrial

HAProxy flow control

Hi, I've read the HAProxy 1.5 Configuration Manual, and I find restrictions for connection numbers, session numbers, etc. However, I notice that there is not any restriction to control the flow rate as they focus more on the numbers rather than the flow rate. I know that iptables can realize this

SSL errors with HAProxy

i am not sure what i am doing wrong, but i keep getting errors in my browser when trying to browse to my site. i just moved from an old OS and HAProxy instance to current, and may have issues with config directives to work out. please be patient :) just about every third request works.

SSL and Piranha conversion

Hello All, First time caller, short time listener. So this is the deal. My organization was running a CentOS box with Piranha on it to work as our load balancer between our two web servers. Well the CentOS box was a Gateway workstation from 2000 and it finally gave up the

Re: SSL and Piranha conversion

On 8 Sep 2015 20:07, "Daniel Zenczak" wrote: > > Hello All, > > First time caller, short time listener. So this is the deal. My organization was running a CentOS box with Piranha on it to work as our load balancer between our two web servers. Well the

Re: SSL and Piranha conversion

Piranha is a front end for LVS (layer 4 load balancing) So I'm assuming that all your Piranha box was doing was forwarding port 443 & 80 to your two servers... So just set up HAProxy in TCP mode for port 80 & 443. Test it , and then when you are happy point your DNS at it. On 8 September

RE: SSL and Piranha conversion

Malcolm, The Piranha gui had some configurations about Virtual IPs and I am not sure how that works or how it is different than HAProxy. The firewall had some rules that pointed website requests to the virtual ips. Daniel -Original Message- From: Malcolm Turnbull

Re: haproxy resolvers, DNS query not send / result NXDomain not expected

Op 8-9-2015 om 17:39 schreef Baptiste: Hi Piba, Finally, Willy fixed it in a different (and smarter) way: http://git.haproxy.org/?p=haproxy.git;a=commit;h=07101d5a162a125232d992648a8598bfdeee3f3f Baptiste Hi Baptiste, Just compiled latest snapshot + the list of patches from today and now it

Re: SSL and Piranha conversion

On Tue, Sep 08, 2015 at 09:53:24PM +0100, Malcolm Turnbull wrote: > Daniel, > > All load balancers work in roughly the same way: > > You have a Virtual IP on the load balancer that the clients talk to, > and the load balancer is configured to talk to multiple Real > IPs/Backend Servers. > Your

Re: SSL and Piranha conversion

On 8 September 2015 at 20:56, Daniel Zenczak wrote: > Hello Jonathan, > > Thank you for the response. That old gateway workstation is > not going to be used anymore (the HDDs failed on it and the RAID board > didn’t warn/detect/tell us when it happened).

Re: SSL and Piranha conversion

Daniel, All load balancers work in roughly the same way: You have a Virtual IP on the load balancer that the clients talk to, and the load balancer is configured to talk to multiple Real IPs/Backend Servers. Your old config probably had one VIP for HTTP and one for HTTPS. HAProxy is very easy

Re: TCP_NODELAY in tcp mode

> On 30 авг. 2015 г., at 22:29, Willy Tarreau wrote: > > On Fri, Aug 28, 2015 at 11:40:18AM +0200, Lukas Tribus wrote: Ok, you may be hitting a bug. Can you provide haproxy -vv output? >>> >>> >>> What do you mean? I get the following warning when trying to use this

Re: halog Makefile

> On 8 сент. 2015 г., at 17:26, Dmitry Sivachenko wrote: > > Hello, > > Can you please apply the following patch to contrib/halog/Makefile not to > override $CC (on some systems compiler is called "cc", not "gcc"): > > --- Makefile.orig 2015-09-08

Re: TCP_NODELAY in tcp mode

Hi Dmitry, On Tue, Sep 08, 2015 at 05:25:33PM +0300, Dmitry Sivachenko wrote: > > > On 30 ??. 2015 ??., at 22:29, Willy Tarreau wrote: > > > > On Fri, Aug 28, 2015 at 11:40:18AM +0200, Lukas Tribus wrote: > Ok, you may be hitting a bug. Can you provide haproxy -vv output?

Re: haproxy resolvers, DNS query not send / result NXDomain not expected

Hi Piba, Finally, Willy fixed it in a different (and smarter) way: http://git.haproxy.org/?p=haproxy.git;a=commit;h=07101d5a162a125232d992648a8598bfdeee3f3f Baptiste

Re: HAProxy flow control

Op 8-9-2015 om 13:16 schreef ruoyu Zhang: Hi, I've read the HAProxy 1.5 Configuration Manual, and I find restrictions for connection numbers, session numbers, etc. However, I notice that there is not any restriction to control the flow rate as they focus more on the numbers rather than the

Re: SSL errors with HAProxy

Op 8-9-2015 om 14:17 schreef Brendan Kearney: listen https 192.168.120.2:443 remove the address and port from the listen directive above, as currently it will bind port 443 twice, once with once without ssl offloading, leading to unpredictable results.. bind 192.168.120.2:443 ssl crt