|
OK. Checked it and the port checker is tcp only is specifically excludes
udp protocol.
The checking code opens a tcp port I think, but I'm sure there must be
an equivalent udp port open/close it could use.
It could be simply that as UDP is connection-less opening/closing a udp
port tells you nothing. I'm rusty on my socket stuff so I can't tell
you.
Sorry.
On Thu, 2005-05-12 at 14:03, Malcolm Turnbull wrote:
> Graham David Purcocks M.A.(Oxon.) wrote:
>
> >I'm missing something. The connect check type just opens and closes a
> >connection based on the protocol. So if the service is udp, why don't
> >you have protocol=udp? Why do you want a TCP check when its a UDP
> >service?
> >
> >
> Well what I'd really like is a UDP connect check for a UDP service but
> that doesn't seem to work.
>
> For instance if you do :
>
> virtual=10.0.1.31:53 gate Test_DNS
> real=10.0.0.50:53 gate 1
> fallback=127.0.0.1:53
> service=none
> checktype=connect
> scheduler=wrr
> protocol=udp
>
> It wont work... (NB. obviously in production I want to use a different
> port than 53 but its an easy one to test
> But :
> service=dns
> will work because of the special handling.
>
>
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
--
|
