|
I can get the tcpdumps Thursday. Here's a breakdown on what I see so far.
Client sends a dns request to eth0:0 207.156.7.23:53 (Director) then it goes to
the real server 207.156.7.21:53.
Client sends an smtp message to eth0:1 207.156.7.33:25 (Director) then instead
of it being forwared to the real server 207.156.7.21:25 the director
207.156.7.33 recieves the mail request. I know this because I check the maillog
on the director. When I remove 207.156.7.23:53 via IPVSADM then the director
forwards the request to 207.156.7.21:25.
IP Virtual Server version 0.9.4 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 207.156.7.23:53 rr
-> 207.156.7.21:53 Route 1 0 0
UDP 207.156.7.23:53 rr
-> 207.156.7.21:53 Route 1 0 0
TCP 207.156.7.33:25 rr
-> 207.156.7.21:25 Route 1 0 0
Brett Simpson
Internet Administrator for Hillsborough County
(813) 301-7144
simpsonb@xxxxxxxxxxxxxxxxxxxxxx
>>> pmueller@xxxxxxxxxxxx 10/17/01 03:40PM >>>
> Hello, I'm trying do some simple load balancing with Direct
> route across several servers. I have two servers running
> seconday dns and sendmail . And two servers running HTTP. The
> problem I'm having is only the first service (207.156.7.23)
> works while the others (207.156.7.33 and 207.156.7.43) don't
> work. If I remove the 207.156.7.23 entries then
> 207.156.7.33:25 works fine. Thanks.
'don't work' ? what actually happens? tcpdumps (does request appear on the
application servers, etc) would be good..
_______________________________________________
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
|
