Hello All, An all new problem to solve.
Came up with this idea, the boss man likes it. Our company supports several clients and the majority have unshakeable policies of ZERO INCOMING INTERNET TRAFFIC. No ports open, period. The only way to remotely support these clients is to dial into their networks through ISDN. We have many (MANY) ISDN lines, and only 1 dual line is plugged into one ancient PC running NT4. This is our remote ISDN support box, and we are beginning to get queues to use it. We can't afford a more support PCs, plus we like this idea better. :) I came up with the idea that we might be able to NAT our development PCs behind a LEAF powered ISDN dial-up support box. The IPs of the remote servers that we support are generally in the 10.0.0.0/16 range, so I have to be careful with routes. Generally 1 IP address (say, 10.1.0.12) means Dial Client X and NAT connections to that host behind the IP dished out by the client's DHCP server. Then that connection must drop after 60 seconds. Any way to remotely control the connections? A daemon that sits and shows connection status and takes commands to drop them? So, multiple ISDN channels (2 per adaptor), can these go into a pool and connected to a client when required? Then discarded back into the pool after the timeout. Just a thought experiment at the moment, I'm still building Alex's network (ECI DSL modems won't work with Bering 1.2, joy...) and I've got a million and one jobs in The List to do first. James. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
