Hi Willy,
Thank you a lot for your help.
Alternately, you can use the "source" parameter either on each server
or in the backend to fix a port range. Haproxy will then use an explicit
bind. This is normally used when you want to have more than 64k conns on
multiple servers. But here you could try this :
source 0.0.0.0:32678-61000
Great! As I understand we can set port range to exclude listening ports
and so eliminate such errors? Probably it may be a good workaround.
Thank you again for the idea.
Yes, but the range is contiguous, so you cannot puch holes in it.
Tried to configure but have some questions. We have several 'listen'
sections with 'server' keyword in our config file (and so there are no
'backend' sections).
1. As I understand 'source' should be put into each of our 'listen'
section. Should we divide port ranges between several 'listen' sections
or may use the same wide range for all?
2. Will there be EADDRNOTAVAIL errors if several 'listen' section use
the same source port range and two connections choose the same port?
Thank you for your time and so good explanations.
--
Best regards,
Denis Malyshkin,
Senior C++ Developer
of ISS Art, Ltd., Omsk, Russia.
Mobile Phone: +7 913 669 2896
Office tel/fax +7 3812 396959
Yahoo Messenger: dmalyshkin
Web: http://www.issart.com
E-mail: dmalysh...@issart.com
