cromp -- idea for useful gateway routerish app

[Fred T. Hamster]

a cromp plugin to take traffic arriving at port X on address Y
and redeliver the packet enclosed to port A on address B.

a basic redelivery mechanism to provide a one way tunnel.

is this useful?

ssh already provides something even more nice.

would it actually meet any needs? we'd need
the sender and receiver to both be cromps, so they
can fake the address and such.

but on the return path, how does the app we're communicating with in the bare,
just the package / payload, how does it get the data back to that cromp component
so the component can redeliver it back out on the appropriate path.
and then the real receiver needs to be out there, or does cromp need to be there?
it just wouldn't work at all well.

you'd have to be able to control the ports and stuff utterly, like the services
think they're talking to cromp server Q at port R on address S.

S would be localhost.
R would be where cromp server runs.
Q would be services provided.

that would actually be useful; a way to reroute local services to a totally
different machine, essentially making the machines feel linked at the local level.

basically surmounts firewalls. not always a good thing at all! but sometimes
really crazy helpful.

possible application: email tunnel. instead of ssh, run the tunnel over the cromp
server. proof of concept perhaps;
cromp is not always encrypted,

is it?

but we have encrypt capability. we could use it for this at least as a demo.