Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+\[SOLVED\]\s+Question\s+about\s+director\s+$LVS\-DR$\s+\&\s+realservers\s+on\s+different\s+VLANs\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+\[SOLVED\]\s+Question\s+about\s+director\s+$LVS\-DR$\s+\&\s+realservers\s+on\s+different\s+VLANs\s*$/: 1 ]

Total 1 documents matching your query.

1. Re: [lvs-users] [SOLVED] Question about director (LVS-DR) & realservers on different VLANs (score: 1): Author: "Net Ground - Frederique Rijsdijk" <frederique@xxxxxxxxxxxx>; Date: Wed, 24 Oct 2012 07:13:35 +0200; Well, it seems my case was not fully onderstood or looked at. My problem seems a feature, not a bug. It is because of the tagged vlan ports the LVS has. When a realserver acts as a client in my case,; /html/lvs-users/2012-10/msg00018.html (9,664 bytes)

Current List: 1 - 1
Page: [1]