|
Hello,
On Fri, 22 Nov 2013, L.S. Keijser wrote:
> Hi,
>
> On a production server with a HUGE firewall list (thanks, Shorewall!) we
> have LVS configured and up & running. All works well, except when all
> realservers are down and ldirectord switches to fallback:
>
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 1.2.3.4:80 wlc
> -> 127.0.0.1:80 Route 1 0 59
> -> 172.20.1.49:80 Masq 0 0 0
>
>
> First of all, I remembered that when switching to fallback, the forward
> method said 'Local' in the past, and now it displays Route. But okay,
> perhaps this is the new syntax.
>
> The problem is that we're getting connection refused messages.
> Telnetting on the director to localhost:80 works fine though.
>
> Anyone with some advice?
The Route mode preserves the packet addresses,
so you need a local 1.2.3.4:80 listener, the test with
localhost:80 is not adequate. IIRC, the Local mode worked
in the same way.
Regards
--
Julian Anastasov <ja@xxxxxx>
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
