> Yes, these are the alternatives we are considering. Yes, all of these > depend -- more or less -- on access to proprietary information to which > we may or may not be privy ;< > > Of course, the image/fileserver approach makes most sense from many > perspectives. > > Nevertheless, the port forwarding ``tee'' feasibility is an interesting > question, regardless of our current customer's predicament!
But saddly, this is not generally possible. Certianly not without some custom code. Perhaps not at all depending on the details of the communication protocol (or at least not without a full application level proxy). > man ipmasqadm, on my potato box, contains and interesting example, which > may or may not shed light on this; but, which I also do *not* fully > understand: > > ``Redirect all web traffic to internals hostA and hostB, where hostB > will serve 2 times hostA connections. Forward rules already masq > internal hosts to outside (typical). > ipchains -I input -p tcp -y -d yours.com/32 80 -m 1 > ipmasqadm mfw -I -m 1 -r hostA 80 -p 10 > ipmasqadm mfw -I -m 1 -r hostB 80 -p 20'' > > What is this really doing? If I'm understanding this properly, it's doing load-balancing. This divides individual inbound web connections between two internal web servers. You want something that takes a single inbound connection (from the remote system to your internal "Master" system) and Tee's the connection to multiple systems, which is just not how TCP communications work... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
