|
Hi Wensong,
Basically it's not ssh specific. I tried it with http and got
the same results. If I use NAT instead of direct routing, it
seems to work fine.
I didn't conciously use and persistent port configuration
unless its a default rule.
It seems to be some funky arp related thing cause like I said, if I
disable the machine that it decides to go to, then balancing begins
to work, as soon as I bring it back up, lvs will only go to that
machine.
Same rules, except using the NAT method works fine.
Please tell me how to give you more information and I will.
The NAT method works fine for my requirements, but I'm still curious about
the weird behavior with Direct Routing.
Thanks
-jeremy
> You probaby need to tell us more information about your ipvs
> configuration. we may help to solve it.
>
> BTW, do you use the persistent port for your VIP:22? If so, the
> default timeout of persistent port is 360 seconds, once the ssh
> session finishs, it takes 360 seconds to expire the persistent
> session. (In ipvs-0.9.1, you can flexibly set the timeout for
> the persistent port.) In fact, there is no need to use persistent
> port for ssh service, because the RSA keys are exchanged in each
> ssh session, and each session is not related.
>
> Wensong
>
>
>
> ----------------------------------------------------------------------
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
>
http://www.xxedgexx.com | jeremy@xxxxxxxxxxxx
---------------------------------------------
Y2K. We're all gonna die.
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
