|
Hi,
tnx :) in few time we must release some news :)
Just before phrack is out, that's good :)
LVS-DR
Ok. You've got asymmetric routing then.
is a separated vlan, not for backuo line, we need behind the LVS
10-12 RS to work as IDS.
So you somehow get traffic over the director over a 2GBit/s VLAN and you will
redirect this to 10 100MBit/s RS that should then do what?
I'm thinking only to divide the traffic between the IDSs, with a
session tracking of LVS I think this could work fine ...
Hmmm, excuse my ignorance but an IDS is a rather passive system. You don't
really want to know someone passing your network that there is an IDS, right?
OTOH, if you mean that you need the LVS to do event correlation and fine
granular pattern matching, then you could set it up in a CIDR manner. The client
(IDS in this case) however will need to sent tcpdump-like trace in GBit/s speed.
I think to use 10/12 cross wire for connect the IDSs directly
I'm confused, sorry. Could you maybe draw an ASCII chart of what you intend to
do?
maybe :) and LVS-DR don't required a lots of memory how could required
LVS-NAT ... but what's about network device ? we are thinking to
but three quad intel for contact the RS and two 3Com 35985 for external
interface, did you know if those work correctly ?
They work correctly in this setup but you need at least 66Mhz, if not 100Mhz
64bit PCI bus systems which are not hardwired, thus the latest Intel boards.
Regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
| 