I've used a FreeBSD box with a kernel extension as an intermediate bridge. The parameters for the connection are then configurable on the FreeBSD box, including bandwidth limiting and dropping packets, etc.
I don't remember the name right now but I will look it up and get back to you. At one point we also had a python webservice running on the FreeBSD box that could configure the options on the fly. -Richard Holden On Tue, Apr 12, 2011 at 1:00 PM, Dave Smith <d...@thesmithfam.org> wrote: > On 04/12/2011 12:07 PM, Nicholas Leippe wrote: >> No, but you could easily write a tool that can do any behavior you >> want between stdin and stdout, then wire it up on both ends via >> netcat. Or simply do the socket code yourself :) > > Indeed, but I want it to be transparent to my TCP/IP client application, > so stdin/stdout are, well, out (pun intended). > > The latter option of creating my own is tempting, but I really wanted to > find out if something like this already existed before embarking. > > --Dave > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
