Just wondering about the possibilities of creating a Proxy/Firewall application,
more playing with the idea really :-)

Looking at it in the "cheap and {*filter*}" design view, a server port (8080) and
client ports (1025 -> 65535); the request goes to the server, and is forwarded
to the client module and spat back to the server for the browser or whatever
made the original call.

Should be fairly easy -- as an "idea"  :)

With .NET's built-in support for sockets, doing this sort of thing
should be much easier than trying to do it in previous versions of VB.

Here's an open-source (Java) proxy:

http://www.*-*-*.com/

You may be able to get more ideas at that site.

--
Patrick Steele
Microsoft .NET MVP

Not entirely what you mean, but getting close: I wrote a Proxy component.
What it does is listening on an IP port for communication. When
communication is received it sends this to the "real" server and the other
way around.

I'm currently using it as a proxy for POP3, connecting to my local server
that in its turn connect to the remote POP3 server. It also works with SMTP.

With FTP there is a problem with PASSIVE mode, when a new connection is to
be made.

Wim

PS: if interested in the component, send me an email at: